In VMS 3.0,
NETCONFIG.com prompted me for an address in range 1..255. So that looks like
Phase III to me.
In VMS 3.5-3.7, I
NETCONFIG.COM prompted me for an address in range 1..1023, but no area
number. It also gave me errors when I tried bringing up the network interface. So, maybe
an earlier unrouted version of Phase IV?
In VMS 4.0,
NETCONFIG.COM prompted me for a Phase IV address. But when I started the
network, I got flooded with errors like:
%RUN-S-PROC_ID, identification of created process is 0000004A
$
%%%%%%%%%%% OPCOM 8-DEC-2021 19:23:45.49 %%%%%%%%%%%
Message from user DECNET
DECnet event 4.19, adjacency down, operator initiated
From node 2.617 (PUGGLE), 8-DEC-2021 19:23:45.49
Circuit UNA-0, Adjacent node address out of range
Packet beginning = 0B020000AA000400BB0A024F0240000A
So, Phase IV, but maybe buggy when exposed to my normal local DECNET traffic?
Finally, I tried VMS 4.7, and it seems to talk to my other nodes just fine. Yay! So I
guess the answer to my original question is something newer than 4.0, and no older than
4.7. Now I have node PUGGLE:: up and running on HECNET with VMS v4.7.
--
Mark J. Blair, NF6X <nf6x at nf6x.net>
https://www.nf6x.net/