The License Management Utility (LICENSE) is a DCL-level interface
   to the License Management Facility (LMF) on the VMS operating
   system. LMF provides a variety of system-level software components
   used to maintain software license information in the LICENSE
   database located in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB.

   Use LICENSE to manage and modify the LICENSE database, and to
   control activation of the licenses registered there. Most Digital
   software products require license registration as part of the
   normal product installation before users can access the product.

   Format

     LICENSE  subcommand parameter

Additional information available:

AMENDCANCELCOPYCREATEDELETEDISABLEENABLE
ISSUELISTLOADMODIFYMOVEREGISTERSTART
UNLOAD

usage summaryMessages

   To use the License Management Utility (LICENSE), enter the LICENSE
   command and the desired LICENSE subcommand and qualifiers 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=5.4 -
     _$ /AVAILABILITY=F /CHECKSUM=1-GEAD-MIDJ-IDNC-DLAC

                                  NOTE

      Enter the LICENSE commands carefully. LICENSE command
      strings can be very long and can require a hyphen (-)
      character at the end of each line. Because LMF may return
      only a checksum error when you omit or incorrectly enter
      information, carefully check the characters typed on each
      line before you press Return. You can eliminate some typing
      by using the command procedure SYS$UPDATE:VMSLICENSE.COM for
      most of the LICENSE commands.

   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 LICENSE databases. The LICENSE database is file based;
   normal VMS file protection applies. LMF provides the 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), 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 CANCEL
      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 the LICENSE LIST command.
   To display the licenses active on the current node, use the DCL
   command SHOW LICENSE.

   In some special circumstances, VMS 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 users with large license databases. When used with multiple
   parameters, positional qualifiers affect only the preceding
   parameter. A positional qualifier that precedes every parameter,
   however, affects them all equally.

   Updates a license currently in the LICENSE database. Digital
   is not currently supplying the Product Authorization Amendments
   (PAAMs) required to use this command. In the future, Digital may
   offer PAAMs that provide the product name and information you
   need to amend a license. If you receive a PAAM, you must enter all
   information provided exactly as it appears.

                                  NOTE

      Use the LICENSE AMEND command only when you have new data
      to enter from a PAAM. Use the LICENSE MODIFY command to make
      all other license changes.

   Format

     LICENSE AMEND  product-name

Additional information available:

ParameterQualifiersDescriptionExamples

product-name
   Name of the product with a license to amend. You can only amend
   licenses that currently exist in the LICENSE database. Enter the
   product name exactly as it appears on your PAAM.

   You cannot use wildcard characters for the product-name parameter
   with this command.

Additional information available:

/AUTHORIZATION/CHECKSUM/DATABASE/HARDWARE_ID
/ISSUER/OPTIONS/PRODUCER/RELEASE_DATE/TERMINATION_DATE
/TOKEN/UNITS/VERSION

      /AUTHORIZATION=string

   Specifies a string that along with the PAK issuer string uniquely
   identifies the license you want to amend. If the PAAM supplies
   an authorization string, you must enter the string exactly as it
   appears on your PAAM.

      /CHECKSUM=string

   Specifies a 17-character verification string created by the PAK
   issuer for each PAAM. The checksum string is presented in the
   format n-cccc-cccc-cccc-cccc, where n is an integer and c is
   an alphabetic character from A through P. A PAAM presents the
   checksum string with hyphen (-)  characters for readability.
   Because LMF does not count them for authorization, you can leave
   them out. Otherwise, you must enter the checksum string exactly as
   it appears on your PAAM.

      /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 VMS
   system.

      /HARDWARE_ID=string

   Specifies the identification number of the hardware on which
   the product is licensed. If your PAAM supplies hardware
   identification, you must enter the information exactly as it
   appears.

      /ISSUER=string

   Specifies the name of the company (for example, DEC) that issued
   the PAK for the product. Note that the PAK issuer is often the
   same as the producer. If your PAAM supplies a PAK issuer, you must
   enter the information exactly as it appears on your PAAM.

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

   Specifies a LICENSE option or a list of LICENSE options. If your
   PAAM supplies license option information, you must enter the
   information exactly as it appears on your PAAM. Current option
   keywords include the following:

   Keyword         Meaning

   MOD_UNITS       The number of license units can be modified.

   NO_SHARE        The license cannot be used by more than one
                   processor in a VAXcluster environment. If this
                   license is used in a VAXcluster environment,
                   you must designate it for one node using LICENSE
                   MODIFY with an /INCLUDE qualifier.

   RESERVE_UNITS   The license must be assigned to one or more users.
                   Reserve the license by using LICENSE MODIFY with
                   the /RESERVE qualifier.

   If you enter more than one keyword, separate them with commas and
   enclose the list in parentheses.

      /PRODUCER=string

   Specifies the name of the company (for example, DEC) that owns
   the product for which you have a license. If your PAAM supplies a
   producer, you must enter the information exactly as it appears on
   your PAAM.

      /RELEASE_DATE=date

   Specifies a product release date such that the license authorizes
   use of all product versions released on or before the date. If
   your PAAM supplies a product release date, you must enter the
   information exactly as it appears. The product release date must
   be presented in the standard VMS syntax: dd-mmm-yyy.

   This qualifier replaces the obsolete qualifier /DATE=date.

      /TERMINATION_DATE=date

   Specifies the date at which the product license terminates. If
   your PAAM supplies a license termination date, you must enter it
   exactly as it appears. The date must be presented in the standard
   VMS format: dd-mmm-yyyy.

   This qualifier replaces the obsolete qualifier /TERMINATION=date.

      /TOKEN=string

   Specifies a string of information associated with some products.
   This option can enable or disable certain product features. See
   your product documentation for details. If your PAAM provides
   token information, you must enter it exactly as it appears.

      /UNITS=number

   Specifies the number of license units on the PAAM. If your PAAM
   supplies the number of units, you must enter them exactly as they
   appear on your PAAM even if your PAAM specifies the MOD_UNITS
   option.

      /VERSION=nn.nn

   Limits the version number of the product for which you have a
   license. Use the format integer.integer. If your PAAM supplies
   version information, you must enter it exactly as it appears.

   The LICENSE AMEND command is one of the primary LICENSE commands.
   Before you enter a LICENSE AMEND command, you need a Product
   Authorization Amendment (PAAM) that supplies the information
   required to change an existing license. The PAAM must be one
   designed to amend the original Product Authorization Key (PAK)
   for the product.

   Usually a PAAM provides only enough information to identify
   the license, specify the changes, and authorize the changes (a
   new checksum). If your PAAM specifies more information than is
   required to identify it, you must enter all of the information;
   the checksum is based on all the provided PAAM information.

   After you amend the license in the LICENSE database, you must
   ensure that it is activated. If a product has a license already
   activated (LICENSE LOAD), you must enter a LICENSE UNLOAD command
   followed by a LICENSE LOAD command for each license you change.
   If a product is not activated, you need only enter a LICENSE
   LOAD command after you amend the license. If you amend several
   licenses, you can activate all the licenses in the database by
   entering LICENSE LOAD without the product-name parameter.

                                  NOTE

      Enter the LICENSE AMEND commands carefully. LICENSE AMEND
      command strings can be very long, and require a hyphen
      (-) character at the end of each line if they will not fit
      on one line. Because LMF may return only a checksum error
      when you omit or incorrectly enter information, you should
      carefully check the characters typed on each line before
      you press Return. You can eliminate some typing by using the
      command procedure SYS$UPDATE:VMSLICENSE.COM.

   1.  $ LICENSE AMEND  FORTRAN /PRODUCER=DEC /ISSUER=DEC -

       _$ /AUTHORIZATION=USA4321 -
       _$ /CHECKSUM=1-GEAD-OODA-HIDN-PLAC /VERSION=5.4

     This command amends the license for the Digital software
     product named FORTRAN. Entering this command upgrades an
     existing FORTRAN license to Version 5.4. The producer name,
     issuer name, authorization number, and checksum number are
     typed exactly as they appear on the PAAM for FORTRAN.

   2.  $ LICENSE AMEND VAXINFO  /PRODUCER=DEC /ISSUER=DEC -

       _$ /AUTHORIZATION=USA1234 /CHECKSUM=1-FFFL-ONNA-DAHH-BCKK -
       _$ /TERMINATION_DATE=12-DEC-1992

     This command amends the license for the Digital software
     product named VAXinfo[[TM]]. Entering this command changes
     the current termination date to December 12, 1992. The producer
     name, issuer name, authorization number, checksum number, and
     termination date are typed exactly as they appear on the PAAM
     for VAXinfo.

   Specifies a new termination date for a product currently in
   the LICENSE database. You must use the /TERMINATION_DATE=date
   qualifier. Use only as many of the other qualifiers as needed
   to identify the license. For example, if the product name is not
   unique, add the producer name or authorization string to identify
   the license.

                                  NOTE

      This command is obsolete. Use the command LICENSE
      MODIFY/TERMINATION_DATE=date.

   Format

     LICENSE CANCEL /TERMINATION_DATE=date  product-name[,...]

Additional information available:

ParameterQualifiersDescriptionExample

product-name[,...]
   Name or names of products with a license to be canceled. You can
   only cancel licenses currently in the LICENSE database.

Additional information available:

/ALL/AUTHORIZATION/DATABASE/ISSUER/LOG
/PRODUCER/RELEASE_DATE/TERMINATION_DATE

   Positional qualifier.

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

      /AUTHORIZATION=string

   Positional qualifier.

   Specifies a string that along with the PAK issuer string uniquely
   identifies the license you want to cancel. This qualifier is
   optional. This qualifier affects only the product name that
   immediately precedes it in the command string.

      /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 VMS
   system. This qualifier is optional; use it only if you do not use
   the default LICENSE database name and location.

      /ISSUER=string

   Positional qualifier.

   Specifies the name of the company (for example, DEC) that issued
   the PAK for the product. Note that the PAK issuer is often the
   same as the producer. 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.

      /LOG
      /NOLOG

   Controls whether the LICENSE CANCEL command displays the name of
   each license that it cancels.

   By default, the LICENSE CANCEL command does not display the names
   of licenses that it cancels.

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

      /RELEASE_DATE=date

   Specifies the date on which the product was released. Use this
   optional qualifier only if you need it to identify the license.
   The date must be presented in the standard VMS format: dd-mmm-
   yyyy.

   This qualifier replaces the obsolete qualifier /DATE=date.

      /TERMINATION_DATE=date

   Specifies the date at which the product license is to be
   terminated. This qualifier is required with the LICENSE CANCEL
   command. If your PAK or most recent PAAM supplied a license
   termination date, LMF uses the earliest date to determine the
   termination date. The date must be presented in the standard
   VMS format: dd-mmm-yyyy. If you want to restrict a product from
   further use today, enter yesterday's date-LMF cancels at the end
   of the day specified.

   This qualifier replaces the obsolete qualifier /TERMINATION=date.

   Use the LICENSE CANCEL/TERMINATION_DATE=date command to cancel
   a product license in the LICENSE database. If your PAK or most
   recent PAAM supplied a license termination date, LMF uses the
   earliest date to determine the termination date. The date must
   be presented in the standard VMS format: dd-mmm-yyyy. You can
   also cancel a product license using the VMSLICENSE.COM command
   procedure.

   LMF cancels licenses just before the end of the day specified.
   In VMS time format this is 23:59:59.99. If you want to restrict a
   product from further use today, enter the LICENSE CANCEL command
   using yesterday's date. To affect an active license you must enter
   a LICENSE UNLOAD command or shut down the system. The LICENSE
   UNLOAD command deactivates the license, disallowing additional
   product use but allowing the current processes to finish.

   Any time you or the system attempts to activate a license after
   the cancellation date, LMF produces an error message. To stop
   the error messages, disable the license with a LICENSE DISABLE
   command, or delete it with the LICENSE DELETE command.

   Canceled licenses that are not also disabled can adversely affect
   the activation of other licenses in a common LICENSE database.

   $ LICENSE CANCEL/AUTHORIZATION=USA1776 -
   _$/TERMINATION_DATE=04-JUL-1992 VAX-VMS

     Unless an earlier termination date exists, this command sets
     a new cancellation date of July 4, 1992, for the license on
     VMS. Cancellation takes effect at the end of the day on July 4,
     1992. Note that the product name is entered with a hyphen (-)
     character because it appears this way on the PAK.

   Copies one or more licenses from one LICENSE database to another.
   When you use the LICENSE COPY command, 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 reenable the source database
   license by using the LICENSE ENABLE command.

   The LICENSE COPY command 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

Additional information available:

ParametersQualifiersDescriptionExamples

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 previously
   created using the LICENSE CREATE command.

   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.

Additional information available:

