HECnet nodename management

This page briefly explains how you update your hosts DECnet nodename database if you are connected to HECnet. It goes through the steps for each OS/system separately.

First of all, the source of all nodename information resides on MIM::, which have node number 1.13. If MIM is not known on your system, start by defining this in DECnet if needed.
   
RSX: In RSX, there is a tool called NNC which copies definitions from another node. Copy over MIM::HECNET:NNC.BAT which is a batch file you can use which does all the work of importing the latest definitions from MIM and updating your local system. All you need to do is just "SUBMIT NNC.BAT" and you are done.
VMS:
Phase IV: the node copy capability is build into NCP. All you need to do is: "NCP COPY KNOWN NODES FROM MIM TO BOTH" and you are done.
Phase V: copy over FIX.PHV and run it, or just directly run it from MIM like this: "@MIM::HECNET:FIX.PHV"
DECdns: If you run DECdns, grab FIX.IMP, and run it with whatever tool is used to manage this (sorry that I can't help more, I don't really have any experience with DECdns).
TOPS-20: Grab MIM::HECNET:FIX.T20 and run in in the NCP submode of OPR (if I remember the setup correctly).
RSTS/E: Grab MIM::HECNET:FIX.RST, and run it with "@FIX.RST".
PyDECnet: Fetch hecnet.dat by doing "wget http://mim.softjar.se/hecnet.dat". Place that where you have configured PyDECnet to get the nodenames from, make sure your PyDECnet.conf file contains node @hecnet.dat, and restart PyDECnet in order for it to use the new nodenames.

If you want a new node added to the nodename database, send a mail to bqt@mim.softjar.se and provide the following information: