Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How do I add the /NODECNET qualifier to initialization of SE interfaces?

0
Posted

How do I add the /NODECNET qualifier to initialization of SE interfaces?

0

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

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123