Document revision date: 19 July 1999 | |
![]() |
![]() ![]() ![]() ![]() |
![]() |
Previous |
Each time you enter a LICENSE MODIFY command with an /INCLUDE or /EXCLUDE qualifier, LMF creates a new list. To edit an existing list, use the /ADD or /REMOVE qualifier in your command line. The following example illustrates the required syntax without using the /ADD or /REMOVE qualifier:
$ LICENSE MODIFY/INCLUDE=(ART,MUSIC,DANCE,THEATR) BASIC - _$ /AUTHORIZATION=USA123456 . . . $ LICENSE MODIFY/INCLUDE=(ART,MUSIC,DANCE,CRAFTS) BASIC - _$ /AUTHORIZATION=USA123456 $ LICENSE UNLOAD BASIC %LICENSE-I-LOADED, DEC BASIC was successfully loaded with 400 units |
You can also use the following commands:
$ LICENSE MODIFY/INCLUDE=(ART,MUSIC,DANCE,THEATR) BASIC - _$ /AUTHORIZATION=USA123456 . . . $ LICENSE MODIFY/REMOVE/INCLUDE=(THEATR) BASIC /AUTHORIZATION=USA123456 $ LICENSE MODIFY/ADD/INCLUDE=(CRAFTS) BASIC /AUTHORIZATION=USA123456 |
If your license uses the MOD_UNITS option, you can also modify the size of a license in a cluster environment. To change the size of the license, enter a LICENSE MODIFY/UNITS=number command that specifies a number sufficient for your needs and allowed by your license agreement. For example, to change a license registered with 1000 license units to a 1500-unit license, enter:
$ LICENSE MODIFY/UNITS=1500 BASIC $ LICENSE LOAD BASIC |
To control which users have access to a product, use the LICENSE MODIFY command with the /RESERVE qualifier. This qualifier takes an argument list of user names called the reservation list. Although the definition of a user can differ from product to product, most products accept the user name that OpenVMS maintains for each account. This is the name you type at the Username prompt during login. See your product's Software Product Description (SPD) for details.
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. Calculate this number as you would for any activity license. For example, if a software product requires 50 license units per activity and your PAK provides 100 license units, you have a 2-activity license. If the PAK also specifies the RESERVE_UNITS option, you have an unlimited activity, two-user license. For this license, you must create a reservation list with at least one, but no more than two, names.
Example:
The following command assigns two users to a reservation list for the
product called Terrapin:
$ LICENSE MODIFY /RESERVE=(R_HUNTER,J_BARLOW) TERRAPIN |
Note that the LICENSE MODIFY command affects only data in the license database; it does not affect licenses already loaded. To affect a loaded license, reload it with a LICENSE LOAD command. For example:
$ LICENSE MODIFY /RESERVE=(R_HUNTER,J_BARLOW) TERRAPIN $ LICENSE LOAD TERRAPIN %LICENSE-I-UNLOADED LICENSE-I-LOADED, DEC TERRAPIN was successfully loaded with 200 units |
To add more user names to the reservation list, use the /ADD qualifier and the /RESERVE qualifier, as follows:
$ LICENSE MODIFY /ADD /RESERVE=(P_LESH,M_HART) TERRAPIN |
This adds new users P_LESH and M_HART to any list already established for the specified product. You can remove a user name with the /REMOVE qualifier.
You can have many Personal Use Licenses for the same product. For license loading, LMF combines all of the license units and determines the number of users according to the total number of units. Therefore, the total number of names on combined reservation lists for this product must not exceed the number LMF authorizes from the unit count, because LMF authorizes only the correct number from the lists and rejects extra names.
Although you can find extra or repeated names using one or more LICENSE LIST/FULL commands, you cannot easily predict which users LMF will reject. Do not assume that LMF denies access to the third name listed on the reservation list of a two-user license. The total number of names and total number of license units is the important calculation.
To load corrections to a reservation list you must enter the LICENSE LOAD command for the licenses. The following example includes the warning message for too many names:
$ LICENSE MODIFY/RESERVE=(R_HUNTER,J_BARLOW) TERRAPIN $ LICENSE LOAD TERRAPIN LICENSE-I-LOADED, DEC TERRAPIN was successfully loaded with 200 units $ LICENSE MODIFY/ADD/RESERVE=(P_LESH,M_HART) TERRAPIN $ LICENSE LOAD TERRAPIN %LICENSE-I-UNLOADED LICENSE-W-LONGLIST, reserve list for DEC TERRAPIN exceeds maximum of 2, 2 names removed LICENSE-I-LOADED, DEC TERRAPIN was successfully loaded with 200 units |
Because LMF combines the license units, you can assign one long
reservation list to a single license; LMF simply adds the license units
from the combinable licenses and counts the names in all reservation
lists for those licenses. If you have three combinable licenses that
authorize use to six users, you can modify one of them to have a 6-name
reservation list. Note that this differs from the behavior of include
and exclude lists with node names in an OpenVMS Cluster.
1.6.4 Controlling Loading Order
If you have many variations of licenses for a product (for example, with different versions, tokens, or hardware identifiers), and you think that you are not getting maximum use of the product, you can check the order of loading of the product licenses. By default, LMF assigns a selection weight to each license and loads each license in descending order of selection weight. The grant order is the order in which LMF checks licenses before loading one. To determine grant order, enter the DCL command SHOW LICENSE/FULL. You can then enter the LICENSE LIST command with the /SELECTION_WEIGHT qualifier to display the selection weight. Modify selection weights of licenses as needed with the /SELECTION_WEIGHT qualifier to the LICENSE MODIFY command.
To change the selection weight, use LICENSE MODIFY/SELECTION_WEIGHT,
and then load the changed licenses with LICENSE LOAD.
1.7 Logical Name LMF$DISPLAY_OPCOM_MESSAGE
A previous version of this manual incorrectly stated that you must define the logical name LMF$DISPLAY_OPCOM_MESSAGE in order for messages to appear.
If you have already defined this logical name, you should delete the definition.
Define the LMF$DISPLAY_OPCOM_MESSAGE logical name only if you are explicitly directed by Digital to do so (for debugging purposes). When defined, this logical name causes many "noise" messages to be displayed on the operator's console. Some of these messages can be confusing and misleading to the point of suggesting that a product is not licensed when in fact it is.
To see if this logical name has been defined on your system, enter the following command:
$ SHOW LOGICAL LMF$DISPLAY_OPCOM_MESSAGE |
To delete the logical name, enter the following command:
$ DEASSIGN LMF$DISPLAY_OPCOM_MESSAGE/EXEC/SYSTEM |
![]() ![]() ![]() ![]() |
privacy and legal statement | ||
4584USING_CH_002.HTML |