[Info-vax] VAXStation 3100

Hans Bachner hans at bachner.priv.at
Sat Jan 19 13:49:15 EST 2019


Bill Gunshannon schrieb am 19.01.2019 um 00:43:
> On 1/18/19 6:06 PM, Dave Froble wrote:
>> On 1/18/2019 2:24 PM, Bill Gunshannon wrote:
>>> On 1/18/19 12:26 PM, Dave Froble wrote:
>>>> On 1/18/2019 9:28 AM, Bill Gunshannon wrote:
>>>>> [...]
>>>>>
>>>>> I have DECNET running.  I have LAT running on two of my
>>>>> Unix boxes and somehow they advertise their availability.
>>>>> How can I get VMS to do that?

If incoming connections are enabled, VMS should advertise the service 
(at startup and, iirc, once per minute).

What does
$ mc latcp show node
tell you?

$ mc latcp show service
will tell you, which other services the VMS node can see. Give it at 
least a minute after starting LAT until the routine service 
announcements of the other nodes have been seen.

>>>>> I tried moving my PAKs
>>>>> over OPA0: but that was a dismal failure.  Overrun after
>>>>> no more than 2 lines.  Wold like to just use DECNET to
>>>>> move them and then get on from there but I can't figure
>>>>> out how to let the other boxes know the VMS systems is
>>>>> there.
 >>>>>
>>>> Where do you currently have the PAKs?
>>>
>>> On other machines like where I get m y email and where I am
>>> running my terminal emulator.
>>
>> If I had no other option, I'd bring up the data (text) in a window,
>> such as Notepad, cut, paste into a VMS session with EDT running, and
>> when ready just exit EDT, thus having the text on the VMS system.
>
> Tried the old cut&paste.  I get no more than 2 1/2 lines before
> I start getting data overruns.  At that rate I might just as
> well hand type the whole file in (and that is not going to happen!!)
> It's going to be DECNET, TCPIP or Kermit first.

I believe there is a system parameter to increase the buffer size of the 
terminal driver but I can't remember which it was. Maybe TTY_TYPAHDSZ?

I usually can work around this problem by not pasting directly to the 
command line, but invoke EDIT /TPU (or EDT) and paste into the editor 
window. Save the buffer as a .COM file and execute it. You only need the 
VMS PAK and one of the NET_APP_SUP_200/300 PAKs to get the node 
accessible over the network; then copy the rest via COPY over DECnet or 
with FTP. The NET_APP_SUP_200/300 PAKs include DECnet, TCP/IP (UCX), 
VMSCLUSTER. DECwindows, and probably a few others. The NET_APP_SUP_250 
is similar, but includes only client functionality at least for TCP/IP 
and VMSCLUSTER.

>>
>>>> While DECnet can be very useful, it's not so much with other than VMS
>>>> systems.  You should get TCP/IP running, and then it's as simple as
>>>> using FTP.
>>>
>>> Probably true, but I  have DECNET running and other machines
>>> also have DECNET running and can talk with each other but
>>> none of them can see the VMS machine.  I was hoping it was
>>> a simple command that would cause it to do whatever the
>>> others are doing (from a protocol standpoint) and become
>>> publicly visible.
>>
>> I'm not sure what you are looking for, "publicly visible".
>
> % llogin -d
> MINECRAFT                   Available    Linux 4.15.0-43-generic
> SPARKY                      Available    FreeBSD 10.1-RELEASE
>
> % llogin MINECRAFT
> Ubuntu 18.04.1 LTS
> MineCraft login: bill
> Password:
> Last login: Wed Jan 16 10:02:14 EST 2019 on pts/6
> Welcome to Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-43-generic x86_64)
>
> %
>
>
>>
>> To know about other DECnet nodes, one would use NCP and set them up as
>> "known nodes".

There is no such mechanism for LAT as it is a LAN only protocol, not 
routable and finding other nodes via the MAC address learned from 
service announcements.

> As I said, these appear to broadcast their presence but VMS neither
> sends or listens for these broadcasts as far as I can tell.
>
>>
>> To access other nodes over DECnet one might set up proxys in the
>> AUTHORIZE program.

That's not a requirement - Proxies only allow you to omit access strings 
(username/password) in a node specification.

You always can $ SET HOST without any proxy definitions.

> Just seems odd that the packet type exists but VMS doesn't
> use it.  Unless it used to bu now, for security reasons, it
> no longer does.

They still are used (see above).

Hope this helps,
Hans.



More information about the Info-vax mailing list