/ALL/AUTHORIZATION/DATABASE/ISSUER/LOG
/PRODUCER

   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.

      /AUTHORIZATION=string

   Positional qualifier.

   Specifies a string that along with the PAK issuer string uniquely
   identifies the license you want to copy. 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.

      /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 VMS system.
   This qualifier is optional; use it only if you do not use the
   default LICENSE database name and location.

      /ISSUER=string

   Positional qualifier.

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

      /LOG
      /NOLOG

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

   By default, the LICENSE COPY command does not display the names of
   licenses that it copies.

      /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 to identify the license. This qualifier affects
   only the product name that immediately precedes it in the command
   string.

   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 ( "USERNAME
      password") within the file name, the actual password string
      is not stored.

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

   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 any 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.

   Creates a LICENSE database with no license records.
   Because LMF provides a default LICENSE database in
   SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB when VMS is installed, you
   do not typically need to use this command. Note that you must have
   a LICENSE database file and the License Unit Requirement Table
   file, SYS$COMMON:[SYSEXE]LMF$LURT.DAT, before you can use LMF.

   Format

     LICENSE CREATE

Additional information available:

QualifierExample

Additional information available:

/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 VMS
   system.

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

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

   Deletes one or more licenses and all history information for those
   licenses from the LICENSE database. Deleted licenses are no longer
   available to the system for any use.

   Format

     LICENSE DELETE  product-name[,...]

Additional information available:

ParameterQualifiersDescriptionExamples

product-name[,...]
   Name or names of products with a license to be removed from the
   LICENSE database. You can only delete licenses that have been
   registered.

Additional information available:

/ALL/AUTHORIZATION/DATABASE/ISSUER/LOG
/PRODUCER/STATUS

   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.

      /AUTHORIZATION=string

   Positional qualifier.

   Specifies a string that along with the PAK issuer string uniquely
   identifies the license you want to modify. 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.

      /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 VMS
   system. This qualifier is optional; use it only if you do not use
   the default LICENSE database name and location.

      /ISSUER=string

   Positional qualifier.

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

      /LOG
      /NOLOG

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

   By default, the LICENSE DELETE command does not display the names
   of licenses that it deletes.

      /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 to identify the license. This qualifier affects
   only the product name that immediately precedes it in the command
   string.

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

   Positional qualifier.

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

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

   o  ACTIVE-Deletes all specified active licenses in the database.
      Notice that ACTIVE status means the registered license is
      enabled for activation, that it has not been disabled, or
      canceled. It does not necessarily mean the license was
      activated with a LICENSE LOAD command.

   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.

   Use LICENSE DELETE to remove 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 VMS Convert and Convert/Reclaim Utility Manual.

   1.  $ LICENSE DELETE FORTRAN

     This command removes the FORTRAN license from the default
     LICENSE database.

   2.  $ LICENSE DELETE FORTRAN, COBOL, PASCAL

     This command removes the FORTRAN, COBOL and Pascal licenses
     from the default LICENSE database.


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

     This command removes the FORTRAN license from the
     MY$DISK:MYDATA.LDB LICENSE database.

   4.  $ LICENSE DELETE FORTRAN/ISSUER=XYLASOFT

     This command removes 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 status of
     EXTINCT from the database. This is effectively a purge of all
     historical information.

   Disables a license currently registered in the LICENSE database.
   You cannot activate (LICENSE LOAD) a disabled license to authorize
   product use.

   Format

     LICENSE DISABLE  product-name[,...]

Additional information available:

ParameterQualifiersDescriptionExample

product-name[,...]
   Name or names of products with a license to disable. You can only
   disable licenses that currently exist in the LICENSE database.
   Enter the product name exactly as it appears on your PAK.

Additional information available:

/ALL/AUTHORIZATION/DATABASE/ISSUER/LOG
/PRODUCER

   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.

      /AUTHORIZATION=string

   Positional qualifier.

   Specifies a string that along with the PAK issuer string uniquely
   identifies the license you want to disable. 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.

      /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 VMS
   system. This qualifier is optional; use it only if you do not use
   the default LICENSE database name and location.

      /ISSUER=string

   Positional qualifier.

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

      /LOG
      /NOLOG

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

   By default, the LICENSE DISABLE command does not display the names
   of licenses that it disables.

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

   The LICENSE DISABLE command does not immediately affect any
   active licenses. To affect an active license you must first enter
   a LICENSE UNLOAD command or shut down the system. The LICENSE
   UNLOAD command then deactivates the license, allowing any current
   processes to finish using the product.

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

   $ LICENSE DISABLE DECSET /PRODUCER=DEC

     This command disables the license for DECset[[TM]], produced by
     Digital. Because no database is specified, LMF uses the default
     database.

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

   Format

     LICENSE ENABLE  product-name[,...]

Additional information available:

ParameterQualifiersDescriptionExample

product-name[,...]
   Name or names of products with a license to enable. You can only
   enable licenses that currently exist in the LICENSE database.
   Enter the product name exactly as it appears on your PAK.

Additional information available:

/ALL/AUTHORIZATION/DATABASE/ISSUER/LOG
/PRODUCER

   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.

      /AUTHORIZATION=string

   Positional qualifier.

   Specifies a string that along with the PAK issuer string uniquely
   identifies the license you want to enable. 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.

      /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 VMS
   system. This qualifier is optional; use it only if you do not use
   the default LICENSE database name and location.

      /ISSUER=string

   Positional qualifier.

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

      /LOG
      /NOLOG

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

   By default, the LICENSE ENABLE command does not display the names
   of licenses that it enables.

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

   Use LICENSE ENABLE to re-establish disabled licenses as available
   for activation with a LICENSE LOAD command.

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

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

   Since errors do not occur until enabled licenses are activated,
   consider entering a LICENSE LOAD command immediately to activate
   each newly enabled license on each appropriate node in a
   VAXcluster. If another combinable license for the same product
   is already activated, you must first deactivate it with a LICENSE
   UNLOAD command. Use the SHOW LICENSE command to see which licenses
   are currently active on your system. After you deactivate the
   other license, enter a LICENSE LOAD command to activate the
   combination of the newly enabled license and the previously active
   license.

   $ LICENSE ENABLE DECSET /PRODUCER=DEC

     This command enables the license for DECset, produced by
     Digital. Because no database is specified, LMF uses the default
     database. Next, activate the license with a LICENSE LOAD
     command.

   Produces a replica of a 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 a
   LICENSE ISSUE command, LMF disables the license in the current
   LICENSE database and marks the license DISABLED. To enable a
   license that has been marked ISSUED, enter the LICENSE ENABLE
   command.

   For LICENSE databases connected to a network, consider using the
   LICENSE MOVE command.

   Format

     LICENSE ISSUE  product-name[,...]

Additional information available:

ParameterQualifiersDescriptionExamples

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

Additional information available:

/ALL/AUTHORIZATION/DATABASE/ISSUER/LOG
/OUTPUT/PROCEDURE/PRODUCER

   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.

      /AUTHORIZATION=string

   Positional qualifier.

   Specifies a string that along with the PAK issuer string uniquely
   identifies the license you want to issue. 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.

      /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 VMS
   system. This qualifier is optional; use it only if you do not use
   the default LICENSE database name and location.

      /ISSUER=string

   Positional qualifier.

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

      /LOG
      /NOLOG

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

   By default, the LICENSE ISSUE command does not display the names
   of licenses that it issues.

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

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

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

   If your license contract allows it, use LICENSE ISSUE to move a
   license from a LICENSE database on one processor (or VAXcluster
   environment) to a LICENSE database on another processor. To
   move a license, enter LICENSE ISSUE, including enough PAK
   information to clearly identify the license. The LICENSE ISSUE
   command automatically disables the current license, but does not
   immediately deactivate it; LMF does not terminate any active
   processes. To deactivate 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 (or LICENSE AMEND) command. The replica
   does not include any changes made with other LICENSE commands.

   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 VAXcluster
     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

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

     This command displays, at the current terminal, a PAK replica
     with the information from the VOLSHAD (VAX Volume Shadowing)
     license. 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 the LICENSE REGISTER
     command.


   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-1991 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

   Displays information from the LICENSE database about the specified
   license or licenses. Use one or more qualifiers to control the
   form, content, and location of information displayed.

   Format

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

Additional information available:

ParameterQualifiersDescriptionExamples

product-name[,...]
   Name or names of products with a license to list. You can only
   list licenses that currently exist 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.

Additional information available:

/AUTHORIZATION/BEFORE/BRIEF/DATABASE/FULL
/HISTORY/ISSUER/OUTPUT/PRODUCER/RELEASE_DATE
/SINCE/TERMINATION_DATE/VERSION

      /AUTHORIZATION=string

   Positional qualifier.

   Specifies a string that along with the PAK issuer string uniquely
   identifies the license you want to list. 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.

   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.

      /BRIEF (default)

   Specifies a listing from the LICENSE database that includes only
   license product names, units, types, version number, release
   dates, and expiration dates.

      /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 VMS
   system. This qualifier is optional; use it only if you do not use
   the default LICENSE database name and location.

   Specifies a listing from the LICENSE database that includes a full
   display of the specified license or licenses.

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

      /ISSUER=string

   Positional qualifier.

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

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

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

      /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 VMS format: dd-mmm-yyyy. The default value is /SINCE
   /RELEASE_DATE=TODAY.

   The /RELEASE_DATE qualifier cannot be used with the /TERMINATION_
   DATE qualifier.

   This qualifier replaces the obsolete qualifier /DATE=date.

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


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

      /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 VMS format: dd-mmm-yyyy. The default value is /SINCE
   /TERMINATION_DATE=TODAY.

   The /TERMINATION_DATE qualifier cannot be used with the /RELEASE_
   DATE qualifier.

   This qualifier replaces the obsolete qualifier /TERMINATION=date.

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

   The LICENSE LIST command displays license records as they appear
   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
      qualifiers, 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) on your
      keyboard.

   For any LICENSE LIST display, use the arrow keys to scroll
   vertically or horizontally a single line at a time. Use 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 activation, that it has not been disabled or
   issued. It does not necessarily mean the license was activated
   with a LICENSE LOAD command. The LICENSE LIST command displays
   only information from the LICENSE database; enter a SHOW LICENSE
   command to determine all active licenses on the current system.

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

   1.  $ LICENSE LIST

        Press CTRL/Z to exit, use arrow keys to scroll.

        License Management Facility

        License Database File:       SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB
        Created on:                  24-DEC-1990
        Created by user:             K_KRINGLE
        LMF Version:                 V1.0
       ----------------------------------

        FORTRAN                  DEC
        COBOL                    DEC
        PASCAL                   DEC
        [End of List]

     This command displays a list of the names of product licenses
     in the LICENSE database. This command is equivalent to LICENSE
     LIST /BRIEF *. Note that the LMF Version shown refers to the
     the software that created the database.

   2.  $ LICENSE LIST /HISTORY FORTRAN

       Use Ctrl/Z to exit, PF3-PF4 for Previous-Next Screen and Arrow keys to Scroll.

        License Management Facility

        License Database File:       ART::SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB
        Created on:                  17-AUG-1990
        Created by user:             MONET
        LMF Version:                 V1.0

        -----------------------------------------------------
        Issuer:                      DEC
        Authorization:               USA-2468
        Product Name:                FORTRAN
        Producer:                    DEC
        Units:                       0
        Modified Units:              2000
        Version:                     5.4
        Release Date:                (none)
        PAK Termination Date:        21-DEC-1992
        Modified Termination Date:   10-NOV-1992
        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-1992 14:32:23.41
        Include:                     ART

     This command example displays a listing with full information
     of a current and past FORTRAN license issued by Digital. 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 History.

   Activates a license or licenses, making them available for
   product authorization for the current node. The product license or
   licenses must be registered and current in the LICENSE database.
   That is, they must not have been disabled or issued. If the
   license is already loaded, LMF returns an informational message
   and makes no changes.

   To use this command you need the privileges to change mode to
   kernel (CMKRNL) and to create system logical names (SYSNAM), and
   system privileges (SYSPRV).

   Format

     LICENSE LOAD  [product-name]

Additional information available:

ParameterQualifiersDescriptionExamples

product-name
   Name of the licensed product to be activated. You can only load
   licenses that are currently registered and enabled in the LICENSE
   database. Enter the product name exactly as it appears on your
   PAK. If you do not specify a product name, LICENSE LOAD activates
   all of the products that are registered and enabled.

Additional information available:

/AUTHORIZATION/DATABASE/LOG/PRODUCER

      /AUTHORIZATION=string

   Positional qualifier.

   Specifies a string that identifies the license or licenses you
   want to activate. This qualifier affects only the product name
   that immediately precedes it in the command string.

      /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 VMS
   system. This qualifier is optional; use it only if you do not use
   the default LICENSE database name and location.

      /LOG (default)
      /NOLOG

   Controls whether the LICENSE LOAD command displays a message to
   acknowledge the activation of each product license.

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

   The LICENSE LOAD command activates licenses registered in the
   LICENSE database. To use a licensed product, you must ensure that
   the system activates the registered license. When you register a
   license with VMSLICENSE.COM, you can confirm an option to activate
   the license, whereas if you register a license with the LICENSE
   REGISTER command, you must also activate it with a LICENSE LOAD
   command. You need to enter the LICENSE LOAD command only after you
   register a new license-LMF automatically activates all registered
   licenses at each subsequent system startup. You may wish to enter
   a pair of LICENSE UNLOAD and LICENSE LOAD commands at other times
   to activate modifications made with other LICENSE commands.

   You can enter a single LICENSE LOAD command without the product-
   name parameter to activate all the available registered licenses.
   A LICENSE START command entered interactively or when the system
   reboots also activates all licenses that are registered and
   enabled.

   If you register multiple licenses for a single product, LICENSE
   LOAD activates all of the matching licenses; you cannot load and
   unload individual licenses for a product. The availability or
   activity units of the multiple licenses combine to provide more
   product availability.

   In a VAXcluster environment, each system activates licenses when
   it reboots. If you need to activate a license for all assigned
   nodes of a running cluster, you can do one of the following:

   o  Log in to each VAXcluster node and enter the LICENSE LOAD
      command.

   o  Invoke the VMS SYSMAN Utility to execute the LICENSE LOAD
      command on the desired VAXcluster nodes. See the the VMS
      SYSMAN Utility 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 OPCOM
   (Operator Communication Facility), 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 combination has failed because LMF attempted to
      activate a product with two or more licenses that could not
      be combined. Only the licenses that can combine are loaded.
      If there are two licenses for the same product and LMF cannot
      combine them, LMF loads the license that appears first in a
      LICENSE LIST command.

   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 activate a disabled license or a license
   modified to exclude the current node in a VAXcluster environment,
   OPCOM does not display an error message.

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

   1.  $ LICENSE UNLOAD FORTRAN

       $ LICENSE MODIFY/INCLUDE=MUSIC FORTRAN
       $ LICENSE LOAD FORTRAN

     The commands in this example illustrate a situation where
     you enter a LICENSE LOAD command interactively. The LICENSE
     LOAD command activates the product FORTRAN on the node MUSIC.
     Data in the LICENSE database determines whether the license is
     successfully activated on the specified node.

   2.  $ LICENSE LOAD BASIC

       %LICENSE-W-NOLOAD, license was not loaded for BASIC
       -LICENSE-F-EXCEEDED, attempted usage exceeds active license limits

     This command attempts to activate the product BASIC, but the
     LICENSE LOAD command fails because too few license units are
     registered to authorize use on the current processor.

   Modifies a license for system management and license sharing
   purposes. The LICENSE MODIFY command changes data in the LICENSE
   database immediately, but the modifications do not affect a
   running system until you activate the modified license with a
   LICENSE LOAD command.

   Use the LICENSE AMEND command to change a license if you have a
   Product Authorization Amendment (PAAM).

   Format

     LICENSE MODIFY  product-name[,...]

Additional information available:

ParameterQualifiersDescriptionExamples

product-name[,...]
   Name or names of products with a license to be modified. You can
   only modify licenses that currently exist in the LICENSE database.

Additional information available:

/ADD/ALL/AUTHORIZATION/COMMENT/DATABASE
/EXCLUDE/INCLUDE/ISSUER/LOG/PRODUCER/REMOVE
/RESERVE/TERMINATION_DATE/UNITS

   Used with the /INCLUDE or /EXCLUDE qualifiers, 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.

   Positional qualifier.

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

      /AUTHORIZATION=string

   Positional qualifier.

   Specifies a string that along with the PAK issuer string uniquely
   identifies the license you want to modify. 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.

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

      /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 VMS
   system. This qualifier is optional; use it only if you do not use
   the default LICENSE database name and location.

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

   Specifies that the named node or nodes in a VAXcluster environment
   cannot access the licensed product. The excluded nodes cannot
   activate (with a LICENSE LOAD or LICENSE START command) the
   license registered in the LICENSE database. Each argument must
   be a System Communications Services (SCS) node name, 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.

   Although you can control license access to nodes with /EXCLUDE and
   control user access with /RESERVE, 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.

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

   Specifies that the named node or nodes in a VAXcluster environment
   can access the licensed product. Only the included nodes can
   activate (with a LICENSE LOAD or LICENSE START command) the
   license registered in the LICENSE database. Each argument must
   be a System Communications Services (SCS) node name, a system
   parameter set with the System Generation Utility (SYSGEN). The
   node name might not be the same as the DECnet node name.

   Because licenses for the VMS operating system software usually
   specify the NO_SHARE option on their PAKs, in a VAXcluster
   environment you must restrict each VMS license to a single
   node. If you did not take the option when registering with
   VMSLICENSE.COM, enter LICENSE MODIFY/INCLUDE=node-name, specifying
   only one SCS node name for each VMS license.

   If you 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.

   Although you can control license access to nodes with /INCLUDE and
   control user access with /RESERVE, 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.

      /ISSUER=string

   Positional qualifier.

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

      /LOG
      /NOLOG

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

   By default, the LICENSE MODIFY command does not display the names
   of licenses that it modifies.

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

   Used with the /INCLUDE or /EXCLUDE qualifiers, 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.

      /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 for details.

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

   If your PAK or most recent PAAM 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. Calculate this number as you would for
   any activity license.

   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, will be denied
   access.

   Although you can control license access to nodes with /INCLUDE
   or /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.

      /TERMINATION_DATE=date

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

   This qualifier, used with LICENSE MODIFY, replaces the obsolete
   command and qualifier LICENSE CANCEL /TERMINATION=date.

      /UNITS=number

   Specifies the number of license units you want on a license that
   includes the MOD_UNITS option. If your PAK or most recent PAAM
   allows you to modify the license units, use this qualifier to
   change the value in the LICENSE database.

   To control which nodes in a VAXcluster 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 activate a license (with a LICENSE LOAD or
   LICENSE START command), LMF activates a license on a first come,
   first served basis. When your license has insufficient license
   units for full VAXcluster environment use, control product access
   with an include list.

   Because most VMS PAKs use the NO_SHARE option, in a VAXcluster
   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 VMS license.

   To control which users have access to what software, use LICENSE
   MODIFY with the /RESERVE qualifier. You can also create and modify
   a reservation list for any availability or regular activity
   license. Only user names on the reservation list or lists are
   allowed access to the product.

   If your PAK or most recent PAAM 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 the License Unit Requirement Tables.
   Calculate this number as you would for any activity 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 or most recent PAAM includes the MOD_UNITS option, you
   can use the /MOD_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.

   1.  $ LICENSE MODIFY /EXCLUDE=(DANCE,THEATR) -

       _$ /COMMENT="Modified to exclude nodes DANCE & THEATR 10/23/91" -
       _$ FORTRAN

     This command modifies the FORTRAN license in the LICENSE
     database so that users cannot access FORTRAN from the nodes
     named DANCE and THEATR. A comment is added to the database
     record for future reference.

   2.  $ LICENSE MODIFY /ADD /INCLUDE=(DRAMA) -

       _$ /COMMENT="Modified to add node named DRAMA 10/23/92" -
       _$ FORTRAN

     This command modifies the FORTRAN license in the LICENSE
     database so that users can access FORTRAN from the node DRAMA
     in addition to any nodes previously named in the license
     include list.

   3.  $ LICENSE UNLOAD FORTRAN

       $ LICENSE MODIFY/ UNITS=1200 FORTRAN
       $ LICENSE LOAD FORTRAN

     This command changes the license units on a license with the
     MOD_UNITS option.

   4.  $ LICENSE MODIFY/ TERMINATION_DATE=1-JAN-1992 FORTRAN

     Unless an earlier termination date exists, this command sets a
     new cancellation date of 1-Jan-1992, for the FORTRAN license.


   5.  $  LICENSE MODIFY/EXCLUDE="" FORTRAN

     This command removes all nodes from the previously established
     exclude list. All nodes now have access to the FORTRAN license.

   Moves one or more licenses from one LICENSE database to another.
   When you use the LICENSE MOVE command, LMF deletes the licenses in
   the source LICENSE database.

   For LICENSE databases not connected to a network consider using
   the LICENSE ISSUE /PROCEDURE command.

   Format

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

Additional information available:

ParametersQualifiersDescriptionExamples

product-name[,...]
   Name or names of products with a license to be moved to the output
   LICENSE database.

output-database
   File specification of the LICENSE database to which the license or
   licenses should be moved. This database must have been previously
   created using the LICENSE CREATE command.

   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.

Additional information available:

/ALL/AUTHORIZATION/DATABASE/ISSUER/LOG
/PRODUCER

   Positional qualifier.

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

      /AUTHORIZATION=string

   Positional qualifier.

   Specifies a string that along with the PAK issuer string uniquely
   identifies the license you want to move. 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.

      /DATABASE=filespec

   Specifies the location of the LICENSE database from which
   the license or licenses should be moved. The default file
   specification is defined by the logical name LMF$LICENSE, which
   points to SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB on an unmodified VMS
   system. This qualifier is optional; use it only if you do not use
   the default LICENSE database name and location.

      /ISSUER=string

   Positional qualifier.

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

      /LOG
      /NOLOG

   Controls whether the LICENSE MOVE command displays the name of
   each license that it moves.

   By default, the LICENSE MOVE command does not display the names of
   licenses that it moves.

      /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 to identify the license. This qualifier affects
   only the product name that immediately precedes it in the command
   string.

   If your license contract allows it, use LICENSE MOVE to move a
   license from one LICENSE database to another. To move a license,
   enter LICENSE MOVE, including enough PAK information to clearly
   identify the license. The LICENSE MOVE command automatically
   deletes the license in the source LICENSE database.

   Note that the moved license includes only the general PAK
   information normally provided by a LICENSE REGISTER (or LICENSE
   AMEND) command. The LICENSE MOVE command does not transfer any
   user supplied data such as reservation lists; modified termination
   dates; modified units; include or exclude node lists; or comments.

   1.  $ LICENSE MOVE FORTRAN ALT_SYS2:LMF$LICENSE.LDB

     This command moves the FORTRAN license in the default LICENSE
     database to the ALT_SYS2:LMF$LICENSE.LDB output LICENSE
     database. This command fails if the default database contains
     more than one FORTRAN license.

   2.  $ LICENSE MOVE FORTRAN/DATABASE=LMFDATA:LMF$LICENSE.LDB -
       _$ ALT_SYS:LMF$LICENSE.LDB

     This command moves the FORTRAN license in the source LICENSE
     database, LMFDATA:LMF$LICENSE.LDB to the destination LICENSE
     database, ALT_SYS:LMF$LICENSE.LDB. This command fails if the
     source LICENSE database, LMFDATA:LMF$LICENSE.LDB contains more
     than one FORTRAN license.


   3.  $ LICENSE MOVE FORTRAN/ALL ALT_SYS2:LMF$LICENSE.LDB

     This command moves all FORTRAN licenses in the default
     LICENSE database to to the output LICENSE database, ALT_
     SYS2:LMF$LICENSE.LDB.

   4.  $ LICENSE MOVE * ALT_SYS2:LMF$LICENSE.LDB

     This command merges two databases by moving all licenses in the
     default LICENSE database to the output LICENSE database, ALT_
     SYS2:LMF$LICENSE.LDB.

   Adds a new license to the LICENSE database. A Product
   Authorization Key (PAK) provides the product name and information
   you need to register the license. You must enter all information
   provided by your PAK exactly as it appears.

   Often you register a new product license with the command
   procedure SYS$UPDATE:VMSLICENSE.COM, which provides a prompt-based
   interface to the LICENSE REGISTER command.

   Format

     LICENSE REGISTER  product-name

Additional information available:

ParameterQualifiersDescriptionExamples

product-name
   Name of the product with a license to register. You can only
   register licenses that do not currently exist in the LICENSE
   database. You can register multiple licenses for the same product
   when they have different authorization numbers. Enter the product
   name exactly as it appears on your PAK.

   You cannot use wildcard characters for the product-name parameter
   with this command.

Additional information available:

/ACTIVITY/AUTHORIZATION/AVAILABILITY/CHECKSUM
/DATABASE/HARDWARE_ID/ISSUER/OPTIONS/PRODUCER
/RELEASE_DATE/TERMINATION_DATE/TOKEN/UNITS/VERSION

                 { code             }
      /ACTIVITY= { CONSTANT=integer }
                 {                  }

   Specifies a license unit code that corresponds to a License Unit
   Requirement Table or to a constant value. If your PAK supplies an
   activity code, you must enter the code exactly as it appears. The
   current codes are A, B, C, D, E, and F. If your PAK specifies the
   keyword CONSTANT, then you must also specify the integer value.
   This denotes a constant requirement for all System Marketing
   Models (SMMs) equal to the value given. If your PAK specifies
   the decimal value 0, then the license has no requirement for that
   license type. PAK issuers determine the value for this element.

      /AUTHORIZATION=string

   Specifies a string that along with the PAK issuer string uniquely
   identifies the license you want to register. You must enter the
   authorization string exactly as it appears on your PAK.

                     { code             }
      /AVAILABILITY= { CONSTANT=integer }
                     {                  }

   Specifies a license unit code that corresponds to a License Unit
   Requirement Table or to a constant value. If your PAK supplies an
   availability code, you must enter the code exactly as it appears.
   The current codes are A, B, C, D, E, and F. If your PAK specifies
   the keyword CONSTANT, then you must also specify the integer value
   from your PAK. PAK issuers determine the value for this element.

      /CHECKSUM=string

   Specifies a 17-character verification string created by the PAK
   issuer for each PAK. The checksum string is presented in the
   format n-cccc-cccc-cccc-cccc, where n is an integer and c is
   an alphabetic character from A through P. A PAK presents the
   checksum string with hyphen (-)  characters for readability.
   Because LMF does not count them for authorization, you can leave
   them out. Otherwise, you must enter the checksum string exactly as
   it appears on your PAK.

      /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 in an unmodified VMS
   system. This qualifier is optional; use it only if you do not use
   the default database.

      /HARDWARE_ID=string

   Specifies the identification number of the hardware on which the
   product is licensed. If your PAK supplies hardware identification,
   you must enter the information exactly as it appears.

      /ISSUER=string

   Specifies the name of the company (for example, DEC) that issued
   the PAK for the product. Note that the PAK issuer is often the
   same as the producer. You must enter the information exactly as it
   appears on your PAK.

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

   Specifies a LICENSE option or a list of LICENSE options. If your
   PAK supplies any license options, you must enter the information
   exactly as it appears. Current option keywords include the
   following:

   Keyword         Meaning

   MOD_UNITS       The number of license units can be modified.

   NO_SHARE        The license cannot be used by more than one
                   processor in a VAXcluster environment. If this
                   license is used in a cluster, you must designate
                   it for one node using LICENSE MODIFY with an
                   /INCLUDE qualifier.

   RESERVE_UNITS   The license must be assigned to one or more users.
                   Reserve the license by using LICENSE MODIFY with
                   the /RESERVE qualifier.

   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.

      /PRODUCER=string

   Specifies the name of the company (for example, DEC) that owns
   the product for which you have a license. You must enter the
   information exactly as it appears on your PAK.

      /RELEASE_DATE=date

   Specifies a product release date such that the license authorizes
   use of all product versions released on or before the date. If
   your PAK supplies a product release date, you must enter the
   information exactly as it appears. The date must be presented
   in the standard VMS format: dd-mmm-yyyy.

   This qualifier replaces the obsolete qualifier /DATE=date.

      /TERMINATION_DATE=date

   Specifies the date on which the product license terminates. If
   your PAK supplies a license termination date, you must enter it
   exactly as it appears. The date must be presented in the standard
   VMS format: dd-mmm-yyyy.

   This qualifier replaces the obsolete qualifier /TERMINATION=date.

      /TOKEN=string

   Specifies a string of information associated with some products.
   This option can enable or disable certain product features. See
   your product documentation for details. If your PAK provides token
   information, you must enter it exactly as it appears.

      /UNITS=number

   Specifies the number of license units for your license. You must
   enter the number exactly as it appears on your PAK even if your
   PAK specifies the MOD_UNITS option.

      /VERSION=nn.nn

   Limits the version number of the product for which you have a
   license. Use the format integer.integer. If your PAK supplies
   version information, you must enter it exactly as it appears.

   The LICENSE REGISTER command is the primary LICENSE command.
   Before you enter a LICENSE REGISTER command, you need a Product
   Authorization Key (PAK) that supplies the information required to
   enter a license in the LICENSE database.

   You can register additional licenses for products that already
   exist in the LICENSE database, but if you have a PAAM use the
   LICENSE AMEND command. If you register another combinable license
   in the LICENSE database, LMF combines the license units during a
   LICENSE LOAD or LICENSE START command. This allows more product
   availability or activity for the same product.

   The checksum number supplied with your PAK is calculated from the
   other information supplied with the PAK. Thus, you must enter each
   qualifier necessary to supply information from your particular
   PAK. If you enter the LICENSE REGISTER command without a required
   qualifier, LMF returns a checksum error.

                                  NOTE

      Enter the LICENSE REGISTER commands carefully. LICENSE
      REGISTER command strings can be very long, and can require
      a hyphen (-) character at the end of each line if they will
      not fit on one line. Because LMF may return only a checksum
      error when you omit or incorrectly enter information, you
      should carefully check the characters typed on each line
      before you press Return. You can eliminate some typing by
      using the command procedure SYS$UPDATE:VMSLICENSE.COM.

   1.  $ LICENSE REGISTER FORTRAN  /ISSUER=DEC  /AUTHORIZATION=USA-10 -

       _$ /PRODUCER=DEC /UNITS=400 /VERSION=5.4 -
       _$ /AVAILABILITY=F /CHECKSUM=1-HIDN-INDA-COMP-DAHH

     This command adds the license for the product FORTRAN to the
     default LICENSE database. FORTRAN becomes licensed using the
     availability formula with 400 license units available.

   2.  $ LICENSE REGISTER  DVNETRTG /ISSUER=DEC  /AUTHORIZATION=USA-15 -

       _$ /PRODUCER=DEC /UNITS=1000 /VERSION=4.0 -
       _$ /AVAILABILITY=E/CHECKSUM=1-COOD-AGON-EFIC-HING

     This command adds the license for the product DVNETRTG (DECnet
     VAX Routing) to the default LICENSE database. In the example,
     DVNETRTG is licensed using the availability formula with 1000
     license units.

   Sets up the License Unit Requirement Table (LURT) for your system,
   and activates all licenses that are registered and enabled in
   the LICENSE database. Because the VMS operating system issues a
   LICENSE START command during system startup, you should need this
   command only if system startup fails.

   To use this command you need the privileges to change mode to
   kernel (CMKRNL) and to create system logical names (SYSNAM), and
   system privileges (SYSPRV).

   To activate the licenses in the LICENSE database of a system with
   LMF already started, use LICENSE LOAD.

   Format

     LICENSE START

Additional information available:

QualifiersExample

Additional information available:

/DATABASE/LOG

      /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 VMS
   system. This qualifier is optional; use it only if you do not use
   the default database.

      /LOG (default)
      /NOLOG

   Controls whether the LICENSE START command displays a message to
   acknowledge the activation of each product license.

   $ LICENSE START

     This command sets up the LURT for your system, and activates
     all the licenses that are registered and enabled in the LICENSE
     database.

   Deactivates a license, making the product unavailable from the
   current node. The product license or licenses must be registered
   in the LICENSE database, and must have been previously activated
   with an interactive or automatic LICENSE LOAD command. The LICENSE
   UNLOAD command has no effect on active processes.

   To use this command, you need the privileges to change mode to
   kernel (CMKRNL) and to create system logical names (SYSNAM), and
   system privileges (SYSPRV).

   Format

     LICENSE UNLOAD  product-name[,...]

Additional information available:

ParameterQualifiersDescriptionExamples

product-name[,...]
   Name or names of the licensed product to be deactivated. You can
   only unload the licenses that have been activated. Enter the
   product names exactly as they appear on your PAKs. You cannot
   use wildcard characters for the product-name parameter.

Additional information available:

/LOG/PRODUCER

      /LOG
      /NOLOG

   Controls whether the LICENSE UNLOAD command displays the name of
   each license that it unloads.

   By default, the LICENSE UNLOAD command does not display the names
   of licenses that it unloads.

      /PRODUCER=string

   Positional qualifier.

   Specifies the name of the company (for example, DEC) that owns the
   product for which you have a license. The default string for this
   qualifier is DEC. If DEC is not the producer of the product, you
   must use this qualifier to identify the product. This qualifier
   affects only the product name that immediately precedes it in the
   command string. Wildcard characters are not allowed.

   The LICENSE UNLOAD command affects all units for a single product
   even if the loaded units are combined from multiple licenses. In
   such a case, you cannot unload the units from a single license.
   You must unload all the units.

   1.  $ LICENSE UNLOAD/PRODUCER=DEC FORTRAN

     This command deactivates the FORTRAN license on the node from
     which it is entered.


   2.  $ LICENSE UNLOAD PASCAL,FORTRAN

     This command deactivates the Pascal and FORTRAN licenses on the
     node from which it is entered.

Following is an alphabetical list of the messages generated by the
License Management Utility (LICENSE), explanations of the messages,
and recommended user action.

Additional information available:

AIDEST, ‘product’ ‘authorization’ not transferred, already in databaseALREADYLOADED, ‘producer’ ‘product’ license has already been loaded
ALREADYSTARTED, the License Management Facility has already been startedAMBIG, information provided was ambiguous; multiple licenses were found
BADCHECKCHAR, invalid checksum character was specifiedBADCHK, checksum does not validate for ‘product’
BADDATE, invalid date was specified for ‘product’BADLDB, error reading license database ‘database-name’
BADLDBWRIT, error writing to license database ‘database-name’BADLURT, error reading License Unit Requirement Table ‘table-name’
BADOPTION, invalid option was specified-‘option-name’BADOUT, error writing to output file ‘file-name’
CANCELED, ‘product’ ‘authorization’ has been canceledCOPIED, ‘product’ ‘authorization’ has been copied
CORRUP, consistency error was found in LICENSE databaseCORRUPREC, ‘product’ ‘authorization’ record has been corrupted
DELETED, ‘product’ ‘authorization’ has been deletedDISABLED, ‘product’ ‘authorization’ has been disabled
DUPREC, license is already registeredEMTLDB, LICENSE database contains no license records
ENABLED, ‘product’ ‘authorization’ has been enabledEXCEEDED, attempted usage exceeds active license limits
HISDELETED, ‘product’ ‘authorization’ history has been deletedILLSELECT, invalid table selector was specified-‘table-selector’
INTERINJ, internal LMF error was encountered. Checkpoint ‘number’INVALID DATE, license is invalid for this product release date
INVALID VERSION, license is invalid for this version of the productISSUED, ‘product’ ‘authorization’ has been issued
LDBPRES, LICENSE database already presentLISTERR, requested list type doesn’t match stored list type
LOADED, ‘producer’ ‘product’ was successfully loaded withLONGLIST, reserve list for ‘product’ ‘producer’ exceeds maximum
MODIFIED, ‘product’ ‘authorization’ has been modifiedMODUNITS, number of units cannot be modified for ‘product’
MOVED, ‘product’ ‘authorization’ has been movedNOAUTH, ‘producer’ ‘product’ use is not authorized on this node
NOCOMB, multiple licenses could not be combined for ‘product’NODELETE, ‘product’ was not deleted, no matching records found
NOENABLE, ‘product’ has been canceled; it cannot be enabled.NOENT, no license was loaded for this product
NOEXCL, EXCLUDE list not permitted with NO SHARE option,NOINC, INCLUDE list must specify exactly one node for ‘product’
NOLDB, error opening LICENSE database ‘database-name’NOLIC, no license was found for this product
NOLICENSE, no license is active for this software productNOLOAD, license was not loaded for ‘product’
NOLURT, error opening License Unit Requirement Table ‘table-name’NOPRIV, insufficient privileges for this operation. CMKRNL,
NOREMOVE, ‘name’ was not removed, not in ‘product’ listNORESERVE, RESERVE list required for ‘product’ to be loaded
NOSTART, licensing cannot be startedNOT STARTED, License Management Facility is not started
NOWILD, no wildcard permitted - ‘product’RNF, the specified license was not found for ‘product’
SYSMGR, please see your system managerTERM, ‘product’ ‘authorization number’ license has terminated
TERMINATED, license has terminatedUNLOADED, ‘product’ ‘authorization’ has been unloaded

   Facility: LMF, License Management Facility

   Explanation: You attempted to copy or move a license to a license
   database that already includes the specified license.

   User Action: One of the following two actions is appropriate:

   o  If you made an error specifying the license or destination
      license database, reenter the command correctly.

   o  If the license you intended to move or copy is already in the
      destination license database, disable or delete the license
      in the source database according to the intentions of your
      original command. A LICENSE MOVE command deletes the original
      license; a LICENSE COPY command disables the original license.

   Facility: LMF, License Management Facility

   Explanation: You attempted to activate a license that was already
   activated with an automatic or interactive LICENSE LOAD command.
   For example, if you amend a license and then try to activate it,
   you receive this message; before activating the amended license,
   you must first deactivate it with a LICENSE UNLOAD command.

   Remember also, LICENSE LOAD activates all combinable licenses.
   Before you can activate a new license for a product with a license
   already active on the node, you must first enter a LICENSE UNLOAD
   command.

   User Action: None.

   Facility: LMF, License Management Facility

   Explanation: You attempted to start the License Management
   Facility, but it had already been started. By default, LMF starts
   at system startup.

   User Action: None.

   for `product'

   Facility: LMF, License Management Facility

   Explanation: You attempted to execute an LMF command, but did not
   specify enough information to uniquely identify the product.

   User Action: Specify more information about the product. You
   always uniquely identify a product when you specify the producer,
   product name, issuer, and authorization string.

   -`checksum-character'

   Facility: LMF, License Management Facility

   Explanation: You entered an invalid checksum. This message
   displays the invalid character.

   User Action: Enter the correct checksum string.

   Facility: LMF, License Management Facility

   Explanation: When you attempted to register a license, the
   checksum did not validate the other license information you
   entered. The checksum contains, in encrypted form, all license
   information from the PAK. If you enter inaccurate license
   information, you receive this message.

   User Action: Carefully review all licensing information on the
   PAK. When you register the license, you must enter all information
   exactly as it appears on the PAK.

   Facility: LMF, License Management Facility

   Explanation: Using LICENSE MODIFY (or CANCEL/TERMINATION_DATE) you
   attempted to set a PAK termination date with a date later than the
   original PAK termination date. For example, if a PAK terminates on
   1-JUL-1990 you cannot change it to 1-SEP-1991.

   User Action: Check the termination date of the database, and
   reenter the command with a valid date.

   Facility: LMF, License Management Facility

   Explanation: LMF encountered an error while attempting to read the
   LICENSE database. An RMS message follows this message.

   User Action: See your system manager. The system manager should
   analyze the RMS message and, if necessary, restore the database
   from a backup copy.

   Facility: LMF, License Management Facility

   Explanation: LMF encountered an error while trying to write to the
   LICENSE database. An RMS message follows this message.

   User Action: See your system manager. The system manager should
   analyze the RMS message and respond appropriately. The appropriate
   action depends on the RMS message; the appropriate action could
   be only to wait a few minutes and enter the command again (for
   example, if the file is locked).

   Facility: LMF, License Management Facility

   Explanation: LMF encountered an error while attempting to read
   the License Unit Requirement Table. An RMS message follows this
   message.

   User Action: See your system manager. The system manager should
   analyze the RMS message and, if necessary, restore the License
   Unit Requirement Table (SYS$COMMON:[SYSEXE]LMF$LURT.DAT) from a
   backup copy.

   Facility: LMF, License Management Facility

   Explanation: You specified an invalid keyword for licensing
   options.

   User Action: Review the options as listed on the PAK, and reenter
   the code correctly.

   Facility: LMF, License Management Facility

   Explanation: You entered a LICENSE ISSUE command with the /OUTPUT
   qualifier; LMF encountered an error while attempting to write to
   the specified output file. An RMS message follows this message.

   User Action: Analyze the RMS message to determine the appropriate
   action.

BADPAK, PAK is for an unsupported license type and cannot be registered

   Facility: LMF, License Management Facility

   Explanation: You attempted to activate a license with attributes
   that LMF does not support. This license uses an unsupported
   mixture of license types or options.

   User Action: You need a different PAK, one that LMF can use.

BADVERSION, illegal version was specified

   Facility: LMF, License Management Facility

   Explanation: You entered a LICENSE LIST command with the /VERSION
   qualifier and incorrect syntax. The /VERSION qualifier uses the
   format integer.integer. You can specify wildcard syntax as *.* but
   not * alone.

   User Action: Reenter the LICENSE LIST/VERSION command using the
   correct syntax.

   Facility: LMF, License Management Facility

   Explanation: This is an information message returned when you
   enter a command with the /LOG qualifier. The specified license has
   been CANCELED.

   Facility: LMF, License Management Facility

   Explanation: This is an information message returned when you
   enter a command with the /LOG qualifier. The specified license has
   been COPIED.

   Facility: LMF, License Management Facility

   Explanation: LMF detected an inconsistency in the LICENSE
   database. You may have been attempting to activate a license (as
   occurs during system startup) while another process is changing a
   record in the LICENSE database. There can also be data corruption
   in the LICENSE database.

   User Action: If the problem occurred because of simultaneous
   attempts to change and activate a license, you must ensure no
   records are being changed when you reenter the LICENSE LOAD
   command. If you continue to receive this message, see your system
   manager. If necessary, the system manager can restore the database
   (SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB) from a backup copy.

   Facility: LMF, License Management Facility

   Explanation: A portion of the specified license record (or
   records) has been corrupted. The corruption may have been caused
   when the license was modified using an earlier version of LMF.

   User Action: Use the LICENSE CREATE command to create a temporary
   license database. Use the LICENSE MOVE command to move the
   corrupted record (license) to the temporary database. Then use
   LICENSE MOVE again to return the license to the original database.
   This should remove the corruption.

   Facility: LMF, License Management Facility

   Explanation: This is an information message returned when you
   enter a command with the /LOG qualifier. The specified license has
   been DELETED.

   Facility: LMF, License Management Facility

   Explanation: This is an information message returned when you
   enter a command with the /LOG qualifier. The specified license has
   been DISABLED.

   Facility: LMF, License Management Facility

   Explanation: You attempted to register a license that was
   already registered. That is, you attempted to register a license
   identified by the same PAK issuer string and authorization number
   as a current license.

   User Action: None.

   Facility: LMF, License Management Facility

   Explanation: You attempted to activate a license, but no license
   records exist in the LICENSE database.

   User Action: You must register licenses before you can activate
   them. You receive this message at system startup if you have not
   yet registered any licenses.

   Facility: LMF, License Management Facility

   Explanation: This is an information message returned when you
   enter a command with the /LOG qualifier. The specified license has
   been ENABLED.

   Facility: LMF, License Management Facility

   Explanation: A license exists for the product, but one of the
   following two problems occurred:

   o  You attempted to activate a license on a processor that
      requires more license units to provide availability than the
      units currently registered for the product. This message can be
      generated at system startup or when you enter a LICENSE LOAD
      command.

   o  You attempted to access a product with an activity license.
      The product license specifies activity authorization, and
      there were insufficient units on your system to permit another
      concurrent user of the product.

   User Action: For the first case described, see your system
   manager. For the second case described, access the product when
   other users have finished using it.

   Facility: LMF, License Management Facility

   Explanation: This is an information message returned when you
   enter a command with the /LOG qualifier. The history records for
   the specified license have been deleted.

   Facility: LMF, License Management Facility

   Explanation: You entered an invalid activity or availability code.
   You enter activity and availability codes using the /ACTIVITY and
   /AVAILABILITY qualifiers to the LICENSE commands, or in response
   to prompts from the command procedure VMSINSTAL or VMSLICENSE.

   User Action: Review the activity or availability code listed on
   the PAK, and reenter the code. You may need to contact your PAK
   issuer.

   Facility: LMF, License Management Facility

   Explanation: An internal LMF problem exists.

   User Action: Submit a Software Performance Report (SPR) and
   include the checkpoint number from the error message. Contact
   your system manager.

   Facility: LMF, License Management Facility

   Explanation: The license release date is earlier than the product
   release date; the license does not authorize use of this version
   of the product.

   User Action: See your system manager. A Product Authorization
   Amendment (PAAM) may not be registered and loaded, or a new
   license for the product may have been obtained but not registered.
   Your system manager may need to install an earlier version of the
   software or contact Digital for a new PAK.

   Facility: LMF, License Management Facility

   Explanation: The version number on the license is lower than
   the product version; the license does not authorize use of this
   version of the product.

   User Action: See your system manager. A Product Authorization
   Amendment (PAAM) may not be registered and loaded, or a new
   license for the product may have been obtained but not registered.
   Your system manager may need to install an earlier version of the
   software or contact Digital for a new PAK.

   Facility: LMF, License Management Facility

   Explanation: This is an information message returned when you
   enter a command with the /LOG qualifier. The specified license has
   been ISSUED.

   Facility: LMF, License Management Facility

   Explanation: You are attempting to create a LICENSE database that
   already exists.

   User Action: None.

   for `product'

   Facility: LMF, License Management Facility

   Explanation: You attempted to use a MODIFY/ADD or MODIFY/REMOVE
   command with a license that does not have the specified type of
   list. For example, you attempted to remove a license from an
   exclude list when the license was previously modified to have
   an include list instead of an exclude list. This error also occurs
   when you try to remove a name from a list that does not already
   exist.

   User Action: Use the LICENSE LIST command to display include,
   exclude, and reservation lists for a license, and reenter the
   command using the appropriate qualifiers.

   `unit-total' units

   Facility: LMF, License Management Facility

   Explanation: LMF successfully activated the license. This message
   displays the total number of units for the product.

   User Action: None.

   of `number', `number' names removed

   Facility: LMF, License Management Facility

   Explanation: A reservation list or combined reservation lists for
   a license includes too many names. When a LICENSE LOAD command
   was entered LMF checked this list and eliminated one or more names
   from the activated reservation list.

   User Action: Modify the reservation list or lists to have
   fewer names. Check for repeated names; LMF does not check for
   redundancies.

   Facility: LMF, License Management Facility

   Explanation: This is an information message returned when you
   enter a command with the /LOG qualifier. The specified license has
   been MODIFIED.

   Facility: LMF, License Management Facility

   Explanation: You attempted to change the number of units for a
   license that does not include the MOD_UNITS option.

   User Action: Verify that you are modifying the correct license.
   You cannot change the number of units for a license that does not
   include the MOD_UNITS option. Use a LICENSE LIST /FULL command to
   check for this option.

   Facility: LMF, License Management Facility

   Explanation: This is an information message returned when you
   enter a command with the /LOG qualifier. The specified license has
   been MOVED.

   Facility: LMF, License Management Facility

   Explanation: You do not have an active license that authorizes use
   of this product on the current node.

   User Action: See your system manager to find out if a license
   exists for the product.

   Authorization: `authorization-number'

   Facility: LMF, License Management Facility

   Explanation: LMF could not combine licenses. Not all licenses
   for a product can be combined. Following are the only fields that
   can differ among licenses: units, termination date, release date,
   version number, comments, and include, exclude, and reservation
   lists.

   User Action: See your system manager to determine if all licenses
   for the product are still valid.

   Facility: LMF, License Management Facility

   Explanation: The license specified with a LICENSE DELETE command
   was not found.

   User Action: Check the name or names of the licenses, and reenter
   the command.

   Facility: LMF, License Management Facility

   Explanation: You cannot use the LICENSE ENABLE command to reverse
   the actions of the LICENSE CANCEL command.

   User Action: Use the LICENSE CANCEL command with a new date to
   change the status of a user-canceled license.

   Facility: LMF, License Management Facility

   Explanation: You attempted to deactivate a license with a LICENSE
   UNLOAD command. However, no license that matches the one specified
   in the command is currently active.

   User Action: Use the SHOW LICENSE command to verify that a license
   for the product has been activated. One of the following two
   actions is appropriate:

   o  If you think you made an error specifying the license, reenter
      the command.

   o  If you are deactivating the license for a product and the
      producer is not DEC, you must specify the name of the producer
      in the LICENSE UNLOAD command. (DEC is the default value for
      the producer.)

   use an INCLUDE list for `product' to be loaded

   Facility: LMF, License Management Facility

   Explanation: You attempted to activate, in a VAXcluster, a NO_
   SHARE license that was modified using the LICENSE MODIFY command;
   when you entered the LICENSE MODIFY command, you did not specify
   an include list of exactly one node.

   User Action: Specify exactly one node name with the LICENSE
   MODIFY/INCLUDE=node-name command.

   to be loaded

   Facility: LMF, License Management Facility

   Explanation: You attempted to activate, in a VAXcluster, a
   NO_SHARE license that was modified using the LICENSE MODIFY
   command; when you entered the LICENSE MODIFY command, you did
   not specify an include list of exactly one node.

   User Action: Specify exactly one node name with the LICENSE
   MODIFY/INCLUDE=node-name command.

   Facility: LMF, License Management Facility

   Explanation: LMF could not find the LICENSE database you
   specified.

   User Action: Check the name of the database, and reenter the
   command.

   Facility: LMF, License Management Facility

   Explanation: You attempted to activate, amend, or modify a
   license, but no license matches the one you specified.

   User Action: Use the LICENSE LIST command to verify that the
   license exists, and then reenter the command.

   Facility: LMF, License Management Facility

   Explanation: A license for the product has not been activated with
   an automatic or interactive LICENSE LOAD command.

   User Action: See your system manager to determine if the required
   license has been obtained. If so, ask the system manager to
   register and activate the license.

   Facility: LMF, License Management Facility

   Explanation: You entered a LICENSE LOAD or LICENSE START command,
   and LMF was unable to activate a license. Typically, LMF displays
   this message when it finds insufficient units to activate the
   license.

   User Action: If you expected the license to be activated
   successfully, review the license information for the product.
   If the license is a ClusterWide license, units may have been
   previously allocated to other nodes.

   Facility: LMF, License Management Facility

   Explanation: LMF could not find the License Unit Requirement
   Table.

   User Action: See your system manager. The table might have been
   deleted or renamed. If necessary, the system manager can restore
   the table from a backup copy.

   SYSNAM, and SYSPRV are required

   Facility: LMF, License Management Facility

   Explanation: You attempted to enter a LICENSE command for which
   you have insufficient privileges.

   User Action: See your system manager. You must obtain the
   following privileges to successfully enter the command: CMKRNL,
   SYSNAM, and SYSPRV.

   Facility: LMF, License Management Facility

   Explanation: Using a LICENSE MODIFY/REMOVE command you specified
   a user name or node name that is not in the include, exclude, or
   reservation list.

   User Action: Check the name carefully and reenter the command
   using an existing name with the /REMOVE qualifier.

   Facility: LMF, License Management Facility

   Explanation: You attempted to activate a RESERVE_UNITS license
   that was not modified to have a reservation list.

   User Action: Enter a LICENSE MODIFY/RESERVE command to reserve the
   license, and then activate it with a LICENSE LOAD command.

   Facility: LMF, License Management Facility

   Explanation: LMF encountered an error while attempting to load
   the LURT entry or create the logical name table. You can receive
   this message at system startup or when entering a LICENSE START
   command. An RMS message follows this message.

   User Action: See your system manager. The system manager should
   analyze the RMS message to determine the appropriate action.

   Facility: LMF, License Management Facility

   Explanation: The License Management Facility has not been started.
   By default, the facility starts when STARTUP.COM is executed. The
   system manager can also start the facility using the LICENSE START
   command.

   User Action: Ask your system manager to start the License
   Management Facility.

   Facility: LMF, License Management Facility

   Explanation: You entered a LICENSE LOAD or LICENSE UNLOAD command
   specifying the product parameter with a wildcard character. This
   is not allowed.

   User Action: Specify an exact product name with these commands.

   Facility: LMF, License Management Facility

   Explanation: You entered a LICENSE command but no license record
   matches the one you specified in the command.

   User Action: Use the LICENSE LIST command to verify that the
   license exists, and then reenter the command.

   Facility: LMF, License Management Facility

   Explanation: A licensing problem has occurred that should be
   discussed with your system manager.

   User Action: See your system manager.

   Facility: LMF, License Management Facility

   Explanation: The current date of an active license is later than
   the license termination date; the license is no longer valid.

   User Action: See your system manager. The system manager may have
   canceled the license or obtained a new license without registering
   and loading it.

   Facility: LMF, License Management Facility

   Explanation: The current date of a loaded license is later than
   the license termination date; the license is no longer valid.

   User Action: See your system manager. The system manager may have
   canceled the license or obtained a new license without registering
   and loading it.

   Alternatively, you can verify the product name and producer. If
   you entered the wrong product name, activate the license again.
   If you have products with the same name but different producers,
   specify the name of the producer in the LICENSE LOAD command.

   If you amend a license, make sure you deactivate the license with
   a LICENSE UNLOAD command before you attempt to activate (with the
   LICENSE LOAD command) the license again.

   Facility: LMF, License Management Facility

   Explanation: This is an information message returned when you
   enter a command with the /LOG qualifier. The specified license has
   been deactivated with a LICENSE UNLOAD command.