[Simh] Multiple telnet ports in SimH to RSTS/E 9.6

[Christian Gauger-Cosgrove]

On 31 December 2015 at 14:19, Will Senn <will.senn at gmail.com> wrote:
> I am not able to figure out what devices to enable in SimH PDP-11 to get
> multiple telnet connections in RSTS/E 9.6.
>
> I'm using a PDP-11/73 with 4megs of memory and I have the console
> configured:
>
> SET CONSOLE TELNET=10000
>
> I am able to telnet into port 10000. It works as a login terminal no
> problem.
>
That's your "master" console device. If that telnet session
disconnects your sim will halt. (Make sure you add a buffer if you
want to be safe.)


> But, then I also tried to set up some DZ11 lines to support additional
> logins over local telnet:
>
> SET DZ ENABLE
> SET DZ LINES=8
> ATTACH DZ  10001
> SHOW DZ
>
> but these don't seem to be picked up by RSTS/E. SimH let's me connect via
> telnet to ports 10001-10007, but RSTS/E does not respond in the telnet
> session. I reviewed my sysgen for RSTS/E and it doesn't appear to have a
> DZ11 peripheral configuration section. My sense is that RSTS/E doesn't
> support DZ11s.
>
Like Mark Pizzolato stated, the eight DZV11 lines will be on port
10001. Add "-am" options to the attach statement to make your life
easier for the actual configuration of the ports. (I'll cover that
later.)


> Here is the relevant section of the sysgen:
> Accept Peripheral defaults ?    <N >
> ---snip disk drives, paper tape, etc.
> DMC11's/DMR11's ?               <00>
> DMV11's/DMP11's ?               <00>
> IBM 3271 or 2780/3780 simultaneous links ?      <00>
> RJ2780 support ?                <N >
>
> In looking at the
> AA-2669J-TC_RSTS-E_System_Installation_and_Update_Guide.pdf file, page 49.
> It has this to say about the IBM 3271 or 2780/3780 option (sounds like an
> alternative device to the DZ?):
>
> Explanation - Each KMC-11 microprocessor controls one DUP11 synchronous line
> interface to the 3271 or 2780/3780 host... and so on.
>

On 31 December 2015 at 14:52, Paul Koning <paulkoning at comcast.net> wrote:
> KMC/DUP are used for the 2780 emulation feature, which is a rather obscure layered product -- I don't know anything about it.
>
Both of those layered products let you connect your RSTS/E PDP-11 to
an IBM System/370 mainframe via BISYNC and have your '11 pretend it is
either a 3271 or an RJE station. I'm particularly interested in
finding the the RJE one, and the 3271 one; since I fool around with
Hercules a lot and I'd love to try out RJE via a PDP-11 (and the 3271
product sounds interesting as well).


> As of RSTS V9.0, if memory serves, terminal configuration is no longer set during Sysgen.  Instead, the monitor contains drivers for each supported terminal interface, and these are loaded at startup according to what hardware was found.
>
Correct, terminal configuration is done in the startup command file:
SY:[0,1]START.COM


So, let's do the whole thing of setting up RSTS/E to use the DZV11
ports. I'm using RSTS/E V10.1-L, and I'm too lazy to pull up V9.6, but
the syntax/process to set up the ports are the same in both:

First of all inside of your simulator configuration:
set TTI 8B ; Full 8-bit transmission, needed for VT-100 to work right
set TTO 8B ; As above
        <...>
set CONSOLE TELNET=10000 ; Connect master console (TTI/TTO devices) to
telnet port
; set CONSOLE TELNET=LOG=conlog.txt  ; Uncomment this if you want a
log of your terminal session
set CONSOLE TELNET=BUFFERED=1048576 ; Buffer the console (in case your
telnet disconnects)

As a fun suggestion, try running the RSTS SYSGEN after setting both
TTI and TTO to 8B mode. The results are nifty:
<https://dl.dropboxusercontent.com/u/69943308/RSTS_VT-100_SYSGEN.png>


Now once you've booted your RSTS/E system, and logged in under [1,2]:
> Create your own privileged account (it'll prompt you to set your password, of course):
$ CREATE/ACCOUNT/NAME="W. Senn"/TEMPLATE=_SY:[1,2] [1,4]
> Logout, and login to your new account:
$ BYE
        <extraneous output snipped for brevity>

HELLO 1,4
> Setup your terminal as a VT-100 (SY:[0,1]START.COM defaults the TT0: device as an LA36):
$ SET TERMINAL/DEVICE_TYPE=VT100
> List all the devices your RSTS/E has been configured with (we need this to know the names of the DZV11 devices):
$ SHOW DEVICES/ALL
Device _DV0:                                         Status: Disabled by INIT
        <extraneous output snipped for brevity>
Device _KB12:  (KBG0:)   Control DZ0:0   CSR 760100  Status: Restricted
Device _KB13:  (KBG1:)   Control DZ0:1   CSR 760100  Status: Restricted
        <More DZ11 lines output trimmed because I configured 64 lines;
UNIBUS for the win>
Device _KB74:  (KBG62:)  Control DZ7:6   CSR 760170  Status: Restricted
Device _KB75:  (KBG63:)  Control DZ7:7   CSR 760170  Status: Restricted
        <extraneous output snipped for brevity>
> Write down, or otherwise note the KBG#: for each of the DZV11 lines.
> Copy SY:[0,1]START.COM to your local directory, make a backup copy of it, and open it with EDT (this is why we needed VT-100 function, unless you *like* line mode editing):
$ COPY SY:[0,1]START.COM [1,4]START.COM
[File [0,1]START .COM copied to [1,4]START .COM]
$ COPY START.COM START.BCK
[File START .COM copied to [1,4]START .BCK]
$ EDIT START.COM
    1       $ !
*CH
> Scroll to the "Set Terminal Characteristics" section of the file and where you see the "DZ0 line 0 as VT100 at 9600 baud" and the line above, make the following changes:
 set terminal kbg0:/permanent/noautobaud/speed=9600/device_type=VT100
 set terminal kbg1:/permanent/noautobaud/speed=9600/device_type=VT100
<repeat until you've setup all your lines>
 set terminal kbg63:/permanent/noautobaud/speed=9600/device_type=VT100
        ! DZV lines as VT-100 at 9600 baud
> Feel free to change the device type of KB0: to a VT100 if you wish.
> Return to EDT's line mode, and exit.
<Ctrl-Z>
*exit
START .COM 329 lines

$
> Replace the original START.COM in [0,1] with your modified START.COM:
$ COPY START.COM _SY:[0,1]START.COM
OK to replace existing file DR0:[0,1]START .COM ? YES
[File START .COM copied to [0,1]START .COM]
$
> Restart your RSTS/E system.
$ RUN $SHUTUP


Once the system is restarted, telnet into the DZV11 port, and you
should have working DZV11 lines. Personally however, I find that the
DHV11/DHQ11 is a much better terminal multiplexer. Especially since
modem control actually works on them from inside RSTS/E. And
consequently when you logoff or if your telnet disconnects when
connected to a DHV11/DHQ11 line setup as a "/DIALUP" line from RSTS/E,
the it will disconnect your telnet session (in the first case), or
automatically log you out (in the second case).



I feck around with RSTS/E *a lot* so feel free to bug me as much as you want.


Cheers,
Christian
-- 
Christian M. Gauger-Cosgrove
STCKON08DS0
Contact information available upon request.