 |
HP OpenVMS License Management Utility Manual
Note
You cannot modify selection weights for Availability Licenses.
|
To restore the selection weight of a PAK to the default value, enter
the LICENSE MODIFY command with /SELECTION_WEIGHT=0. For example, you
can use either of the following commands:
$ LICENSE MODIFY FORTRAN /SELECTION_WEIGHT=0
$ LICENSE MODIFY FORTRAN /NOSELECTION_WEIGHT
|
/TERMINATION_DATE=date
Date at which the product license is to be terminated. If your PAK
supplied a license termination date, LMF uses the earliest date to
determine the termination date. The date must be presented in the
standard OpenVMS format: dd-mmm-yyyy. If you want to restrict
a product from further use today, enter yesterday's date; LMF
terminates the license at the end of the day specified.
/UNITS=n
Number of license units you want on a license that includes the
MOD_UNITS option. If your PAK allows you to modify the license units,
use this qualifier to change the value in the License Database.
Description
Use the LICENSE MODIFY command to modify a license. To control which
nodes in a cluster 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 load a license (with a LICENSE
LOAD or LICENSE START command), LMF loads a license on a first-come,
first-served basis. When your license has insufficient license units
for full cluster environment use, control product access with an
include list.
Because most OpenVMS PAKs use the /NO_SHARE option, in a cluster
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 OpenVMS license.
To control which users have access to a product, use LICENSE MODIFY
with the /RESERVE qualifier. You can create and modify a reservation
list for any kind of license. Only users on the reservation lists are
allowed access to the product.
If your PAK 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
(LURTs). Calculate this number as you would for any Activity License.
For example, a 200-unit license with a constant value of 100 is a
two-user license.
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 includes the MOD_UNITS option, you can use the /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.
List Size Restrictions
Two restrictions apply to the size of lists (reservation lists, include
lists, or exclude lists). These restrictions apply to PAKs of all
license types.
- On any single PAK, the sum of characters contained in all lists
must not exceed 5000 characters.
Because the length of names varies
and some overhead is used for each name, this 5000-character limit
cannot be expressed as an exact number of permissible names. However,
HP guarantees that at least 400 names, in total, can be specified in
the various types of lists. For example, each of the following
represents the minimally guaranteed number of names:
- Reservation list with up to 400 user names
- Reservation list with up to 200 user names plus an include list
with up to 200 node names (totaling up to 400)
- Reservation list with up to 200 user names plus an exclude list
with up to 200 node names (totaling up to 400)
- Include list with up to 400 node names
- Exclude list with up to 400 node names
Note
If you enter more names than are permitted, LICENSE LIST might not be
able to display all names entered. In this case, you receive the error
message LICENSE-F-CORRUP. However, the License Database is not actually
corrupt, and the PAKs can still be loaded into memory (though the names
are not displayed).
|
- The LICENSE LOAD and LICENSE START commands can load into memory a
reservation list with no more than 30,000 characters. (Include and
exclude lists, which are not loaded into memory, are irrelevant to the
30,000-character limit.)
Because the length of names varies and
some overhead is used for each name, this 30,000-character limit cannot
be expressed as an exact number of permissible names. But HP guarantees
that, for each product, at least 2000 user names can appear on
reservation lists. In the case of an OpenVMS Cluster, this is a
per-node limit. Note that, because 2000 user names is a per-product
limit and because there can be more than one PAK per product, the
number of user names on a per-product basis is the sum of the
user names specified on each PAK. For example, if three activity
PAKs for the DECwrite product were registered on a system and each PAK
specified a reservation list with 200 user names, the total number of
user names for that product is 600. This is safely below the
30,000-character (2000 user name) limit and below the 5000-character
(400 user name) limit.
Examples
#1 |
$ LICENSE MODIFY /EXCLUDE=(DANCE,THEATR) -
_$ /COMMENT="Modified to exclude nodes DANCE & THEATR 10/23/04" -
_$ 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/04" -
_$ 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 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-2005 FORTRAN
|
Unless an earlier termination date exists, this command sets a new
termination date of 1-JAN-2005 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.
LICENSE MOVE
Moves one or more licenses from one License Database to another. When
you use LICENSE MOVE, LMF deletes those licenses from 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
Parameters
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 LICENSE CREATE.
If you enter a partial file specification (for example, specifying only
a directory), LMF$LICENSE is the default file name, and .LDB is the
default file type. If you do not specify a device or directory, the
current default device and directory are used.
Qualifiers
/ALL
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 helps identify the license you want to modify.
You must enter the authorization string exactly as it appears on your
PAK. Use this optional qualifier only if you need it to identify the
license. This qualifier affects only the product name that immediately
precedes it in the command string.
/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 OpenVMS system. Use
this optional qualifier 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 (default)
Controls whether LICENSE MOVE displays the name of each license 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 it to identify the license. This qualifier affects only the
product name that immediately precedes it in the command string.
Description
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.
LICENSE MOVE automatically deletes the license from the source License
Database.
Note that the moved license includes only the general PAK information
normally provided by LICENSE REGISTER. LICENSE MOVE does not transfer
any user-supplied data such as reservation lists, modified termination
dates, modified units, include or exclude node lists, or comments.
Examples
#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 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 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.
LICENSE REGISTER
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
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.
Qualifiers
/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.
/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.
/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.
/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.
/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.
/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 I64
systems, the HARDWARE_ID string is in the format SOCKETS=n.
/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 LICENSE REGISTER options. If your PAK supplies any license
options, you must enter this information exactly as it appears.
Table A-1 describes the available keywords.
Table A-1 LICENSE REGISTER /OPTIONS 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 I64 systems.
|
IA64_ALPHA
|
Identifies Activity Licenses that are valid for OpenVMS I64 and OpenVMS
Alpha systems.
|
IA64_ALPHA_VAX
|
Identifies Activity Licenses that are valid for OpenVMS I64, 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 I64 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.
/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.
/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.
/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.
/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.
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.
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.
LICENSE START
This command loads all licenses that are registered and enabled in the
License Database into memory. On OpenVMS Alpha and VAX systems, it sets
up the License Unit Requirement Table (LURT) for your system. On
OpenVMS I64 systems, it loads the operating environment table and all
per core licenses into memory. Because the OpenVMS 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 CMKRNL, SYSNAM, and SYSPRV privileges on
OpenVMS Alpha systems. In addition to those three, you also need SYSLCK
privilege on OpenVMS I64 systems.
To load the licenses in the License Database of a system with LMF
already started, use LICENSE LOAD.
Format
LICENSE START
Parameters
None.
Qualifiers
/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 database.
/LOG (default)
/NOLOG
Controls whether LICENSE START displays a message to acknowledge the
loading of each product license.
Example
On OpenVMS Alpha and VAX systems, this command sets up the LURT for
your system and loads all the licenses that are registered and enabled
in the License Database. On OpenVMS I64 systems, this command loads the
operating environment table and all PCL licenses into memory.
|