[Info-vax] VAXStation 3100
Bill Gunshannon
bill.gunshannon at gmail.com
Sat Jan 19 12:35:27 EST 2019
On 1/19/19 3:29 AM, Dave Froble wrote:
> On 1/18/2019 8:17 PM, Bill Gunshannon wrote:
>> On 1/18/19 7:35 PM, Dave Froble wrote:
>
>>> And I have to ask, are you ocnfusing DECnet with LAT? Two totally
>>> separate things.
>>
>> Yes, but I thought LAT was a subset of DECNET. Guess I was wrong.
>> So, does VMS still support connections via LAT?
>
> No, LAT is a totally separate thing.
>
>>> Perhaps the non-VMS DECnet stuff you have has had additions that never
>>> existed on VMS?
>>
>> Not as far as I know. It was done from the published DEC
>> protocol docs. I know it works with my DECServer 200 so I
>> can login to the other boxes from a terminal connected to
>> it. Hmmmm... Maybe that's a solution. I wonder if I can
>> connect to the VMS box from the DECServer? That would
>> provide buffering and flow control.
>
> If you have a working DECserver 200, then things get real simple.
>
> Well, maybe ....
>
> I confess, I've never really been a system manager. I used to know
> enough to manage my own systems, and in the dim past I used to know
> enough to set up customer systems.
>
> I don't remember if you have to do anything other than start up LAT,
> LAT$SYSTARTUP.COM, which should be part of system startup, and perhaps
> have a MOP download to the terminal server, which means you need the
> terminal server software.
>
> I set up my current systems so long ago that I seem to forget just about
> everything.
>
> NCP CONNECT NODE SRVR3
>
> Got me to a # prompt, and I have forgotten the access password, wait,
> that's it I think, ACCESS.
>
> With a connection to the terminal server you can set up each port. You
> can set up an automatic (default) connection to the VMS system on each
> port.
>
> I'm sitting here in the middle of the night, aghast at how much I don't
> remember. This is distressing.
>
> But, perhaps it shows how good DEC gear and VMS is, since it's been
> running for maybe 20 years without any management. Or not much.
>
> If you need details, ask, me, I'm going to maybe spend the weekend
> jogging some old memories.
>
> Maybe I'll fire up one of the older systems, install V7.3, and do the
> rest of the set-up. Might be fun, jog my memory, and it's suppose to
> snow anyway, what else is there to do?
>
Was much easier than that. I found a mention of
SYS$STARTUP:LAT$STARTUP.COM on a website so I ran it.
$ llogin -d
HOME1 Available Welcome to OpenVMS (TM) VAX
Operating System, Version V7.3
MINECRAFT Available Linux 4.15.0-43-generic
SPARKY Available FreeBSD 10.1-RELEASE
There it is, right at the top of the list. Was able to connect
to it from my Unix systems and from the DECServer. I used the
method offered to bootstrap Kermit as my setup:
set terminal /ttsync /hostsync
create 2019PAK.COM
and then just used cut&paste to send it on its merry way.
^Z at the end and @2019PAK and now I have all my licenses
loaded (confirmed with SHOW LICENSE).
Now on to loading stuff and then I can get on with the
real fun.
A couple more quick questions, though.
I saw no PAK for it so is there no RGP I or RPG II for
VMS? It's another language I haven't used for ages and
would have liked to play with again. And what about APL?
Does Multinet still have a Hobbyist license? What about
the former Kednos? PL/I?
I wonder if BLISS-11 is still around anywhere? Freeware?
Thanks for all the help. Next big step will be to hang
a stack of RZ1DB's off the back of this thing. :-)
Don't worry, I'll be back with even more questions
probably.
bill
More information about the Info-vax
mailing list