| This would probably get a better response in HELP::DECNET-OSI_for_VMS
so you may want to ask there as well.
Generally, when you first installed DECnet-Plus (or DECnet/OSI) it tried to
discover a name server, and if it did there's probably little else you need to
do. As long as the EASYnet namespace is kept up-to-date (and it usually is),
there is no need to run any of the old command procedures you used to use to
keep your local copy of netnode_remote.dat current. The namespace does this
automagically.
Now, if when you installed, a local nameserver was not discovered, then you may
need to use the local file for names (the DECnet-Plus equiv of
netnode_remote.dat). Since I only maintain information about nodes I typically
use, the only utility I use to manage this is SYS$SYSTEM:DECNET_REGISTER.EXE - I
recall that there is a utility to take a netnode_remote.dat and populate the
local file, but I don't remember what it is offhand.
I think there's also some white papers floating around about how to
install/configure a node for use on the easynet, maybe someone who remembers
where these are hiding can post a pointer.
--Scott
|