Produces a replica of a Product Authorization Key (PAK) that
is sent to a file or displayed on your terminal (the default).
If the terms and conditions of your license contract allow it,
you can then enter this PAK replica in the License Database of
another processor. When you enter LICENSE ISSUE, LMF disables
the license in the current License Database and marks the license
DISABLED. To enable a license that has been marked ISSUED, enter
LICENSE ENABLE.
For License Databases connected to a network, consider using
LICENSE MOVE.
Format
LICENSE ISSUE product-name[,...]
1 – Parameter
product-name[,...]
Name or names of products with a license to be issued. You can
issue only licenses that currently exist in the License Database.
Enter the product name exactly as it appears on your PAK.
2 – Qualifiers
2.1 /ALL
Positional qualifier.
Specifies that all licenses with the given product name should
be issued. This qualifier affects only the product name that
immediately precedes it in the command string.
2.2 /AUTHORIZATION
/AUTHORIZATION=string
Positional qualifier.
Specifies a string that helps identify the license you want to
issue. You must enter the authorization string exactly as it
appears on your PAK. Use this optional qualifier only if you
need it to identify the license. This qualifier affects only the
product name that immediately precedes it in the command string.
2.3 /DATABASE
/DATABASE=filespec
Specifies the location of the License Database. The default file
specification is defined by the logical name LMF$LICENSE, which
points to SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB on an unmodified
OpenVMS system. Use this optional qualifier only if you do not
use the default License Database name and location.
2.4 /ISSUER
/ISSUER=string
Positional qualifier.
Specifies the name of the company (for example, VSI) 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.
2.5 /LOG
/LOG
/NOLOG (default)
Controls whether LICENSE ISSUE displays the name of each license
that it issues.
2.6 /OUTPUT
/OUTPUT[=filespec]
Specifies the name of the file to which your PAK replica is
written. If you do not specify the /OUTPUT qualifier, or if
you do not supply a file specification with this qualifier, the
output is sent to SYS$OUTPUT.
If you specify a file name that already exists, this command
creates a new version of the file. If you specify a complete file
name and version that already exists, this command appends the
PAK replica to the existing file.
2.7 /PROCEDURE
/PROCEDURE
/NOPROCEDURE (default)
Specifies that the PAK replica is to be written in the form of a
DCL command procedure. Use /PROCEDURE with the /OUTPUT qualifier
to create a command procedure in a file. Then you can invoke the
procedure to register the PAK replica in the License Database of
another processor.
If you do not specify the /OUTPUT qualifier with /PROCEDURE,
or if you do not supply a file specification with the /OUTPUT
qualifier, the procedure is sent to SYS$OUTPUT.
2.8 /PRODUCER
/PRODUCER=string
Positional qualifier.
Specifies the name of the company (for example, VSI) 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.
3 – Description
If your license contract allows it, use LICENSE ISSUE to
move a license from a License Database on one processor (or
OpenVMS Cluster environment) to a License Database on another
processor. To move a license, enter LICENSE ISSUE, including
enough PAK information to clearly identify the license. LICENSE
ISSUE automatically disables the current license but does
not immediately unload it; LMF does not terminate any active
processes. To unload the license, enter a LICENSE UNLOAD command.
After you issue the PAK replica, read the information, and
register it on the new processor as you would any PAK, or, if
you used the /PROCEDURE qualifier with the /OUTPUT qualifier,
invoke the new DCL command procedure to register the license.
Note that the PAK replica includes only PAK information
registered with a LICENSE REGISTER command. The replica does
not include any changes made with other LICENSE commands.
4 – Examples
1.$ LICENSE ISSUE /OUTPUT=SYS$MANAGER:FORTRAN.PAK -
_$ /PRODUCER=DEC FORTRAN
This command issues a PAK replica, which you can use to
register the Fortran license on a new processor (or OpenVMS
Cluster environment), and puts it into the file named
FORTRAN.PAK. The next step is to print the file, read the
information, and, using a LICENSE REGISTER command or
VMSLICENSE.COM, enter the correct information in the License
Database of the new processor. The Fortran license in the
current License Database is marked ISSUED and is disabled.
2.$ LICENSE ISSUE /PRODUCER=DEC VOLSHAD
This command displays, at the current terminal, a PAK replica
with the information from the VOLSHAD (Volume Shadowing)
license. This display is reproduced below. The license
registered in the current License Database is marked ISSUED
and is disabled. You can register the data from this replica of
a PAK in the License Database of another processor using either
VMSLICENSE.COM or LICENSE REGISTER.
Software Product Authorization Key Replica
Issued by CASPER
Issued on 24-FEB-2001 14:23
-----------------------------------
Issuer: DEC
Authorization: ALS-WM-93166-5573
Product Name: VOLSHAD
Producer: DEC
Units: 460
Version: 5.4
PAK Termination Date: 31-DEC-2001
Availability: E
Options: MOD_UNITS
Checksum: 1-ADEB-DOCJ-NENC-KDBM
3.$ LICENSE ISSUE /PROCEDURE /OUTPUT=FORTRAN-USA10.COM -
_$FORTRAN /AUTHORIZATION=USA-10
This command generates a DCL command procedure such as the
following to be used for registering the specified license in a
License Database:
$! Software Product Authorization Key Replica
$! Issued by CASPER
$! Issued on 23-Oct-2001 14:23
$ LICENSE REGISTER FORTRAN -
/ISSUER=DEC -
/PRODUCER=DEC -
/AUTHORIZATION=USA-10 -
/UNITS=400 -
/VERSION=5.4 -
/AVAILABILITY=F -
/CHECKSUM=1-HIDN-INDA-COMP-DAHH