VMS Help  —  LICENSE
    The License Management utility (LICENSE) is a DCL-level interface
    to the License Management Facility (LMF). LMF provides tools for
    managing software license information in the License Database
    and controlling the loading of licenses registered there. This
    database is located in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB.

    Most HP software products require license registration as part
    of the normal product installation before users can access the
    product. The LICENSE commands are:

    LICENSE COPY       LICENSE LOAD
    LICENSE CREATE     LICENSE MODIFY
    LICENSE DELETE     LICENSE MOVE
    LICENSE DISABLE    LICENSE REGISTER
    LICENSE ENABLE     LICENSE START
    LICENSE ISSUE      LICENSE UNLOAD
    LICENSE LIST       SHOW LICENSE

1  –  Usage Summary

 To use the License Management utility (LICENSE), enter a LICENSE
 command and subcommand at the DCL prompt ($).  For example, you can
 enter short commands on one line:
    $ LICENSE LIST /FULL VAX-VMS /AUTHORIZATION=USA12345

    Or you can enter long command strings followed by a hyphen (-)
    before pressing Return each time:

    $ LICENSE REGISTER FORTRAN /ISSUER=DEC /AUTHORIZATION=USA-1957 -
    _$ /PRODUCER=DEC /UNITS=1200 /VERSION=7.0 -
    _$ /AVAILABILITY=F /CHECKSUM=1-GEAD-MIDJ-IDNC-DLAC

                                   NOTE

       Enter the LICENSE commands carefully. LICENSE command
       strings can be long. If so, type a hyphen (-) at the end
       of a screen line to continue entering the same command.

       LMF may return only a checksum error when you omit or
       incorrectly enter information. Therefore, before you press
       Return, carefully check the characters you typed on each
       line.

       For most of the LICENSE commands, you can eliminate
       some typing by using the command procedure
       SYS$UPDATE:VMSLICENSE.COM

    All the LICENSE commands except LICENSE START, LICENSE LOAD, and
    LICENSE UNLOAD manipulate only the LMF databases. Thus, to enter
    most LICENSE commands, you need only the privileges required
    to access the License Databases. The License Database is file-
    based; normal file protection applies. LMF provides the License
    Database with a default file access of read and write privileges
    to system-level processes (S:RW).

    To enter the LICENSE START, LICENSE LOAD, and LICENSE UNLOAD
    commands, you need the privilege to change mode to kernel
    (CMKRNL) and to create system logical names (SYSNAM) and system
    privileges (SYSPRV).

    Some commands change license record fields in the License
    Database. LMF writes a history record when you use the following
    commands:

       LICENSE AMEND
       LICENSE COPY
       LICENSE DISABLE
       LICENSE ENABLE
       LICENSE ISSUE
       LICENSE MODIFY

    To display a listing of current and history records of licenses
    registered in the License Database, use LICENSE LIST. To display
    the licenses active on the current node, use the DCL command SHOW
    LICENSE.

    In some special circumstances, OpenVMS licenses are in a separate
    License Database located in SYS$SPECIFIC:[SYSEXE]LMF$SYSTEM.LDB.
    Your LICENSE commands must identify this database with the
    /DATABASE qualifier.

    Many of the LICENSE commands can affect more than one license
    simultaneously. You can control which licenses a command
    affects by adding more than one product name in the product-
    name parameter, using the /ALL qualifier, or using the standard
    DCL wildcard characters (* and %) in your command strings. Using
    the wildcard character (*) in the product-name parameter implies
    the use of /ALL.

    Many of the qualifiers are positional, allowing further control
    for the management of large License Databases. With multiple
    parameters, positional qualifiers affect only the preceding
    parameter. A positional qualifier that precedes every parameter,
    however, affects them all equally.

2  –  COPY

    Copies licenses from one License Database to another. When you
    use LICENSE COPY, LMF disables the source license and registers
    a copy in the destination License Database as if it were a new
    license. If the terms and conditions of your license contract
    allow it, you can re-enable the source database license by using
    LICENSE ENABLE.

    LICENSE COPY cannot be used to create a copy of a license in the
    same database as the source of the copy.

    Format

      LICENSE COPY  product-name[,...] output-database

2.1  –  Parameters

 product-name[,...]

    Name or names of products with a license to be copied to the
    output License Database.

 output-database

    File specification of the License Database to which the license
    or licenses should be copied. This database must have been
    created previously using LICENSE CREATE.

    If you enter a partial file specification (for example,
    specifying only a directory), LMF$LICENSE is the default file
    name, and .LDB is the default file type. If you do not specify a
    device or directory, the current default device and directory are
    used.

2.2  –  Qualifiers

2.2.1    /ALL

    Positional qualifier.

    Specifies that all licenses with the given product name should
    be copied. This qualifier affects only the product name that
    immediately precedes it in the command string.

2.2.2    /AUTHORIZATION

       /AUTHORIZATION=string

    Positional qualifier.

    Specifies a string that helps identify the license you want to
    copy. 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.

2.2.3    /DATABASE

       /DATABASE=filespec

    Specifies the location of the License Database from which
    the license should be copied. 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.

2.2.4    /ISSUER

       /ISSUER=string

    Positional qualifier.

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

2.2.5    /LOG

       /LOG
       /NOLOG (default)

    Controls whether LICENSE COPY displays the name of each license
    that it copies.

2.2.6    /PRODUCER

       /PRODUCER=string

    Positional qualifier.

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

2.3  –  Description

    To copy a license from one database to another, use LICENSE COPY.
    The following conditions apply to a LICENSE COPY transaction:

    o  The status of the source database license changes to disabled.

    o  Network copies are supported within the limits of remote
       FAL access. If you use access control strings, such as
        "USERNAME password" within the file specification, the actual
       password string is not stored.

    o  LICENSE COPY does not transfer any user-supplied data such as
       reservation lists, modified termination dates, modified units,
       include or exclude node lists, or comments.

2.4  –  Examples

    1.$ LICENSE COPY FORTRAN BACKUP_DATA:BACKUP.LDB

      This command copies the Fortran license in the default License
      Database to the BACKUP_DATA:BACKUP.LDB License Database. This
      command fails if there is more than one Fortran license in the
      default database.

    2.$ LICENSE COPY FORTRAN /DATABASE=BACKUP_DATA:BACKUP.LDB -
      _$ BACKUP_DATA2:BACKUP2.LDB

      This command copies the Fortran license in the source License
      Database to the BACKUP_DATA2:BACKUP2.LDB License Database. This
      command fails if there is more than one Fortran license in the
      source database.

    3.$ LICENSE COPY FORTRAN /ALL BACKUP_DATA:BACKUP.LDB

      This command copies all Fortran licenses in the default License
      Database to the BACKUP_DATA:BACKUP.LDB License Database.

    4.$ LICENSE COPY FOR*  BACKUP_DATA:BACKUP.LDB

      This command copies all licenses whose product names begin
      with the string "FOR" from the default License Database to the
      BACKUP_DATA:BACKUP.LDB License Database. In this case, using
      the wildcard character (*) implies the use of /ALL.

    5.$ LICENSE COPY * BACKUP_DATA:BACKUP.LDB

      This command copies all licenses from the default License
      Database to the BACKUP_DATA:BACKUP.LDB License Database. In
      this case, using the wildcard character (*) implies the use of
      /ALL.

    6.$ LICENSE COPY * /PRODUCER=DEC BACKUP_DATA:BACKUP.LDB

      This command copies all licenses with the producer name DEC
      from the default License Database to the BACKUP_DATA:BACKUP.LDB
      License Database. In this case, using the wildcard character
      (*) implies the use of /ALL.

    7.$ LICENSE COPY D%%  BACKUP_DATA:BACKUP.LDB

      This command copies all licenses beginning with a "D" followed
      by exactly two characters from the default License Database
      to the BACKUP_DATA:BACKUP.LDB License Database. In this case,
      using the wildcard character (%) implies the use of /ALL.

