HP OpenVMS Systems

ask the wizard
Content starts here

Finding cause of unauthorized license error?

» close window

The Question is:

when the system reboots, the console gets a message from the lmf ultility
 saying the license can't be loaded - "license not authorized for this node"
 referring to the openvms alpha license.  There are old licenses for other
 nodes (with the include stateme
nt on them) but they seem to all be disabled.  There are two licenses with the
 proper nodename combined and loaded on the system.  How can I get rid of the
 console message on reboot?  Why is the system trying to load the vmslicense
 for a node that is not
in the /include statement? How can I stop it?

The Answer is :

  The initial diagnostic would involve the DCL command:
  This from a privileged username, of course.  Does the error occur?
  Additional commands which can be used to debug licensing-related
  problems include the LMF logical name referenced in the OpenVMS
  FAQ and in the attached information, as well as the various LMF
  commands including:
  This command will list all PAK's that are in the License DataBase
  (.LDB).  These licenses may or may not have been loaded into the
  in-memory license database.
  This command shows all activity that has been performed on the
  License DataBase.  This can be very helpful in determining if
  there are problems that may be local and specifically may be
  a result of LMF-related commands entered on the system.
  This information can help you diagnose a problem where the system
  is short of units, and can also point to additional considerations.
  As one brute-force approach for finding the offending license(s)
  involved here, boot the system minimally and then start and load
  the licensing manually using the (privileged) LICENSE START/LOG
  The following is from the HELP files:
Displays information in the License Unit Requirement Table (LURT). The
/UNIT_REQUIREMENTS qualifier is incompatible with the product-name
parameter and with the /BRIEF and /PRODUCER qualifiers.
Use with the /UNIT_REQUIREMENTS qualifier to display the license unit
requirements for every node in an OpenVMS Cluster.
Tells you how many license units are loaded, how many are currently
allocated, and how many are currently available, as well as the license
type for each product on the system. Use with the /FULL qualifier to
display complete information-including the PID, process name, node, or
user name-for each instance of use of the product. You need group
privilege to see the list of users in your group who have allocated
license units; you need world privilege to see the list of users in all
In an OpenVMS Cluster, if you own multiple license types for a single
product, you are limited to viewing the usage information for the
license type loaded on the node from which you are executing the SHOW
LICENSE/USAGE command. To find out the usage of the other license type
loaded on another node, issue the command on that node. You can also use
the System Management (SYSMAN) utility to do this.
In an OpenVMS Cluster, usage information is limited to the local license
type. For example, VAX and Alpha availability licenses are considered by
LMF to be different license types. If you are running both VAX and Alpha
systems in a cluster, usage information for availability licenses is
limited to the local system type. For example, if you have DEC C
installed on all nodes in your OpenVMS Cluster, you can display DEC C
license allocation on all the VAX nodes in the cluster from any VAX node
with DEC C installed, but you cannot display the DEC C license
allocation on the Alpha nodes.
Usage information is not available for unlimited licenses (a license
with 0 units). Clusterwide usage information is not available for
personal use or NO_SHARE licenses. Refer to the OpenVMS License
Management Utility Manual for more information on license types.
Define the LMF$DISPLAY_OPCOM_MESSAGE logical name if you want to DEBUG
licensing.  This command will provide additional information on the
status of licensing and failures that may occur by outputting messages
using the OPCOM process.
The messages that are output are DEBUGGING in nature and may look like a
failure is occurring when one is not actually occurring, but is expected
To see if this logical name has been defined on your system, enter the
following command:
To turn on this feature, enter the following command:
To delete the logical name, enter the following command:

answer written or last revised on ( 16-NOV-2002 )

» close window