The LICENSE LOAD command loads licenses registered in the License
    Database. To use a licensed product, ensure that the system
    loads the registered license. When you register a license with
    VMSLICENSE.COM, you can confirm an option to load the license,
    whereas if you register a license with LICENSE REGISTER, you must
    also load it with LICENSE LOAD.

    Use LICENSE LOAD only after you register a new license; LMF
    automatically loads all registered licenses at each subsequent
    system startup. You can enter LICENSE LOAD at other times to load
    modifications made with other LICENSE commands.

    You can enter one LICENSE LOAD command without product-name to
    load all the available registered licenses.

                                   NOTE

       Registered licenses are enabled for loading by default.
       You can, however, disable a registered license to prevent
       loading.

    A LICENSE START command entered interactively or when the system
    reboots also loads all licenses that are registered and enabled.

    If you register multiple licenses for a single product, LICENSE
    LOAD loads all of the matching licenses. You do not typically
    load individual licenses, and you cannot unload individual
    licenses for a product. The Availability, Activity, Personal Use,
    and User license units of the multiple licenses work in concert
    to provide more product availability.

    In an OpenVMS Cluster environment, each system loads licenses
    when it reboots. If you need to load a license for all assigned
    nodes of a running cluster, you can do one of the following:

    o  Log in to each OpenVMS Cluster node, and enter LICENSE LOAD.

    o  Invoke the OpenVMS SYSMAN utility to execute the LICENSE
       LOAD command on the desired OpenVMS Cluster nodes. See the
       HP OpenVMS System Manager's Manual for details on defining
       your management environment and executing commands on a list
       of nodes.

    A LICENSE LOAD command can fail, sending a message to the
    operator communication manager (OPCOM) for any of the following
    reasons:

    o  Insufficient license units are registered for the current
       node.

    o  The current date is later than the license termination date.

    o  A license checksum does not match the rest of the license
       data. Check for data corruption in the License Database.

    If you attempt to load a disabled license or a license modified
    to exclude the current node in an OpenVMS Cluster environment,
    OPCOM does not display an error message.

    If licenses for more than one product are being loaded, LICENSE
    LOAD continues with the next license following a failure.