3  –  CREATE

    Creates a License Database with no license records.
    Because LMF provides a default License Database in
    SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB when OpenVMS is installed,
    you do not typically need to use this command.

    To use LMF, you must have a License Database file and the
    appropriate number of units for your system. On OpenVMS Alpha
    and VAX, the units are located in the License Unit Requirement
    Table (LURT) file (SYS$COMMON:[SYSEXE]LMF$LURT.DAT), which comes
    installed with OpenVMS. On OpenVMS Integrity servers, the units
    are based on the number of processor cores and the class of the
    machine specified in the PAK you receive with the license.

    Format

      LICENSE CREATE

3.1  –  Qualifier

3.1.1    /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.

3.2  –  Example

  $ LICENSE CREATE /DATABASE=SYS$MANAGER:LMF$LICENSE.LDB

      This command creates the License Database named LMF$LICENSE.LDB
      in the directory SYS$MANAGER.

4  –  DELETE

    Deletes one or more licenses and all history information for
    those licenses from the License Database.

    Format

      LICENSE DELETE  product-name[,...]

4.1  –  Parameter

 product-name[,...]

    Name or names of products with a license to be removed from the
    License Database. You can delete only licenses that have been
    registered.

4.2  –  Qualifiers

4.2.1    /ALL

    Positional qualifier.

    Specifies that all licenses with the given product name should
    be deleted. This qualifier affects only the product name that
    immediately precedes it in the command string.

4.2.2    /AUTHORIZATION

       /AUTHORIZATION=string

    Positional qualifier.

    Specifies a string that helps identify the license you want to
    delete. 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.2.3    /DATABASE

       /DATABASE=filespec

    Specifies the location of the License Database from which
    the license or licenses should be deleted. 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.

4.2.4    /ISSUER

       /ISSUER=string

    Positional qualifier.

    Specifies the name of the company (for example, HP) that issued
    the PAK for the product. 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.2.5    /LOG

       /LOG
       /NOLOG (default)

    Controls whether LICENSE DELETE displays the name of each license
    that it deletes.

4.2.6    /PRODUCER

       /PRODUCER=string

    Positional qualifier.

    Specifies the name of the company (for example, HP) 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.

4.2.7    /STATUS

       /STATUS=[(keyword)[,...]]

    Positional qualifier.

    Selects licenses to be deleted according to the product-name
    parameter specified and one or more license status keywords from
    the following list:

    o  ALL (default)-Deletes all specified licenses in the database.

    o  ACTIVE-Deletes all specified enabled licenses in the database.
       ACTIVE status means that the registered license is enabled for
       loading. For backward compatibility, the LICENSE LIST command
       identifies enabled licenses as having a status of active.

    o  DISABLED-Deletes all specified disabled licenses in the
       database.

    o  EXTINCT-Purges specified license information by deleting all
       extinct license records in the database. Extinct records are
       history records retained after a license is modified.

    o  CANCELED-Deletes all specified canceled licenses in the
       database. Note that current versions of LMF do not set license
       status to canceled. Old licenses may have this status.

    If you enter more than one keyword, separate them with commas,
    and enclose the list in parentheses. You can abbreviate each
    option to the minimum number of characters needed to uniquely
    identify it.

4.3  –  Description

    Use LICENSE DELETE to delete licenses from the License Database.
    To tailor your command, use options to the /STATUS qualifier and
    wildcard characters in product name strings.

    File space is not released following LICENSE DELETE commands.
    For information on retrieving Record Management Services (RMS)
    file space, see the OpenVMS Record Management Utilities Reference
    Manual.

4.4  –  Examples

    1.$ LICENSE DELETE FORTRAN

      This command deletes the Fortran license from the default
      License Database.

    2.$ LICENSE DELETE FORTRAN, COBOL, PASCAL

      This command deletes the Fortran, COBOL and Pascal licenses
      from the default License Database.

    3.$ LICENSE DELETE FORTRAN /DATABASE=MY$DISK:MYDATA.LDB

      This command deletes the Fortran license from the
      MY$DISK:MYDATA.LDB License Database.

    4.$ LICENSE DELETE FORTRAN /ISSUER=XYLASOFT

      This command deletes all licenses for the product named Fortran
      issued by XYLASOFT from the default License Database. If there
      are licenses for products named Fortran issued by companies
      other than XYLASOFT, they are not deleted.

    5.$ LICENSE DELETE * /STATUS=(EXTINCT)

      This command deletes all license records with a status of
      EXTINCT from the database. This is effectively a purge of all
      historical information.

