Tag Archives: OpenVMS

OpenVMS: How to Fix %NCP-W-MIRCTF and %SYSTEM-F-NOSUCHNODE No Such Node errors

Whilst configuring an OpenVMS 7.3 (VAX) 2-node Cluster using DECnet Phase IV, I was unable to use commands such as SET HOST as nodename lookup was failing. Each node could “see itself”, as it were, but that was about it.

To resolve this, I first started by using NCP and ran a couple of LOOP NODE commands. The first to my local node TOM (which silently returns - i.e. loop is verified) and the second to remote node JERRY (which fails):

OK - let’s check the NODE database:

So, we can only see the EXECUTOR itself, TOM (with DECnet address 1.151). Using the SET NODE and DEFINE NODE commands, I added an entry for JERRY to the database on TOM:

A SHOW NODE now looks more promising:

Next, on JERRY, run NCP and copy the known nodes database down from TOM (1.151):

Great - we can see both nodes from both nodes. LOOP NODE will confirm this, but let’s try something cooler, a remote login with SET HOST:

From JERRY:

Excellent. Check the other direction with a SET HOST JERRY from TOM, and verify that all is well. The PHONE utility should now work too - bet you’re happy about that ;)

DECNet Phase IV Fails to Install on OpenVMS 7.3

During installation of OpenVMS 7.3 on a simulated VAXserver 3900 under SIMH, I selected the installation of DECnet Phase IV as follows:

The attempted installation of DECnet Phase IV fails, and the following system messages are generated:

First, let’s mount our OpenVMS media and see if we can locate the appropriate kit manually:

OK, we’ve found our kit. Let’s install it:

Confirm that the .PCSI file is in the current directory:

And install the kit:

Excellent - DECNet Phase IV is now correctly installed. You can proceed with applying your DECNet license PAKs (the LICENSE command), and configuration of DECNet as appropriate (@SYS$MANAGER:NETCONFIG.COM).

OpenVMS: How to Get TCP/IP to Start Automatically on Boot

After installing Compaq TCP/IP on my OpenVMS 7.3 SIMH image, TCP/IP was not starting when the node was rebooted.

To resolve this, I performed the following steps. First, ensure you have assumed your privileged identity (or just log in as SYSTEM):

Next, edit SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM:

Find the following line, and uncomment it (by removing the leading $! comment sequence):

Save and exit the editor (with Control-Z). Now, you can either reboot the node

or just start the services manually for now:

It’s worth noting that the following command will shut down TCP/IP:

It’s also worth noting that individual services can be restarted using the following format, just substitute TELNET for the service you wish to act upon: