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.
You can also 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
1 – Parameter
product-name
Name of the product with a license to register. You can register
only 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.
2 – Qualifiers
2.1 /ACTIVITY
/ACTIVITY=code | CONSTANT=integer
Specifies a license unit code that corresponds to a License Unit
Requirement Table (LURT) 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, F, G, H, and I.
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.
2.2 /AUTHORIZATION
/AUTHORIZATION=string
Specifies a string that helps identify the license you want to
register. You must enter the authorization string exactly as it
appears on your PAK.
2.3 /AVAILABILITY
/AVAILABILITY= code | CONSTANT=integer
Specifies a license unit code that corresponds to a License Unit
Requirement Table (LURT) 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, F, G, H, and
I. 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.
2.4 /CHECKSUM
/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 hyphens for authorization, you do not
have to enter them. Otherwise, you must enter the checksum string
exactly as it appears on your PAK.
2.5 /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 in an unmodified
OpenVMS system. Use this optional qualifier only if you do not
use the default database.
2.6 /HARDWARE_ID
/HARDWARE_ID=string
Specifies the identification number of the hardware on which
the product is licensed. If your PAK supplies a hardware
identification number, you must enter the information exactly as
it appears. On Integrity server systems, the HARDWARE_ID string
is in the format SOCKETS=n.
2.7 /ISSUER
/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.
2.8 /OPTIONS
/OPTIONS=[(keyword[,...])]
Specifies LICENSE REGISTER options. If your PAK supplies any
license options, you must enter this information exactly as it
appears.
The following table describes the available keywords.
Keyword Meaning
ALPHA Identifies Availability Licenses for Alpha
systems.
HARD_COMPLIANCE Identifies a license that will enforce
compliance to license terms.
IA64 Identifies Licenses for Integrity server
systems.
IA64_ALPHA Identifies Activity Licenses that are valid
for OpenVMS Integrity servers and OpenVMS Alpha
systems.
IA64_ALPHA_VAX Identifies Activity Licenses that are valid for
OpenVMS Integrity servers, OpenVMS Alpha, and
OpenVMS VAX systems.
MOD_UNITS You can modify the number of license units.
NO_SHARE You cannot use the license on more than one
processor in an OpenVMS Cluster environment.
To use this license in a cluster, designate
it for one node. Issue LICENSE MODIFY with the
/INCLUDE qualifier.
PCL Designates a Per Core License on an OpenVMS
Integrity server system.
RESERVE_UNITS The license must be assigned to one or more
users. Reserve the license using LICENSE MODIFY
with the /RESERVE qualifier.
USER Designates a User License.
VAX_ALPHA Identifies Availability Licenses that are valid
for both OpenVMS VAX and OpenVMS Alpha systems.
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.
2.9 /PRODUCER
/PRODUCER=string
Specifies the name of the company (for example, HP) that owns
the product for which you have a license. You must enter the
information exactly as it appears on your PAK.
2.10 /RELEASE_DATE
/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 OpenVMS format: dd-mmm-yyyy.
2.11 /TERMINATION_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
OpenVMS format: dd-mmm-yyyy.
2.12 /TOKEN
/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.
2.13 /UNITS
/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.
2.14 /VERSION
/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.
3 – Description
LICENSE REGISTER is the primary LICENSE command. Before you enter
a LICENSE REGISTER command, you need a 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. 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 LICENSE REGISTER without a required
qualifier, LMF returns a checksum error.
4 – Examples
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
for OpenVMS Routing) to the default License Database. In the
example, DVNETRTG is licensed using the availability formula
with 1000 license units.