5  –  DISABLE

    Disables a license currently registered in the License Database.

    Format

      LICENSE DISABLE  product-name[,...]

5.1  –  Parameter

 product-name[,...]

    Name or names of products with a license that you want to
    disable. You can disable only licenses that currently exist
    in the License Database. Enter the product name exactly as it
    appears on your Product Authorization Key (PAK).

5.2  –  Qualifiers

5.2.1    /ALL

    Positional qualifier.

    Specifies that all licenses with the given product name should
    be disabled. This qualifier affects only the product name that
    immediately precedes it in the command string.

5.2.2    /AUTHORIZATION

       /AUTHORIZATION=string

    Positional qualifier.

    Specifies a string that helps identify the license you want to
    disable. 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.

5.2.3    /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.

5.2.4    /ISSUER

       /ISSUER=string

    Positional qualifier.

    Specifies the name of the company (for example, HP) that issued
    the PAK for the product. 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.

5.2.5    /LOG

       /LOG
       /NOLOG (default)

    Controls whether LICENSE DISABLE displays the name of each
    license that it disables.

5.2.6    /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.

5.3  –  Description

    LICENSE DISABLE does not immediately affect loaded licenses. To
    affect a loaded license, you must first enter a LICENSE UNLOAD
    command, which unloads the license, but allows current processes
    to finish using the product. Note that to immediately disable all
    loaded licenses, you must shut down the system.

    You cannot use LICENSE LOAD to activate a disabled license; you
    must first use LICENSE ENABLE.

    LMF does not display error messages when either you or the system
    attempts to unload a disabled license.

5.4  –  Example

  $ LICENSE DISABLE ABCD /PRODUCER=DEC

      This command disables the license for ABCD software produced
      by HP. Because no database is specified, LMF uses the default
      database.

6  –  ENABLE

    Enables an existing license in the License Database so that you
    can load it with LICENSE LOAD. This command cancels the effect
    of LICENSE DISABLE, LICENSE COPY, and LICENSE ISSUE, which leave
    the license disabled. Newly registered licenses are enabled by
    default.

    Format

      LICENSE ENABLE  product-name[,...]

6.1  –  Parameter

 product-name[,...]

    Name or names of products with a license to enable. You can
    enable only licenses that currently exist in the License
    Database. Enter the product name exactly as it appears on your
    PAK.

6.2  –  Qualifiers

6.2.1    /ALL

    Positional qualifier.

    Specifies that all licenses with the given product name should
    be enabled. This qualifier affects only the product name that
    immediately precedes it in the command string.

6.2.2    /AUTHORIZATION

       /AUTHORIZATION=string

    Positional qualifier.

    Specifies a string that helps identify the license you want to
    enable. 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.

6.2.3    /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.

6.2.4    /ISSUER

       /ISSUER=string

    Positional qualifier.

    Specifies the name of the company (for example, HP) that issued
    the PAK for the product. 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.

6.2.5    /LOG

       /LOG
       /NOLOG (default)

    Controls whether LICENSE ENABLE displays the name of each license
    that it enables.

6.2.6    /PRODUCER

       /PRODUCER=string

    Positional qualifier.

    Specifies the name of the company (for example, HP) 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.

6.3  –  Description

    Use LICENSE ENABLE to reestablish disabled licenses as available
    for loading with a LICENSE LOAD command.

    Enabled licenses can combine with other licenses when loaded for
    use. Do not enable a license that has expired, and be sure that
    all include, exclude, and reservation lists are up to date.

    Use LICENSE LIST to inspect each license before you enable it.
    Use LICENSE MODIFY to change include, exclude, and reservation
    lists.

    Because errors do not occur until enabled licenses are loaded,
    consider entering LICENSE LOAD immediately to load each newly
    enabled license on each appropriate node in an OpenVMS Cluster.
    If another combinable license for the same product is already
    loaded, first unload it with LICENSE UNLOAD. Use the DCL command
    SHOW LICENSE to see which licenses are currently active on your
    system. After you unload the other license, enter LICENSE LOAD
    to load the combination of the newly enabled license and the
    previously active license.

6.4  –  Example

  $ LICENSE ENABLE DECSET /PRODUCER=DEC

      This command enables the license for DECset software. Because
      no database is specified, LMF uses the default database. Next,
      load the license with LICENSE LOAD.

7  –  ISSUE

    Produces a replica of a Product Authorization Key (PAK) that
    is sent to a file or displayed on your terminal (the default).
    If the terms and conditions of your license contract allow it,
    you can then enter this PAK replica in the License Database of
    another processor. When you enter LICENSE ISSUE, LMF disables
    the license in the current License Database and marks the license
    DISABLED. To enable a license that has been marked ISSUED, enter
    LICENSE ENABLE.

    For License Databases connected to a network, consider using
    LICENSE MOVE.

    Format

      LICENSE ISSUE  product-name[,...]

7.1  –  Parameter

 product-name[,...]

    Name or names of products with a license to be issued. You can
    issue only licenses that currently exist in the License Database.
    Enter the product name exactly as it appears on your PAK.

7.2  –  Qualifiers

7.2.1    /ALL

    Positional qualifier.

    Specifies that all licenses with the given product name should
    be issued. This qualifier affects only the product name that
    immediately precedes it in the command string.

7.2.2    /AUTHORIZATION

       /AUTHORIZATION=string

    Positional qualifier.

    Specifies a string that helps identify the license you want to
    issue. 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.

7.2.3    /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.2.4    /ISSUER

       /ISSUER=string

    Positional qualifier.

    Specifies the name of the company (for example, HP) that issued
    the PAK for the product. 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.

7.2.5    /LOG

       /LOG
       /NOLOG (default)

    Controls whether LICENSE ISSUE displays the name of each license
    that it issues.

7.2.6    /OUTPUT

       /OUTPUT[=filespec]

    Specifies the name of the file to which your PAK replica is
    written. If you do not specify the /OUTPUT qualifier, or if
    you do not supply a file specification with this qualifier, the
    output is sent to SYS$OUTPUT.

    If you specify a file name that already exists, this command
    creates a new version of the file. If you specify a complete file
    name and version that already exists, this command appends the
    PAK replica to the existing file.

7.2.7    /PROCEDURE

       /PROCEDURE
       /NOPROCEDURE (default)

    Specifies that the PAK replica is to be written in the form of a
    DCL command procedure. Use /PROCEDURE with the /OUTPUT qualifier
    to create a command procedure in a file. Then you can invoke the
    procedure to register the PAK replica in the License Database of
    another processor.

    If you do not specify the /OUTPUT qualifier with /PROCEDURE,
    or if you do not supply a file specification with the /OUTPUT
    qualifier, the procedure is sent to SYS$OUTPUT.

7.2.8    /PRODUCER

       /PRODUCER=string

    Positional qualifier.

    Specifies the name of the company (for example, HP) 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.

7.3  –  Description

    If your license contract allows it, use LICENSE ISSUE to
    move a license from a License Database on one processor (or
    OpenVMS Cluster environment) to a License Database on another
    processor. To move a license, enter LICENSE ISSUE, including
    enough PAK information to clearly identify the license. LICENSE
    ISSUE automatically disables the current license but does
    not immediately unload it; LMF does not terminate any active
    processes. To unload the license, enter a LICENSE UNLOAD command.

    After you issue the PAK replica, read the information, and
    register it on the new processor as you would any PAK, or, if
    you used the /PROCEDURE qualifier with the /OUTPUT qualifier,
    invoke the new DCL command procedure to register the license.

    Note that the PAK replica includes only PAK information
    registered with a LICENSE REGISTER command. The replica does
    not include any changes made with other LICENSE commands.

7.4  –  Examples

    1.$ LICENSE ISSUE /OUTPUT=SYS$MANAGER:FORTRAN.PAK -
      _$ /PRODUCER=DEC FORTRAN

      This command issues a PAK replica, which you can use to
      register the Fortran license on a new processor (or OpenVMS
      Cluster environment), and puts it into the file named
      FORTRAN.PAK. The next step is to print the file, read the
      information, and, using a LICENSE REGISTER command or
      VMSLICENSE.COM, enter the correct information in the License
      Database of the new processor. The Fortran license in the
      current License Database is marked ISSUED and is disabled.

    2.$ LICENSE ISSUE /PRODUCER=DEC VOLSHAD

      This command displays, at the current terminal, a PAK replica
      with the information from the VOLSHAD (Volume Shadowing)
      license. This display is reproduced below. The license
      registered in the current License Database is marked ISSUED
      and is disabled. You can register the data from this replica of
      a PAK in the License Database of another processor using either
      VMSLICENSE.COM or LICENSE REGISTER.

        Software Product Authorization Key Replica
        Issued by CASPER
        Issued on 24-FEB-2001 14:23
        -----------------------------------
        Issuer:             DEC
        Authorization:      ALS-WM-93166-5573
        Product Name:       VOLSHAD
        Producer:           DEC
        Units:              460
        Version:            5.4
        PAK Termination Date:   31-DEC-2001
        Availability:       E
        Options:            MOD_UNITS
        Checksum:           1-ADEB-DOCJ-NENC-KDBM

    3.$ LICENSE ISSUE /PROCEDURE /OUTPUT=FORTRAN-USA10.COM -
      _$FORTRAN /AUTHORIZATION=USA-10

      This command generates a DCL command procedure such as the
      following to be used for registering the specified license in a
      License Database:

        $! Software Product Authorization Key Replica
        $! Issued by CASPER
        $! Issued on 23-Oct-2001 14:23
        $ LICENSE REGISTER FORTRAN -
         /ISSUER=DEC -
         /PRODUCER=DEC -
         /AUTHORIZATION=USA-10 -
         /UNITS=400 -
         /VERSION=5.4 -
         /AVAILABILITY=F -
         /CHECKSUM=1-HIDN-INDA-COMP-DAHH

8  –  LIST

    Displays information from the License Database on disk about
    the specified license or licenses. Use one or more qualifiers to
    control the form, content, and location of information displayed.

    The SHOW LICENSE command, described in the HP OpenVMS DCL
    Dictionary and in this help, displays information from the
    License Database in memory.

    Format

      LICENSE LIST  [product-name[,...]]

8.1  –  Parameter

 product-name[,...]

    Name or names of products with a license that you want to
    list. You can list only licenses that currently exist on disk
    in the License Database. You can specify one product name or
    use wildcard characters to display licenses. The product-name
    parameter is optional; the default is to display all of the
    licenses.

8.2  –  Qualifiers

8.2.1    /AUTHORIZATION

       /AUTHORIZATION=string

    Positional qualifier.

    Specifies a string that helps identify the license you want to
    list. 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.

8.2.2    /BEFORE

    Used with /TERMINATION_DATE and /RELEASE_DATE, selects only those
    licenses whose times are before the time specified with the other
    qualifiers.

    The /BEFORE qualifier cannot be used with the /SINCE qualifier.

8.2.3    /BRIEF

       /BRIEF (default)

    Specifies a listing from the License Database that includes only
    the license product and producer names.

8.2.4    /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.

8.2.5    /FULL

    Specifies a listing from the License Database that includes a
    full display of the specified license or licenses.

8.2.6    /HISTORY

    Specifies a listing from the License Database that includes the
    history records in the License Database for the specified license
    or licenses.

8.2.7    /ISSUER

       /ISSUER=string

    Positional qualifier.

    Specifies the name of the company (for example, HP) that issued
    the PAK for the product. 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.

8.2.8    /OUTPUT

       /OUTPUT[=filespec]

    Specifies the name of the file to which your list is written. If
    you do not specify the /OUTPUT qualifier, or if you do not supply
    a file specification with this qualifier, the output is sent to
    SYS$OUTPUT.

8.2.9    /PRODUCER

       /PRODUCER=string

    Positional qualifier.

    Specifies the name of the company (for example, HP) 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.

8.2.10    /RELEASE_DATE

       /RELEASE_DATE=date

    Used with /BEFORE or /SINCE, specifies a listing from the License
    Database that includes only licenses with a release date on
    or after the date specified. The date must be presented in the
    standard OpenVMS format: dd-mmm-yyyy. The default value is /SINCE
    /RELEASE_DATE=TODAY.

8.2.11    /SELECTION_WEIGHT

    Produces a full display that includes the current selection
    weights assigned to individual PAKs.

8.2.12    /SINCE

    Used with /TERMINATION_DATE and /RELEASE_DATE, selects only those
    licenses whose times are after the time specified with the other
    qualifiers.

    /SINCE cannot be used with /BEFORE.

8.2.13    /TERMINATION_DATE

       /TERMINATION_DATE[=date]

    Used with /BEFORE or /SINCE, specifies a listing from the License
    Database that includes only licenses with a termination date on
    or after the date specified. The date must be presented in the
    standard OpenVMS format: dd-mmm-yyyy. The default value is /SINCE
    /TERMINATION_DATE=TODAY.

8.2.14    /VERSION

       /VERSION=nn.nn

    Positional qualifier.

    Specifies the version number of the product for which you have
    a license. Versions use the format integer.integer. You can
    specify wildcard syntax as *.* but not * alone. 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.

8.3  –  Description

    LICENSE LIST displays license records as they appear on disk
    in the License Database. LICENSE LIST /BRIEF does not produce
    a display with history records. You can control the displays as
    follows:

    o  After you enter LICENSE LIST with the /BRIEF qualifier, you
       can scroll through the display with the arrow keys on your
       keyboard.

    o  After you enter LICENSE LIST with the /FULL or /HISTORY
       qualifier, which displays the first LICENSE record, you can
       see the other records one at a time by pressing Return. You
       can also scroll through the license records using the Previous
       Screen key (or PF3) and the Next Screen key (or PF4).

    For any LICENSE LIST display, use the arrow keys to scroll
    vertically or horizontally one line at a time. Press Ctrl/Z to
    exit from the display.

    Note that a LICENSE LIST command may display the status of a
    registered license as Active. This means the registered license
    is enabled for loading; it has not been disabled. It does not
    necessarily mean the license was loaded with a LICENSE LOAD
    command. The LICENSE LIST command displays only information on
    disk in the License Database; enter SHOW LICENSE to determine all
    active licenses on the current system.

    You can also list licenses using the VMSLICENSE.COM command
    procedure.

8.4  –  Examples

    1.$ LICENSE LIST /FULL

      This example displays a list of the names of product licenses
      in the License Database on an OpenVMS Alpha system. Note that
      the LMF Version shown refers to the software that created the
      database.

        CTRL/Z to exit, PF3-PF4 for Prev-Next Screen, ArrowKeys to scroll.

         License Management Facility  V1.2

         License Database File:       WORK2:[BACKUP]LMF$LICENSE.LDB;1
         Created on:                  20-JUL-2000
         Created by user:             USER_1
         Created by LMF Version:      V1.1

         -----------------------------------
         Issuer:                      DEC
         Authorization:
         Product Name:                OPENVMS-ALPHA
         Producer:                    DEC
         Units:                       500
         Version:                     0.0
         Release Date:                 4-MAY-2001
         PAK Termination Date:        (none)
         Availability:                0
         Activity:                     000000100
         Options:                     MOD_UNITS
         Product Token:
         Hardware ID:

         Revision Level:              1
         Status:                      Active
         Command:                     REGISTER

    2.$ LICENSE LIST /FULL

      This example displays a list of the names of product licenses
      in the License Database on an OpenVMS Integrity server system.

        CTRL/Z to exit, PF3-PF4 for Prev-Next Screen, ArrowKeys to scroll.

        License Management Facility  V2.0

         License Database File:       SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB;1
         Created on:                  11-MAR-2010
         Created by user:             SYSTEM
         Created by LMF Version:      V2.0

         -----------------------------------

         Issuer:                      HP
         Authorization:               USA-1715
         Product Name:                C
         Producer:                    HP
         Units:                       3
         Version:                     0.0
         Release Date:                (none)
         PAK Termination Date:        31-DEC-2012
         Availability:                0
         Activity:                     000000001
         Options:                     IA64_ALPHA
         Product Token:
         Hardware ID:

         Revision Level:              1
         Status:                      Active
         Command:                     REGISTER
         Modified by user:            SYSTEM
         Modified on:                 11-MAR-2010 12:18:59.95

         -----------------------------------
         Issuer:                      HP
         Authorization:               I64-AB-001
         Product Name:                DVNETEXT
         Producer:                    HP
         Units:                       20
         Modified Units:              4
         Version:                     0.0
         Release Date:                (none)
         PAK Termination Date:        31-DEC-2012
         Options:                     IA64, PCL
         Product Token:
         Hardware ID:

         Revision Level:              2
         Status:                      Active
         Command:                     MODIFY
         Modified by user:            SYSTEM
         Modified on:                 11-MAR-2010 12:29:42.18

         -----------------------------------
         Issuer:                      HP
         Authorization:               I64-AB-004
         Product Name:                OPENVMS-I64-BOE
         Producer:                    HP
         Units:                       2
         Version:                     0.0
         Release Date:                (none)
         PAK Termination Date:        31-DEC-2012
         Options:                     IA64, PCL
         Product Token:
         Hardware ID:

         Revision Level:              1
         Status:                      Active
         Command:                     REGISTER
         Modified by user:            SYSTEM
         Modified on:                 11-MAR-2010 12:33:26.19

    3.$ LICENSE LIST /HISTORY FORTRAN

      This example displays a listing with full information of a
      current Fortran license issued by HP.

      The first screen, shown here, displays the most recent license
      record for the Fortran license. To see the history records
      one screen at a time, press Return. The revision level of
      the displayed record is 2, and the status is Active. The
      next screen would display the previous license record with a
      revision level of 1 and a status of Extinct.

        CTRL/Z to exit, PF3-PF4 for Prev-Next Screen, ArrowKeys to scroll.

         License Management Facility  V1.2

         License Database File:   ART::SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB

         Created on:                  17-AUG-2000
         Created by user:             USER_2
         Created by LMF Version:      V1.2

         -----------------------------------------------------
         Issuer:                      DEC
         Authorization:               USA-2468
         Product Name:                FORTRAN
         Producer:                    DEC
         Units:                       0
         Modified Units:              2000
         Version:                     5.4
         Release Date:                (none)
         PAK Termination Date:        31-DEC-2000
         Modified Termination Date:   30-NOV-2001
         Availability:                F (Layered Products)
         Activity:                    0
         Options:                     MOD_UNITS
         Hardware ID:

         Revision Level:              2
         Status:                      Active
         Command:                     MODIFY
         Modified by user:            DEGAS
         Modified on:                 19-AUG-2000 14:32:23.41
         Include:                     ART

    4.$ LICENSE LIST /FULL

      This example displays the full listing of a license that has
      been modified using the /VIRTUAL qualifier, for an OpenVMS
      guest system.

        License Management Facility  V2.0

        License Database File:       SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB;1
        Created on:                  1-MAR-2010
        Created by user:             SYSTEM
        Created by LMF Version:      V2.0

        -----------------------------------

         Issuer:                      HP
         Authorization:               I64-AB-001
         Product Name:                OPENVMS-I64-HAOE
         Producer:                    HP
         Units:                       4
         Version:                     0.0
         Release Date:                (none)
         PAK Termination Date:        10-MAR-2011
         Options:                     IA64, PCL, VIRTUAL
         Product Token:
         Hardware ID:

         Revision Level:              2
         Status:                      Active
         Command:                     MODIFY
         Modified by user:            SYSTEM
         Modified on:                 8-MAR-2010 16:45:00.32

9  –  LOAD

    Loads licenses, making them available for product authorization
    on the current node. The product licenses must be registered and
    curr