9 Dec
2021
9 Dec
'21
9:30 p.m.
On Dec 9, 2021, at 4:09 AM, Johnny Billquist <bqt
at softjar.se> wrote:
I suspect you might get even 3.5 working. But you need to go into NCP and change a
thing.
At least with RSX, you have a parameter that tells which is the highest node number it
should handle, and if you see, or configure, a number higher than that, you'll get
some kind of error similar to what you have described above.
In RSX, this is the EXECUTOR parameter MAXIMUM ADDRESS. Check if you don't have that
one, and what it's set to in 3.5, 3.7 and 4.0.
You might also want to check for MAXIMUM AREA while you're at it...
That was the clue I needed. Thank you!
$ mc ncp
NCP>DEFINE EXECUTOR MAXIMUM ADDRESS 1023
NCP>EXIT
I think I didn't see MAXIMUM AREA in 3.7, but it appears in NCP later on.
Username: SYSTEM
Password:
Welcome to VAX/VMS version V3.7
$ @startnet
%RUN-S-PROC_ID, identification of created process is 0001000E
%OPCOM, 9-DEC-2021 11:59:04.72, message from user DECNET
DECnet starting
%RUN-S-PROC_ID, identification of created process is 0001000C
$
%OPCOM, 9-DEC-2021 11:59:08.44, message from user DECNET
DECnet event 4.10, circuit up
From node 2.616 (PUG), 9-DEC-2021 11:59:06.44
Circuit UNA-0
$
%OPCOM, 9-DEC-2021 11:59:08.44, message from user DECNET
DECnet event 4.15, adjacency up
From node 2.616 (PUG), 9-DEC-2021 11:59:06.73
Circuit UNA-0, Adjacent node = 2.698
--
Mark J. Blair, NF6X <nf6x at nf6x.net>
https://www.nf6x.net/
DOGPAK::MBLAIR