HP OpenVMS License Management Utility Manual
This example displays a list of the names of product licenses in the License
Database on an OpenVMS I64 system.
Use CTRL/Z to exit, PF3-PF4 for Previous-Next Screen, Arrow Keys to scroll. License Management Facility V2.0 License Database File: SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB;1 Created on: 26-FEB-2004 Created by user: USER1 Created by LMF Version: V2.0 ----------------------------------- Issuer: HP Authorization: USA-1715 Product Name: C Producer: HP Units: 3 Version: 0.0 Release Date: (none) PAK Termination Date: 25-SEP-2004 Availability: 0 Activity: 000000001 Options: IA64_ALPHA Product Token: Hardware ID: Revision Level: 1 Status: Active Command: REGISTER Modified by user: SYSTEM Modified on: 2-MAR-2004 04:45:20.79 ----------------------------------- Issuer: HP Authorization: TOPAZ-I64-FT-001 Product Name: DVNETEXT Producer: HP Units: 20 Modified Units: 4 Version: 0.0 Release Date: (none) PAK Termination Date: 6-FEB-2005 Options: IA64, PPL Product Token: Hardware ID: Revision Level: 3 Status: Active Command: MODIFY Modified by user: SYSTEM Modified on: 12-MAY-2004 11:01:13.65 ----------------------------------- Issuer: HP Authorization: TOPAZ-I64-FT-001 Product Name: OPENVMS-I64-FOE Producer: HP Units: 1 Modified Units: 2 Version: 0.0 Release Date: (none) PAK Termination Date: 1-SEP-2004 Options: IA64, PPL Product Token: Hardware ID: Revision Level: 80 Status: Active Command: MODIFY Modified by user: SYSTEM Modified on: 9-MAY-2004 08:52:48.35
|
| #3 |
$ LICENSE LIST /HISTORY FORTRAN
|
This example displays a listing with full information of a current Fortran
license issued by HP.
The first screen, shown here, displays the most recent license record for
the Fortran license. To see the history records one screen at a time, press
Return. The revision level of the displayed record is 2, and the status is
Active. The next screen would display the previous license record with a
revision level of 1 and a status of Extinct.
Use CTRL/Z to exit, PF3-PF4 for Previous-Next Screen, Arrow Keys to scroll. License Management Facility V1.2 License Database File: ART::SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB Created on: 17-AUG-2000 Created by user: USER_2 Created by LMF Version: V1.2 ----------------------------------------------------- Issuer: DEC Authorization: USA-2468 Product Name: FORTRAN Producer: DEC Units: 0 Modified Units: 2000 Version: 5.4 Release Date: (none) PAK Termination Date: 31-DEC-2000 Modified Termination Date: 30-NOV-2001 Availability: F (Layered Products) Activity: 0 Options: MOD_UNITS Hardware ID: Revision Level: 2 Status: Active Command: MODIFY Modified by user: DEGAS Modified on: 19-AUG-2000 14:32:23.41 Include: ART
|
LICENSE LOAD
Loads licenses,
making them available for product authorization on the current node. The product
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,
unloads the license, and then loads the license.
To use this command, you need CMKRNL, SYSNAM, and SYSPRV privileges.
Format
LICENSE LOAD [product-name][,...]
Parameter
[product-name][,...]
Name or names of products with a license to be loaded. You can load only licenses
that are currently registered and enabled in the License Database. Enter the
product name exactly as it appears on your Product Authorization Key (PAK).
If you do not specify a product name, LICENSE LOAD loads all of the products
that are registered and enabled.
You cannot use wildcard characters for product-name.
Qualifiers
/AUTHORIZATION=string
Positional qualifier.
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.
This qualifier affects only the product name that immediately precedes it
in the command string.
/DATABASE=filespec
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.
/ISSUER=string
Positional qualifier.
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 (default)
/NOLOG
Controls whether or not LICENSE LOAD displays a message to acknowledge the
loading of each license.
/OEDB - I64 only
Using this qualifier refreshes the contents of the OE database. The contents
of the OE database are described in a datafile (LMF$OE.DAT). If new variants
of operating environments become available, HP will provide a new datafile
with information on the new or changed operating environments. Using LICENSE
LOAD/OEDB updates your OE database without having to reboot the system.
/PRODUCER=string
Positional qualifier.
Name of the company 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.
/UNLOAD (default)
/NOUNLOAD
When requested to load a license that is currently loaded, LMF first automatically
unloads it and then loads the latest license.
You can specify /NOUNLOAD to verify whether or not there is already a license
loaded; LMF issues the warningLICENSE-W-ALREADYLOADED and
does not load the license. To then load the license, follow these steps:
- Manually unload the current license with the LICENSE UNLOAD command.
- Reissue the LICENSE LOAD command.
Description
The LICENSE LOAD command loads licenses registered in the License
Database. To use a licensed product, ensure that the system loads the registered
license. When you register a license with VMSLICENSE.COM, you can confirm an
option to load the license, whereas if you register a license with LICENSE
REGISTER, you must also load it with LICENSE LOAD.
Use LICENSE LOAD only after you register a new license; LMF automatically
loads all registered licenses at each subsequent system startup. You can
enter LICENSE LOAD at other times to load modifications made with other LICENSE
commands.
You can enter one LICENSE LOAD command without product-name to
load all the available registered licenses.
Note
Registered licenses are enabled for loading by default.
You can, however, disable a registered license to prevent loading. |
A LICENSE START command entered interactively or when the system reboots
also loads all licenses that are registered and enabled.
If you register multiple licenses for a single
product, LICENSE LOAD loads all of the matching licenses. You do not typically
load individual licenses, and you cannot unload individual licenses for a
product. The Availability, Activity, Personal Use, and User license units
of the multiple licenses work in concert to provide more product availability.
In an OpenVMS Cluster environment, each system loads licenses when it reboots.
If you need to load a license for all assigned nodes of a running cluster,
you can do one of the following:
- Log in to each OpenVMS Cluster node, and enter
LICENSE LOAD.
- Invoke the OpenVMS SYSMAN utility to execute the LICENSE LOAD command
on the desired OpenVMS Cluster nodes. See the HP OpenVMS System Manager's
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 the operator communication
manager (OPCOM) for any of the following reasons:
- Insufficient license units are registered for the current node.
- The current date is later than the license termination date.
- A license checksum does not match the rest of the license data. Check
for data corruption in the License Database.
If you attempt to load a disabled license or a license modified to exclude
the current node in an OpenVMS Cluster environment, OPCOM does not display
an error message.
If licenses for more than one product are being loaded, LICENSE LOAD continues
with the next license following a failure.
Examples
| #1 |
$ LICENSE MODIFY /INCLUDE=MUSIC FORTRAN$ LICENSE LOAD FORTRAN
|
The commands in this example illustrate a situation in which you enter a
LICENSE LOAD command interactively. LICENSE LOAD loads the product Fortran
on the node MUSIC. Data in the License Database determines whether the license
is successfully loaded 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 load the product BASIC, but LICENSE LOAD fails
because too few license units are registered to authorize use on the current
processor.
LICENSE MODIFY
Modifies a license for system management and license-sharing purposes.
Immediately changes data in the License Database, but your modifications do
not affect the running system until you load the modified license.
Format
LICENSE MODIFY qualifier[,...] product-name[,...]
Parameter
product-name[,...]
Name or names of products with a license to be modified. You can modify only
licenses that currently exist in the License Database.
Qualifiers
/ADD
Used with the /INCLUDE or /EXCLUDE qualifier, 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.
/ALL
Positional qualifier.
Modifies all the licenses with the given product name. 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.
/COMBINE
/NOCOMBINE
Modifies a PAK by adding or removing the COMBINE option. If the PAKs are combinable,
LMF combines them during license loading.
/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 OpenVMS system. Use this optional qualifier 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 an OpenVMS Cluster environment cannot
access the licensed product. The excluded nodes cannot load (with a LICENSE
LOAD or LICENSE START command) the license registered in the License Database.
Each node-name argument must be a System Communications Services
(SCS) node name or 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.
You can control license access to nodes with /EXCLUDE and control user access
with /RESERVE, but you cannot use these qualifiers on the same command line.
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 an OpenVMS Cluster environment can
access the licensed product. Only the included nodes can load (with a LICENSE
LOAD or LICENSE START command) the license registered in the License Database.
Each node-name argument must be an SCS node name, or a system
parameter set with SYSGEN. The node name might not be the same as the DECnet
node name.
Licenses for the OpenVMS operating system usually specify the NO_SHARE option
on their PAKs. In a cluster environment you must restrict each of these OpenVMS
licenses to a single node. If you did not do this when registering with VMSLICENSE.COM,
enter LICENSE MODIFY/INCLUDE=node-name, specifying one SCS node
name for each OpenVMS license.
To 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.
You can control license access to nodes with /INCLUDE and control user access
with /RESERVE, but you cannot use these qualifiers on the same command line.
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 qualifier only if it is required 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 MODIFY displays the name of each license that it modifies.
/NO_SHARE
/NONO_SHARE
Specifies whether to add or subsequently remove /NO_SHARE from a PAK. Adding
/NO_SHARE prevents the sharing of the PAK units with other cluster nodes.
PAKs with /NO_SHARE require you to provide the SCS node name of the cluster
node that will be using this particular license. See the /INCLUDE qualifier
for more information.
Note that if /NO_SHARE is present on your PAK when you register it, you
cannot remove the option using /NONO_SHARE. Only if you add /NO_SHARE with
the MODIFY command, can you subsequently remove it.
/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.
/REMOVE
Used with the /INCLUDE or /EXCLUDE qualifier, 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 (SPD) for details.
Most products define user-name to be the user name OpenVMS
maintains for each account. This is the name you type at the Username prompt
during login.
If
your PAK specifies the RESERVE_UNITS option, you must assign one
or more users to a reservation list. On OpenVMS Alpha and VAX systems, 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. On
OpenVMS I64 systems, units are expressed in single units that directly correlate
to the contant value listed.
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
are denied access.
Although you can control license access to nodes with /INCLUDE and /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.
/SELECTION_WEIGHT=number
Modifies the selection weight. Selection-weight values determine the order
in which LMF checks multiple licenses when a product makes a license grant
request. LMF checks higher-weighted licenses before lower-weighted ones. Specify
arbitrary numbers between 1 and 1000.
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
|
|
