HELPLIB.HLB  —  LICENSE  MODIFY  Qualifiers

1    /ADD

    Used with the /INCLUDE or /EXCLUDE qualifier, specifies that the
    node names provided are to be added to the previously established
    include or exclude lists.

    Used with the /RESERVE qualifier, specifies that the user
    names provided are to be added to the previously established
    reservation lists.

    When you use /ADD, you do not need to retype the entire list to
    add a new node name or user name.

2    /ALL

    Positional qualifier.

    Modifies all the licenses with the given product name. This
    qualifier affects only the product name that immediately precedes
    it in the command string.

3    /AUTHORIZATION

       /AUTHORIZATION=string

    Positional qualifier.

    Specifies a string that helps identify the license you want to
    modify. You must enter the authorization string exactly as it
    appears on your PAK. Use this optional qualifier only if you
    need it to identify the license. This qualifier affects only the
    product name that immediately precedes it in the command string.

4    /COMBINE

       /COMBINE
       /NOCOMBINE

    Modifies a PAK by adding or removing the COMBINE option. If the
    PAKs are combinable, LMF combines them during license loading.

5    /COMMENT

       /COMMENT=string

    Specifies a string of text. Use this comment field of up to 63
    characters to associate information for this transaction with
    the license. History records for the license retain this license
    information. If you specify more than one word, enclose the text
    in quotation marks (""). This qualifier is optional.

    The text in the comment field is replaced only when you enter new
    comments with another LICENSE MODIFY command. At this point the
    old comment text is available as a history record.

6    /DATABASE

       /DATABASE=filespec

    Specifies the location of the License Database. The default file
    specification is defined by the logical name LMF$LICENSE, which
    points to SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB on an unmodified
    OpenVMS system. Use this optional qualifier only if you do not
    use the default License Database name and location.

7    /EXCLUDE

       /EXCLUDE=(node-name[,node-name,...])

    Specifies that the named node or nodes in an OpenVMS Cluster
    environment cannot access the licensed product. The excluded
    nodes cannot load (with a LICENSE LOAD or LICENSE START command)
    the license registered in the License Database. Each node-name
    argument must be a System Communications Services (SCS) node
    name or a system parameter set with the System Generation utility
    (SYSGEN). The node name might not be the same as the DECnet node
    name. If you specify more than one node name, separate them with
    commas, and enclose the list in parentheses. This qualifier is
    optional.

    To modify previously defined lists without having to retype
    all of the node names, use the /ADD or /REMOVE qualifiers with
    /EXCLUDE.

    You can control license access to nodes with /EXCLUDE and control
    user access with /RESERVE, but you cannot use these qualifiers on
    the same command line. To use both types of control with the same
    license, you must enter separate LICENSE MODIFY commands.

8    /INCLUDE

       /INCLUDE=(node-name[,node-name,...])

    Specifies that the named node or nodes in an OpenVMS Cluster
    environment can access the licensed product. Only the included
    nodes can load (with a LICENSE LOAD or LICENSE START command)
    the license registered in the License Database. Each node-name
    argument must be an SCS node name, or a system parameter set with
    SYSGEN. The node name might not be the same as the DECnet node
    name.

    Licenses for the OpenVMS operating system usually specify the
    NO_SHARE option on their PAKs. In a cluster environment you must
    restrict each of these OpenVMS licenses to a single node. If
    you did not do this when registering with VMSLICENSE.COM, enter
    LICENSE MODIFY/INCLUDE=node-name, specifying one SCS node name
    for each OpenVMS license.

    To specify more than one SCS node name for a license that does
    not specify NO_SHARE, separate the names with commas, and enclose
    the list in parentheses. This qualifier is optional.

    To modify previously defined lists without having to retype
    all of the node names, use the /ADD or /REMOVE qualifiers with
    /INCLUDE.

    You can control license access to nodes with /INCLUDE and control
    user access with /RESERVE, but you cannot use these qualifiers on
    the same command line. To use both types of control with the same
    license, you must enter separate LICENSE MODIFY commands.

9    /ISSUER

       /ISSUER=string

    Positional qualifier.

    Specifies the name of the company (for example, DEC) that
    issued the PAK for the product. Use this qualifier only if it is
    required to identify the license. This qualifier affects only the
    product name that immediately precedes it in the command string.

10    /LOG

       /LOG
       /NOLOG (default)

    Controls whether LICENSE MODIFY displays the name of each license
    that it modifies.

11    /NO_SHARE

       /NO_SHARE
       /NONO_SHARE

    Specifies whether to add or subsequently remove /NO_SHARE from a
    PAK. Adding /NO_SHARE prevents the sharing of the PAK units with
    other cluster nodes.

    PAKs with /NO_SHARE require you to provide the SCS node name of
    the cluster node that will be using this particular license. See
    the /INCLUDE qualifier for more information.

    Note that if /NO_SHARE is present on your PAK when you register
    it, you cannot remove the option using /NONO_SHARE. Only if
    you add /NO_SHARE with the MODIFY command, can you subsequently
    remove it.

12    /PRODUCER

       /PRODUCER=string

    Positional qualifier.

    Specifies the name of the company (for example, DEC) that owns
    the product for which you have a license. Use this optional
    qualifier only if you need it to identify the license. This
    qualifier affects only the product name that immediately precedes
    it in the command string.

13    /REMOVE

    Used with the /INCLUDE or /EXCLUDE qualifier, specifies that
    the node names provided are to be removed from the previously
    established include or exclude lists.

    Used with the /RESERVE qualifier, specifies that the user names
    provided are to be removed from the previously established
    reservation lists.

    When you use /REMOVE, you do not need to retype the entire list
    to remove a node name or user name.

14    /RESERVE

       /RESERVE=(user-name[,user-name,...])

    Specifies that the license or licenses are to be reserved for use
    by the users listed in the user-name parameter. Users not listed
    are denied access to the product. The value applied to user-
    name differs from product to product. See your Software Product
    Description (SPD) for details.

    Most products define user-name to be the user name OpenVMS
    maintains for each account. This is the name you type at the
    Username prompt during login.

    If your PAK specifies the RESERVE_UNITS option, you must assign
    one or more users to a reservation list. On OpenVMS Alpha and VAX
    systems, 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. On
    OpenVMS Integrity server systems, units are expressed in single
    units that directly correlate to the constant value listed.

    You can also create and modify a reservation list for
    Availability and regular Activity Licenses that do not specify
    the RESERVE_UNITS option. Because these licenses do not limit
    the number of names on the list, you can assign as many names as
    you like to the reservation list. All users not on the list are
    denied access.

    Although you can control license access to nodes with /INCLUDE
    and /EXCLUDE qualifiers and control user access with the /RESERVE
    qualifier, you cannot use these qualifiers on the same command
    line. If you want to use both types of control with the same
    license, you must enter separate LICENSE MODIFY commands.

    Use the /ADD and /REMOVE qualifiers for further control in
    modifying previously established reservation lists.

15    /SELECTION_WEIGHT

       /SELECTION_WEIGHT=number

    Modifies the selection weight. Selection-weight values determine
    the order in which LMF checks multiple licenses when a product
    makes a license grant request. LMF checks higher-weighted
    licenses before lower-weighted ones. Specify arbitrary numbers
    between 1 and 1000.

                                   NOTE

       You cannot modify selection weights for Availability
       Licenses.

    To restore the selection weight of a PAK to the default value,
    enter the LICENSE MODIFY command with /SELECTION_WEIGHT=0. For
    example, you can use either of the following commands:

    $ LICENSE MODIFY FORTRAN /SELECTION_WEIGHT=0
    $ LICENSE MODIFY FORTRAN /NOSELECTION_WEIGHT

16    /TERMINATION_DATE

       /TERMINATION_DATE=date

    Date at which the product license is to be terminated. If
    your PAK supplied a license termination date, LMF uses the
    earliest date to determine the termination date. The date must
    be presented in the standard OpenVMS format: dd-mmm-yyyy. If
    you want to restrict a product from further use today, enter
    yesterday's date; LMF terminates the license at the end of the
    day specified.

17    /UNITS

       /UNITS=n

    Number of license units you want on a license that includes the
    MOD_UNITS option. If your PAK allows you to modify the license
    units, use this qualifier to change the value in the License
    Database.

18    /VIRTUAL

       /VIRTUAL
       /NOVIRTUAL

    Specifies that the modified license must only be loaded on
    OpenVMS guests. Virtual licenses are ignored during physical
    machine LICENSE LOAD command processing. To see the licenses
    that are ignored, use the /LOG qualifier with the LICENSE LOAD
    command. Use the /NOVIRTUAL qualifier to remove the virtual
    option from the license.

    The /VIRTUAL qualifier is valid for licenses with the IA64 and
    PCL options.

    Licenses that you intend to load on OpenVMS guest cluster members
    must be modified with the /VIRTUAL qualifier. It is optional,
    but recommended to modify licenses for standalone OpenVMS guest
    systems with the /VIRTUAL qualifier.

    VSI recommends that you use /INCLUDE or /EXCLUDE lists on your
    virtual machine host licenses to define all the OpenVMS guest
    cluster members from a host that must load the license. In
    future, VSI may limit the usage of a Virtual license to one host,
    which is the first host that loads the license.
Close Help