Years ago, I was given an image of VMS 4.7. I only tested it for idle capabilities, and that is as far as I got with it. I never used it for anything else.
But today I needed to verify my Win32 Hecnet project works, so I needed to generate some legit DECNet traffic. Luckily I still have the VMS image, and in the prevailing years I managed to get a copy of PathWorks for Windows NT (And one for MS-DOS as well!).
So googling around, I found blinkenbone who mentions the command needed to setup some DECNet love. Now the one thing that is strange about DECNet is that the MAC address needs to be changed to the DECNet area & node id. Thankfully there is an online calculator, powerdog. Since I’m just testing, I’ll put my VAX in area 1, node 1, that means the VAX MAC needs to be set to:
So in SIMH, I just use the line:
set xq mac=AA-00-04-00-01-04
Cool. Now I use ansicon, in the hopes it’ll make the console better, and fire up VMS.
And then login as system/manager
Now I can setup decnet very simply like this:
Welcome to VAX/VMS version V4.7
Last interactive login on Saturday, 20-SEP-2008 17:32
DECnet-VAX network configuration procedure
This procedure will help you define the parameters needed to get DECnet
running on this machine. You will be shown the changes before they are
executed, in case you wish to perform them manually.
What do you want your DECnet node name to be? : rabbit
What do you want your DECnet address to be? : 1.1
Do you want to operate as a router? [NO (nonrouting)]:
Do you want a default DECnet account? [YES]:
Here are the commands necessary to setup your system.
$ RUN SYS$SYSTEM:NCP
PURGE KNOWN OBJECTS ALL
PURGE MODULE CONFIGURATOR KNOWN CIRCUITS ALL
$ DEFINE/USER SYS$OUTPUT NL:
$ DEFINE/USER SYS$ERROR NL:
$ RUN SYS$SYSTEM:NCP ! Remove existing entry, if any
PURGE NODE 1.1 ALL
PURGE NODE RABBIT ALL
$ RUN SYS$SYSTEM:NCP
DEFINE EXECUTOR ADDRESS 1.1 STATE ON
DEFINE EXECUTOR NAME RABBIT
DEFINE EXECUTOR MAXIMUM ADDRESS 1023
DEFINE EXECUTOR TYPE NONROUTING IV
DEFINE EXECUTOR NONPRIVILEGED USER DECNET
DEFINE EXECUTOR NONPRIVILEGED PASSWORD DECNET
$ DEFINE/USER_MODE SYSUAF SYS$SYSTEM:SYSUAF.DAT
$ RUN SYS$SYSTEM:AUTHORIZE
ADD DECNET /OWNER=”DECNET DEFAULT” –
/UIC=[376,376] /ACCOUNT=DECNET –
/DEVICE=SYS$SPECIFIC: /DIRECTORY=[DECNET] –
Press RETURN to continue
/FLAGS=(CAPTIVE) /LGICMD=NL: –
$ CREATE/DIRECTORY SYS$SPECIFIC:[DECNET] /OWNER=[376,376]
$ RUN SYS$SYSTEM:NCP
DEFINE LINE QNA-0 STATE ON
DEFINE CIRCUIT QNA-0 STATE ON COST 4
DEFINE LOGGING MONITOR STATE ON
DEFINE LOGGING MONITOR EVENTS 0.0-9
DEFINE LOGGING MONITOR EVENTS 2.0-1
DEFINE LOGGING MONITOR EVENTS 4.2-13,15-16,18-19
DEFINE LOGGING MONITOR EVENTS 5.0-18
DEFINE LOGGING MONITOR EVENTS 128.0-4
Do you want to go ahead and do it? [YES]:
%UAF-I-ADDMSG, user record successfully added
%UAF-I-RDBADDMSGU, identifier DECNET value: [000376,000376] added to RIGHTSLIST.
%UAF-I-DONEMSG, system authorization file modified
%UAF-I-RDBDONEMSG, rights database modified
%NCP-I-NMLRSP, listener response – Success
Logging sink type = monitor
%NML-I-RECADDED, Database entry added
The changes have been made.
If you have not already installed the DECnet-VAX license, then do so now.
After the license has been installed, you should invoke the procedure
SYS$MANAGER:STARTNET.COM to startup DECnet-VAX with these changes.
(If the license is already installed) Do you want DECnet started? [YES]:
%%%%%%%%%%% OPCOM 28-OCT-1987 15:42:37.64 %%%%%%%%%%%
Message from user DECNET
%RUN-S-PROC_ID, identification of created process is 00000109
%RUN-S-PROC_ID, identification of created process is 0000010B
%%%%%%%%%%% OPCOM 28-OCT-1987 15:42:42.67 %%%%%%%%%%%
Message from user DECNET
DECnet event 4.10, circuit up
From node 1.1 (RABBIT), 28-OCT-1987 15:42:37.69
It basically set itself up.
And on the Windows NT side, I simply set itself up as node 2 in area 1.
And now I can use CTERM to connect to the VAX.
Nice!. And it even works through my port of HECNet.
On reboots you have to manually start the network. I don’t have EDT, or I don’t know where to find it (remember the gold key? ugh).
But it’s a simple command:
And you are good to go!
Likewise shutting down is accomplished with this:
And that’s about all I know about VMS. But it’s good to see that configuring this was pain free!
I was just going to ask when you were going to do something on VMS. You read my mind. Uncanny.
Ha! I just uploaded my build of hecnet for win32… I’ll need to test this some more, but I may just go ahead to announce, and see if it lands with a thud.
“If you’re not familiar with it, OpenVMS was a partially successful communist plot to destroy the POSIX standard.” http://www.tedunangst.com/flak/post/worst-common-denominator-programming
lol sounds right. I barely could logon and check email @ school, then our vax was killed. later on I helped virtualize a VAX, then it too was killed. Too bad, as they were massive beasts. I wanted to put NetBSD on the 8600, and use it for a NTP server… but a hurricane blew out the buildings triple phase for it, and that was the end of that.
I know it’s kind of interesting that you can just link ASM, Cobol, Fortran and C together, but to be honest, I can’t figure out how to even link a simple C program..
Gee, now I know what all those DECNet options are for on my Shiva Fastpath router.. I bet I could count the number of people running DECNet over Localtalk with one hand…
I had some VAX access while in college, mostly to run assembly language programs. I don’t think they teach VAX ASM anymore since they finally retired that machine.
There is a big group of DEC refugee’s on over at hecnet. I think there is a few dozen.
I never really played with VAX/VMS outside of that class. Whats weird is that I seemed to have been exposed to many old mainframe systems over the years. In high school they were still teaching BASIC on a HP 3000… in 1996! They were taking advantage of the fact that they had one around running the school scheduling and student management system. There is a free eval copy of an emulator if I ever decided to brush off those freshman year programming assignments. 😛
IIRC: EDIT/EDT is the command. EDIT itself could also be EDT in that release.
Also: VMS would automatically change the MAC…so the address set on xq doesn’t really matter iirc.
At this point, I’m just logging in and testing my compressed bridge… what I need is a game on VMS or something, doing ‘dir’ is getting boring quick.
Also who do I talk to about joining HECnet? Since I can run the bridge on Windows now, I setup a Terminal server, bound decnet to a loopback interface, and running HECnetNT, I can connect to my SIMH VAX, but it’s a lonely world.
Email Johnny (bqt at softjar dot se, iirc. Could also email me or the list proper)
Any idea how I can configure Pathworks on Windows NT 4.0 to grant FAL access to remote VMS hosts? When I do NCP “DEFINE ACCESS DEFAULT READ”, OpenVMS remote hosts get back the entire c:\winnt\system32 directory for “DIR WINNTHOST::” – I want to force the default FAL to another directory. NCP “DEFINE ACCESS USER DEFAULT HOME C:\FAL” is not accepted as a command. Thank you.