Changing license

[Duncan Morris]

You have V5.0 of DECnet Phase IV - the classic form of DECnet. This is the correct version for your version of VMS.

DECnet Phase V was a much later product (around VMS V5.5 timescale).

[Rickard_A]

Thanks for the reply. I Assumed that it was phase V.

[John Gillings]

If this is a cluster, it could be misconfigured, so the PAK has been registered in the LDB, but not available to be loaded by this node.

Try $ SHOW LICENSE/USAGE/FULL from each node in the cluster.

If you want to find out exactly which product is being requested, do the following:

$ REPLY/ENABLE=LICENSE
$ DEFINE/SYSTEM/EXEC LMF$DISPLAY_OPCOM_MESSAGE TRUE

Then repeat the failing command. You should see a sequence of OPCOM messages naming the products requested.

You should also check the LMF group table to see if you have any applicable group PAKs.

$ SEARCH SYS$UPDATE:VMSINSTAL_LMFGROUPS.COM

[John Gillings]

Sorry, forgot to mention...

Don't leave LMF$DISPLAY_OPCOM_MESSAGE defined. S
ome products can be authorized by multiple product names (for example DVNETEND and DVNETRTG). Those products will probe the LDB in some sequence. If a request fails, it will try another. LMF$DISPLAY_OPCOM_MESSAGE will cause a message to be issued for each unsuccessful probe, which means you may see false alarms. It should only be used for debugging.

[Rickard_A]

It worked out. It was set to be routing without the right license for routing.

[Rickard_A]

It worked out. It was set to be routing without the right license for routing.