How do I add the /NODECNET qualifier to initialization of SE interfaces?
When configuring multiple interfaces, add the /NODECNET qualifier to interfaces that are NOT running DECnet. The /DECNET (or /NODECNET) only comes into play when MultiNet is started *before* DECnet. If DECnet is started first, the interface gets the new “hardware” address assigned by DECnet (AA-blah). MultiNet then comes along and uses that address for the interface. With the /NODECNET qualifier on the interface, it will use the PROM address if DECnet was not started on that interface. However, if MultiNet starts first, by default, it uses /DECNET, which means it calculates the same “AA-blah” address that DECnet will use. If you specify /NODECNET, it uses the PROM address. If the PROM address is used, DECnet can not run on that interface once MultiNet has been started. Customers using /NODECNET but starting DECnet first are going to have no problem. How to enable your applications that are designed to execute over DECNET to execute over TCP/IP instead. If your OpenVMS systems are all r