Re: terminal server for vax?

In message <e28rah$hou$1@xxxxxxxxxxxxxxxxx>
legalize+jeeves@xxxxxxxxxxxxxxxxx (Richard) wrote:

[Please do not mail me a copy of your followup]

In article <sZO1g.6590$po3.2201@xxxxxxxxxxxxxxxx> you write:

<snip>
Can the DECserver models provide LAT connectivity, or do you need to
get a different box for that? I am under the impression that VMS has
LAT support builtin on the host side.

If I recall correctly, all Devcservers did LAT - some (most) also did
TCP/IP

I looked at the DECserver 90 manual which is what gave me the idea for
buying some sort of terminal connectivity to my VAX. They mention
installation of software in the manual, but I didn't drill deep enough
to know if this was software installed on the 90 itself or on a host.
Is there some sort of host software that must be installed in order
to service these serial ports via the terminal server as distinct login
sessions? I am not familiar with how VMS handles this and while my VAX
has OpenVMS installed, I am a complete newbie to VMS :-).

You need to use a program called LATCP to set up LAT services on VMS.
I think it was add-on software in some VMS versions, and built in on
later ones. It's been a few years since I did this stuff
unfortunately...

I know in *nix they did something like associate the login program
with the serial device. So you would get a login by pressing RETURN
on the terminal. I vaguely recall using a LAT server in 1989 to which
you had to request connection to a particular host and then you got a
telnet type login session. ISTR that you could have the terminal
connected to multiple hosts via the LAT and could switch back and
forth. Was specific terminal support required for this to work? I
only did this with a VT220, so I don't know if it was exploiting
something that was present only in DEC terminals.

LAT Terminal servers can be set up with a dedicated connection on a
port, so pressing <return> will connect you. VMS can then be set up do
log you in using a predetermined user, if your physical security
environment is good enough to allow this. Otherwise you get the usual
username and password prompts.

You can also have a preferred service, so typing Connect will connect
to that service, but you can type Connect <name> to choose a different
one.

Then there's reverse LAT, for printers etc. Pretty versatile.

Oh, and most will do all sorts of similar tricks with TCP/IP.

Be aware that LAT isn't routable, so it's pretty much confined to a
LAN.



--
Alan Adams, from Northamptonshire
alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.nckc.org.uk/
.

Relevant Pages

  • Re: Copy of SuperLat
    ... Your environment's net-folks still tolerate LAT? ... }Unfortunatley it's the only route possible for our clinet with his VMS ... }for sending and managing printing jobs to LAT ports directly. ... $ latcp:= $ latcp ...
    (comp.os.vms)
  • Re: LAT to SSH(or Telnet even) tunnel?
    ... RSTS/E that has no form of TCP/IP available, only LAT and DECnet, and I ... want to make it available via SSH connection through the VMS system. ...
    (comp.os.vms)
  • Re: LAT to SSH(or Telnet even) tunnel?
    ... RSTS/E that has no form of TCP/IP available, only LAT and DECnet, and I ... want to make it available via SSH connection through the VMS system. ...
    (comp.os.vms)
  • LAT ping? or, how do I run a DCPS queue to an LN17PS if LAT doesnt work
    ... It's accessed from both VMS and Windows. ... It has both a LAT ... one point telnet to it (although it's now refusing connections). ... The DCPS queue is set up to talk to the LN17PS via LAT, ...
    (comp.os.vms)
  • Re: VMS with BULL terminals
    ... Now I want to connect to a VMS ... | output of the host scrolls only in this single line. ... | One DEC VT510 in VT220 emulation mode, working as the system console, ... the DEC terminals, so incompatibility often is revealed by them. ...
    (comp.unix.misc)