VSI 8.4 on FREEAXP

  • Post author:
  • Post category:OpenVMS

The next step….

Windows 10
FreeAXP 4.0.0.653 with OpenVPN-2.5.0-I601-amd64.msi
OpenVMS8.4 -2L2

You know how to install Windows10
You can find here how to install FreeAXp and the extra NIC.

After you have got this all installed it is time to install OpenVMS 8.4

My default setup;
dka0 – cdrom (iso file)
dka100 – System disk (rz27)
dka200 – Data/user disk (rz27)

After the initial installation:

$ start/queu/manager/new

$ set def sys$system
$ mc authorize
UAF> create/proxy

$ @sys$manager:net$configure advanced
configure DECnet
If you’ve configured everything the right way and started the network it is easy to check if everything is ok
$ set host 0
and if you have another node running
$ set host 1.1 (or whatever address the node that is already running has)

$ edit sys$startup:NET$DTSS_CLERK_STARTUP.NCL
!ENABLE DTSS SET CLOCK TRUE
ctrl-z

Always nice to have a Batchqueue
$ init/queu/batch/autostart_on=(“nodename”::) sys$batch

Now initialise & mount the DATA/User disk
$ INITIALIZE /STRUCTURE_LEVEL=5 DKA200: DATA
$ mount/system dka200 data disk200

$ reboot
check the output on your screen
I forgot to use SYMAN to have the sys$system:startup.log configured. This is a nice way to see if there are any problems during startup.
$ mc sysman
SYSMAN> startup set options/output=file/check

Next; TCPIP
$ @sys$manager:tcpip$config
My guess is you know how to do this.

After I started the network it is time for an interesting topic in this file;
Terminal Emulation!
I work on a MacBook Air and my favourite terminal emulation program is iTerm2

And just like the previous time I ended up with an OpenVMS node unwilling to communicate. So I decided to switch back to version 3.0.0.617. Installed it, booted the node and everything communicates again. Weird.