|
||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||
|
 |
 |
HP OpenVMS systems documentation |
|
| Previous | Contents | Index |
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.
LICENSE MOVE product-name[,...] output-database
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.
/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.
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.
| #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.
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.
LICENSE REGISTER product-name
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.
/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 will be in the format of CPU_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.PPL Designates a Per Processer 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.
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.
| #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.
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 processor 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.
LICENSE START
None.
/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.
$ LICENSE START |
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 PPL licenses into memory.
Unloads a license, making the product unavailable from the current node. The product license or licenses must be registered in the License Database and must have been previously loaded with an interactive or automatic LICENSE LOAD command. Running processes are allowed to continue to completion.To use this command, you need CMKRNL, SYSNAM, and SYSPRV privileges.
LICENSE UNLOAD product-name[,...]
product-name[,...]
Name of the product to be unloaded. You can unload only licenses that have been loaded. Enter each product name exactly as it appears on its Product Authorization Key (PAK). You cannot use wildcard characters for product-name.
/LOG
/NOLOG (default)
Controls whether LICENSE UNLOAD lists the name of each unloaded license./PRODUCER=string
Positional qualifier.Specifies the name of the company (for example, DEC) that owns the product for which you have a license. The default string for this qualifier on Alpha and VAX is DEC. On I64, the default string is HP. If DEC or HP is not the producer of the product, you must use this qualifier to identify the product. This qualifier affects only the product name that immediately precedes it in the command string. Wildcard characters are not allowed.
LICENSE UNLOAD affects all units for a single product even if the loaded units are combined from multiple licenses. In such a case, you cannot unload the units from a single license. You must unload all the units.You are not required to unload a loaded license before modifying data in the License Database. To maximize product availability, modify licenses in the License Database first, and then load the changes by entering a LICENSE UNLOAD command followed by a LICENSE LOAD command.
| #1 |
|---|
$ LICENSE UNLOAD /PRODUCER=DEC FORTRAN |
This command unloads the HP Fortran license on the node from which it is entered.
| #2 |
|---|
$ LICENSE UNLOAD PASCAL,FORTRAN |
This command unloads the HP Pascal and HP Fortran licenses on the node from which it is entered.
Displays software product licenses active on the current node and lists the names attached to a license (known as the RESERVE list). The SHOW LICENSE command displays the license database information currently in your system's memory. Use the License Management utility command, LICENSE LIST, when you want to view the license database information that is on disk.
SHOW LICENSE [product-name [,...]]
product-name
Specifies the name or names of activated software product licenses to display. The asterisk (*) and the percent sign (%) wildcard characters are allowed. If you do not specify a product name, information is displayed about all active product name licenses. The product-name parameter is incompatible with the /UNIT_REQUIREMENTS qualifier.
The DCL command SHOW LICENSE displays software product licenses active on the current node. An active license is one that has been registered in the LICENSE database and has been loaded into system memory. To register and activate software product licenses, use the License Management utility (LICENSE) or VMSLICENSE.COM. Some licenses are registered automatically during product installation.To display licenses registered in the LICENSE database, use the LICENSE LIST command.
/BEFORE
Use with /TERMINATION_DATE and /RELEASE_DATE qualifiers. Selects only those licenses whose times are before the time specified with the other qualifiers.The /BEFORE qualifier cannot be used with the /SINCE qualifier.
/BRIEF (default)
Displays a summary of information about the specified active product licenses. Use the /FULL qualifier to obtain a complete product license listing./CHARGE_TABLE
Synonym for the /UNIT_REQUIREMENTS qualifier./CLUSTER
Use with the /UNIT_REQUIREMENTS qualifier to display the license unit requirements for every node in an OpenVMS Cluster./EXACT
Use with the /PAGE=SAVE and /SEARCH qualifiers to specify a search string that must match the search string exactly and must be enclosed with quotation marks (" ").If you specify the /EXACT qualifier without the /SEARCH qualifier, exact search mode is enabled when you set the search string with the Find (E1) key.
/FULL
Displays a summary of information about the specified active product licenses, including Product Authorization Key (PAK) options and the reserve list (if any). On I64 systems, lists the licenses for OEs currently active on the system./HIERARCHY - I64 only
Displays the hierarchy of licenses for operating environments active on the current node./HIGHLIGHT[=keyword]
Use with the /PAGE=SAVE and /SEARCH qualifiers to specify the type of highlighting you want when a search string is found. When a string is found, the entire line is highlighted. You can use the following keywords: BOLD, BLINK, REVERSE, and UNDERLINE. BOLD is the default highlighting./OE[=OE name] - I64 only
When an OE name is specified, displays the contents the of named operating environment. Currently, valid OE names are FOE, EOE, and MCOE. When no OE name is specified, displays the operating environment currently active on the node./OUTPUT[=filespec]
/NOOUTPUT
Controls where the output of the SHOW LICENSE command is sent. By default, the output of the SHOW LICENSE command is sent to the current SYS$OUTPUT device (usually your terminal). To send the output to a file, use the /OUTPUT qualifier followed by a file specification.The asterisk (*) and the percent sign (%) wildcard characters are not allowed in the file specification. If you enter a partial file specification (for example, specifying only a directory), SHOW is the default file name and .LIS is the default file type.
If you enter the /NOOUTPUT qualifier, output is suppressed.
/PAGE[=keyword]
/NOPAGE (default)
Controls the display of license information on the screen.You can use the following keywords with the /PAGE qualifier:
CLEAR_SCREEN Clears the screen before each page is displayed. SCROLL Displays information one line at a time. SAVE[= n] Enables screen navigation of information, where n is the number of pages to store. The /PAGE=SAVE qualifier allows you to navigate through screens of information. The /PAGE=SAVE qualifier stores up to 5 screens of up to 255 columns of information. When you use the /PAGE=SAVE qualifier, you can use the following keys to navigate through the information:
Key Sequence Description Up arrow key, Ctrl/B Scroll up one line. Down arrow key Scroll down one line. Left arrow key Scroll left one column. Right arrow key Scroll right one column. Find (E1) Specify a string to find when the information is displayed. Insert Here (E2) Scroll right one half screen. Remove (E3) Scroll left one half screen. Select (E4) Toggle 80/132 column mode. Prev Screen (E5) Get the previous page of information. Next Screen (E6), Return, Enter, Space Get the next page of information. F10, Ctrl/Z Exit. (Some utilities define these differently.) Help (F15) Display utility help text. Do (F16) Toggle the display to oldest/newest page. Ctrl/W Refresh the display. The /PAGE qualifier is not compatible with the /OUTPUT qualifier.
/PRODUCER=producer-name
Displays software product licenses active on the current node and supplied by the specified producer. The asterisk (*) and the percent sign (%) wildcard characters are allowed for the producer-name parameter. You cannot use the /PRODUCER qualifier with the /UNIT_REQUIREMENTS qualifier.
For HP Products Only
On OpenVMS VAX and Alpha systems, the producer is shown as DEC. On OpenVMS I64 systems, the producer is shown as HP./RELEASE_DATE=[date_time]
Allows listing licenses using release dates as selection criteria./SEARCH="string"
Use with the /PAGE=SAVE qualifier to specify a string that you want to find in the information being displayed. Quotation marks are required for the /SEARCH qualifier, if you include spaces in the text string.You can also dynamically change the search string by pressing the Find key (E1) while the information is being displayed. Quotation marks are not required for a dynamic search.
/SINCE(default)
Use with the /TERMINATION_DATE and /RELEASE_DATE qualifiers. Selects only those licenses whose times are on or after the time specified with the other qualifiers.The /SINCE qualifier cannot be used with the /BEFORE qualifier.
/TERMINATION_DATE=date_time
Allows listing licenses using termination dates as selection criteria./UNIT_REQUIREMENTS
On Alpha and VAX systems, displays information in the License Unit Requirement Table (LURT). On I64 systems, displays information about the type of system, the number of CPUs active, and the number of sockets. The /UNIT_REQUIREMENTS qualifier is incompatible with the product-name parameter and with the /BRIEF and /PRODUCER qualifiers./USAGE
Tells you how many license units are loaded, how many are currently allocated, and how many are currently available, as well as the license type for each product on the system. Use with the /FULL qualifier to display complete information---including the PID, process name, node, or user name---for each instance of use of the product. You need group privilege to see the list of users in your group who have allocated license units; you need world privilege to see the list of users in all groups.
Previous Next Contents Index