Use the LICENSE MODIFY command to modify a license. To control
    which nodes in a cluster environment have access to what
    software, use LICENSE MODIFY with the /INCLUDE or /EXCLUDE
    qualifier. For example, you can load licenses for products used
    less often or requiring limited access on one node.

    If you do not specify which nodes can load a license (with a
    LICENSE LOAD or LICENSE START command), LMF loads a license
    on a first-come, first-served basis. When your license has
    insufficient license units for full cluster environment use,
    control product access with an include list.

    Because most OpenVMS PAKs use the /NO_SHARE option, in a cluster
    environment you must restrict these operating system licenses to
    one node. Enter LICENSE MODIFY/INCLUDE=node-name, specifying only
    one SCS node name for each OpenVMS license.

    To control which users have access to a product, use LICENSE
    MODIFY with the /RESERVE qualifier. You can create and modify
    a reservation list for any kind of license. Only users on the
    reservation lists are allowed access to the product.

    If your PAK specifies the RESERVE_UNITS option, you must assign
    one or more users to a reservation list. The number of user
    names allowed per list depends on the number of activity units
    available and a constant value or the License Unit Requirement
    Tables (LURTs). Calculate this number as you would for any
    Activity License. For example, a 200-unit license with a constant
    value of 100 is a two-user license.

    Use the /ADD and /REMOVE qualifiers in conjunction with the
    /INCLUDE, /EXCLUDE, and /RESERVE qualifiers when you modify
    existing include, exclude, and reservation lists.

    To add comments about a license in the License Database, use
    LICENSE MODIFY with the /COMMENT qualifier.

    If your PAK includes the MOD_UNITS option, you can use the /UNITS
    qualifier to specify the number of license units you want for
    your registered license.

    Use the other LICENSE MODIFY command qualifiers only as needed to
    identify the correct license.

    You can also modify a license record using the VMSLICENSE.COM
    command procedure.

    List Size Restrictions

    Two restrictions apply to the size of lists (reservation lists,
    include lists, or exclude lists). These restrictions apply to
    PAKs of all license types.

    o  On any single PAK, the sum of characters contained in all
       lists must not exceed 5000 characters.

       Because the length of names varies and some overhead is
       used for each name, this 5000-character limit cannot be
       expressed as an exact number of permissible names. However,
       VSI guarantees that at least 400 names, in total, can be
       specified in the various types of lists. For example, each
       of the following represents the minimally guaranteed number of
       names:

       -  Reservation list with up to 400 user names

       -  Reservation list with up to 200 user names plus an include
          list with up to 200 node names (totaling up to 400)

       -  Reservation list with up to 200 user names plus an exclude
          list with up to 200 node names (totaling up to 400)

       -  Include list with up to 400 node names

       -  Exclude list with up to 400 node names

                                      NOTE

          If you enter more names than are permitted, LICENSE LIST
          might not be able to display all names entered. In this
          case, you receive the error message LICENSE-F-CORRUP.
          However, the License Database is not actually corrupt,
          and the PAKs can still be loaded into memory (though the
          names are not displayed).

    o  The LICENSE LOAD and LICENSE START commands can load into
       memory a reservation list with no more than 30,000 characters.
       (Include and exclude lists, which are not loaded into memory,
       are irrelevant to the 30,000-character limit.)

       Because the length of names varies and some overhead is used
       for each name, this 30,000-character limit cannot be expressed
       as an exact number of permissible names. But VSI guarantees
       that, for each product, at least 2000 user names can appear on
       reservation lists. In the case of an OpenVMS Cluster, this is
       a per-node limit.

       Note that, because 2000 user names is a per-product limit and
       because there can be more than one PAK per product, the number
       of user names on a per-product basis is the sum of the user
       names specified on each PAK.

       For example, if three activity PAKs for the DECwrite
       product were registered on a system and each PAK specified
       a reservation list with 200 user names, the total number of
       user names for that product is 600. This is safely below the
       30,000-character (2000 user name) limit and below the 5000-
       character (400 user name) limit.