PMDF System Manager's Guide

If the error message "Usage level requires PMDF-MTA service" is reported by PMDF components, then a PMDF-ACCESS license is loaded on a system that has a PMDF-MTA configuration, that is, a configuration including channels not allowed on a PMDF-ACCESS system.

If this system is supposed to be a PMDF-ACCESS system, then the problem is that the PMDF configuration has non-ACCESS, disallowed components in it. Either manually modify the PMDF configuration file to remove non-ACCESS channels, or use the PMDF CONFIGURE ACCESS utility to generate a new PMDF-ACCESS configuration.

If this system is supposed to be a PMDF-MTA system rather than a PMDF-ACCESS system, then the problem is that a PMDF-ACCESS license has been loaded instead of or in addition to a PMDF-MTA license. Note that the (lesser functionality) PMDF-ACCESS license will override the PMDF-MTA license; you must remove the PMDF-ACCESS license in order for the PMDF-MTA license to take effect. The

$ PMDF LICENSE UNLOAD

command should be used to ensure that PMDF's own bundle license accounting is not counting this system as a PMDF-ACCESS node. Then the DCL LICENSE command should also be used to ensure that the PMDF-ACCESS license has not been loaded by OpenVMS' own license accounting; note that the LICENSE MODIFY/EXCLUDE or LICENSE MODIFY/INCLUDE commands are useful in a cluster setup to ensure that the proper licenses are loaded only on the proper nodes.