Document revision date: 19 July 1999

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

2.6.3 Controlling User Access

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.

2.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.

2.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

This appendix describes the syntax of the following License Management utility (LICENSE) commands:

• LICENSE COPY
• LICENSE CREATE
• LICENSE DELETE
• LICENSE DISABLE
• LICENSE ENABLE
• LICENSE ISSUE
• LICENSE LIST
• LICENSE LOAD
• LICENSE MODIFY
• LICENSE MOVE
• LICENSE REGISTER
• LICENSE START
• LICENSE UNLOAD

LICENSE COPY

Copies licenses from one License Database to another. When you use LICENSE COPY, LMF disables the source license and registers a copy in the destination License Database as if it were a new license. If the terms and conditions of your license contract allow it, you can re-enable the source database license by using LICENSE ENABLE.

LICENSE COPY cannot be used to create a copy of a license in the same database as the source of the copy.

Format

LICENSE COPY product-name[,...] output-database

Parameters

product-name[,...]

Name or names of products with a license to be copied to the output License Database.

output-database

File specification of the License Database to which the license or licenses should be copied. 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 copied. 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 copy. 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 should be copied. 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 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 COPY displays the name of each license that it copies.

/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 to identify the license. This qualifier affects only the product name that immediately precedes it in the command string.

Description

To copy a license from one database to another, use LICENSE COPY. The following conditions apply to a LICENSE COPY transaction:

• The status of the source database license changes to disabled.
• Network copies are supported within the limits of remote FAL access. If you use access control strings, such as "USERNAME password" within the file specification, the actual password string is not stored.
• LICENSE COPY does not transfer any user-supplied data such as reservation lists, modified termination dates, modified units, include or exclude node lists, or comments.

Examples

$ LICENSE COPY FORTRAN BACKUP_DATA:BACKUP.LDB
      

This command copies the Fortran license in the default License Database to the BACKUP_DATA:BACKUP.LDB License Database. This command fails if there is more than one Fortran license in the default database.

$ LICENSE COPY FORTRAN/DATABASE=BACKUP_DATA:BACKUP.LDB -
_$ BACKUP_DATA2:BACKUP2.LDB
      

This command copies the Fortran license in the source License Database to the BACKUP_DATA2:BACKUP2.LDB License Database. This command fails if there is more than one Fortran license in the source database.

$ LICENSE COPY FORTRAN/ALL BACKUP_DATA:BACKUP.LDB
      

This command copies all Fortran licenses in the default License Database to the BACKUP_DATA:BACKUP.LDB License Database.

$ LICENSE COPY FOR*  BACKUP_DATA:BACKUP.LDB
      

This command copies all licenses whose product names begin with the string "FOR" from the default License Database to the BACKUP_DATA:BACKUP.LDB License Database. In this case, using the wildcard character (*) implies the use of /ALL.

$ LICENSE COPY * BACKUP_DATA:BACKUP.LDB
      

This command copies all licenses from the default License Database to the BACKUP_DATA:BACKUP.LDB License Database. In this case, using the wildcard character (*) implies the use of /ALL.

$ LICENSE COPY */PRODUCER=DEC BACKUP_DATA:BACKUP.LDB
      

This command copies all licenses with the producer name DEC from the default License Database to the BACKUP_DATA:BACKUP.LDB License Database. In this case, using the wildcard character (*) implies the use of /ALL.

$ LICENSE COPY D%%  BACKUP_DATA:BACKUP.LDB
      

This command copies all licenses beginning with a "D" followed by any two characters from the default License Database to the BACKUP_DATA:BACKUP.LDB License Database. In this case, using the wildcard character (%) implies the use of /ALL.

Creates a License Database with no license records. Because LMF provides a default License Database in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB when OpenVMS is installed, you do not typically need to use this command.

To use LMF, you must have a License Database file and the License Unit Requirement Table (LURT) file (SYS$COMMON:[SYSEXE]LMF$LURT.DAT), which comes installed with OpenVMS.

Format

LICENSE CREATE

Parameters

None.

Qualifier

/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.

Example

$ LICENSE CREATE/DATABASE=SYS$MANAGER:LMF$LICENSE.LDB
 
      

This command creates the License Database named LMF$LICENSE.LDB in the directory SYS$MANAGER.

Deletes one or more licenses and all history information for those licenses from the License Database. Deleted licenses are no longer available to the system for any use.

Format

LICENSE DELETE product-name[,...]

Parameter

product-name[,...]

Name or names of products with a license to be removed from the License Database. You can delete only licenses that have been registered.

Qualifiers

/ALL

Positional qualifier.

Specifies that all licenses with the given product name should be deleted. 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 delete. 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 deleted. 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 DELETE displays the name of each license that it deletes.

/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.

/STATUS=[(keyword)[,...]]

Positional qualifier.

Selects licenses to be deleted according to the product-name parameter specified and one or more license status keywords from the following list:

• ALL (default)---Deletes all specified licenses in the database.
• ACTIVE---Deletes all specified enabled licenses in the database. ACTIVE status means that the registered license is enabled for loading. For backward compatibility, the LICENSE LIST command identifies enabled licenses as having a status of active.
• DISABLED---Deletes all specified disabled licenses in the database.
• EXTINCT---Purges specified license information by deleting all extinct license records in the database. Extinct records are history records retained after a license is modified.
• CANCELED---Deletes all specified canceled licenses in the database. Note that current versions of LMF do not set license status to canceled. Old licenses may have this status.

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.

Description

Use LICENSE DELETE to delete licenses from the License Database. To tailor your command, use options to the /STATUS qualifier and wildcard characters in product name strings.

File space is not released following LICENSE DELETE commands. For information on retrieving Record Management Services (RMS) file space, see the OpenVMS Record Management Utilities Reference Manual.

Examples

$ LICENSE DELETE FORTRAN
      

This command deletes the Fortran license from the default License Database.

$ LICENSE DELETE FORTRAN, COBOL, PASCAL
      

This command deletes the Fortran, COBOL and Pascal licenses from the default License Database.

$ LICENSE DELETE FORTRAN/DATABASE=MY$DISK:MYDATA.LDB
      

This command deletes the Fortran license from the MY$DISK:MYDATA.LDB License Database.

$ LICENSE DELETE FORTRAN/ISSUER=XYLASOFT
      

This command deletes all licenses for the product named Fortran issued by XYLASOFT from the default License Database. If there are licenses for products named Fortran issued by companies other than XYLASOFT, they are not deleted.

$ LICENSE DELETE */STATUS=(EXTINCT)
      

This command deletes all license records with a status of EXTINCT from the database. This is effectively a purge of all historical information.

	privacy and legal statement
4584PRO_004.HTML