The /WARNING_INTERVAL qualifier in this example displays three licenses that will terminate in 8000 days.

#8

$ SHOW LICENSE/USAGE/FULL DECWRITE-USER View of loaded licenses from node SLTG24 29-DEC-2001 13:36:22.23 ACTIVITY license DECWRITE-USER usage information: Pid Process Name Units Username Node 416000E6 MACAHAY 100 MACAHAY SLTG24 416000E7 MACAHIGH 100 MACAHIGH SLTG24 416000E8 ALICE 100 ALICE SLTG24 416000E9 MORGEN 100 MORGEN SLTG24 416000F1 ANGEL 100 ANGEL SLTG24 416000F2 ANGEL_1 100 ANGEL SLTG24 Units loaded: 2000 Units allocated: 600 Units available: 1400

The SHOW LICENSE command in this example lists the current users of the activity license for the product DECwrite. For each instance of use of the product, the process identification (PID), process name, node, and user name are identified. The units column shows the number of units allocated for each particular invocation of the product. The last line displays the units loaded when the LICENSE LOAD command was given, the total number of units currently allocated, and the total of unused (available for others to use) units.

$ SHOW LICENSE/USAGE/FULL TEST_PER
View of loaded licenses from node: SLTG24  30-DEC-2001 15:45:59 
 
PERSONAL USE license DEC TEST_PER usage information: 
Units   Reserved for: 
  100   UNCLE 
  100   AUNT 
  100   NEPHEW                                                    
  100   NIECE 
Units loaded: 600    Units reserved: 400    Units available: 200
 
      

This example shows a personal use license. The DEC TEST_PER product has enough units for six reservations with 100 units for each reservation. The license database (LDB) only has a total of four names in the reserve list attached to this product. If the license administrator (usually the system manager) wants to take full advantage of this license and adds 2 more names to the reserve list, he should use the following commands to update the product information:

$ LICENSE MODIFY TEST_PER/RESERVE=(NAME, ANOTHER_NAME)/ADD $ LICENSE UNLOAD TEST_PER $ LICENSE LOAD TEST_PER

If this product is used in a cluster environment, you may use the SYSMAN utility to unload and load the license.

$ SHOW LICENSE/USAGE/FULL TEST_CAP
View of loaded licenses from node: SLTG24  30-DEC-2001 15:45:59 
 
Availability license DEC TEST_CAP usage information: 
Units   Node   
   10   SLTG24 
   10   SLTG43 
  600   TORN8O 
  600   LTNUP 
Units loaded: 620    Units allocated: 1220    Units available: ***
 
      

In this example, the number of units allocated appears to be greater than the total units loaded and the units available value is three asterisks (***).

When you see three asterisks (***) as the number of units available, it is generally not a cause for alarm. This situation might arise when the license database (LDB) has been updated on disk, but the new information has not been propagated to the license database in memory on all nodes in the cluster. This node, SLTG24, happens to be one of the nodes that has not received the latest LDB information.

To update the information in the license database in memory for the TEST_CAP product, enter the following commands:

$ LICENSE UNLOAD TEST_CAP $ LICENSE LOAD TEST_CAP

The next time you issue the SHOW LICENSE/USAGE command the three asterisks (***) in display should disappear. If, however, you are using multiple LDB files in a cluster, you should read the section on the license database in the HP OpenVMS License Management Utility Manual.

$ SHOW LICENSE/UNIT_REQUIREMENT/CLUSTER
VMS/LMF Cluster License Unit Requirements Information 24-DEC-2001 
  14:05:51.65 
 
Node        A     B     C     D     E     F     G     H     I 
 
KARBO       -     -     -   100    50    10    -     -     10 
JENJON      -     -     -   100    50    10    -     -     10 
HELENA    143     -     -     -   600  2400    -     -   2400 
SHAKTI      -     -     -   100    50    10    -     -     10
 
Total Cluster Unit Requirements
Type: A, Units Required: 143     (VMS Capacity)
Type: B, * Not Permitted *       (VMS Server)
Type: C, * Not Permitted *       (VMS Concurrent User)
Type: D, Units Required: 300     (VMS Workstation)
Type: E, Units Required: 750     (System Integrated Products)
Type: F, Units Required: 2430    (Layered Products)
Type: G, * Not Permitted *       (VMS Reserved)
Type: H, * Not Permitted *       (Alpha Layered Products)
Type: I, Units Required: 2430    (Layered Products)
 
      

In this example, the display shows how many license units are required for each license type (A, B, etc.) on each node in the cluster. If a row of three asterisks (***) is displayed for a node, it means that the node is in the process of booting.

 $ SHOW LICENSE/USAGE/FULL TEST_CAP
 
 View of loaded licenses from node: SLTG24  30-DEC-2001 15:45:59 
 
 Availability license DEC TEST_CAP usage information: 
 Units   Node   
    10   SLTG24 
    10   SLTG43 
   600   TORN8O 
   600   LTNUP 
 Units loaded: 620    Units allocated: 1220    Units available: ***
 
      

In this example, the number of units allocated appears to be greater than the total units loaded and the units available value is three asterisks (***).

When you see three asterisks (***) as the number of units available, it is generally not a cause for alarm. This situation might arise when the license database (LDB) has been updated on disk, but the new information has not been propagated to the license database in memory on all nodes in the cluster. This node, SLTG24, happens to be one of the nodes that has not received the latest LDB information.

To update the information in the license database in memory for the TEST_CAP product, enter the following commands:

$ LICENSE UNLOAD TEST_CAP $ LICENSE LOAD TEST_CAP

The next time you issue the SHOW LICENSE/USAGE command the three asterisks (***) in display should disappear. If, however, you are using multiple LDB files in a cluster, you should read the section on the license database in the HP OpenVMS License Management Utility Manual.

 $ SHOW LICENSE/UNIT_REQUIREMENT/CLUSTER
 
 VMS/LMF Cluster License Unit Requirements Information 24-DEC-2001 
   14:05:51.65 
 
 Node        A     B     C     D     E     F     G     H     I 
 
 KARBO       -     -     -   100    50    10    -     -     10 
 JENJON      -     -     -   100    50    10    -     -     10 
 HELENE    143     -     -     -   600  2400    -     -   2400 
 SHAKTI      -     -     -   100    50    10    -     -     10
 
 Total Cluster Unit Requirements
 Type: A, Units Required: 143     (VMS Capacity)
 Type: B, * Not Permitted *       (VMS Server)
 Type: C, * Not Permitted *       (VMS Concurrent User)
 Type: D, Units Required: 300     (VMS Workstation)
 Type: E, Units Required: 750     (System Integrated Products)
 Type: F, Units Required: 2430    (Layered Products)
 Type: G, * Not Permitted *       (VMS Reserved)
 Type: H, * Not Permitted *       (Alpha Layered Products)
 Type: I, Units Required: 2430    (Layered Products)
 
      

In this example, the display shows how many license units are required for each license type (A, B, etc.) on each node in the cluster. If a row of three asterisks (***) is displayed for a node, it means that the node is in the process of booting.

 $ SHOW LICENSE/USAGE
 
 
View of loaded licenses from node REDSOX                26-MAY-2004 16:20:11.14 
 
------- Product ID --------   ---- Unit usage information ---------------- 
Product            Producer       Loaded  Allocated  Available  Compliance 
C                  HP                250          0        250  Yes 
DVNETEXT           HP                  4          3          1  Yes 
OPENVMS-I64-FOE    HP                  2          2          0  Yes 
OPENVMS-I64-MCOE   HP                 20          8         12  Yes 
VAXSET             HP                 10          8          2  Yes 
      

This example shows how many license units are loaded, how many are currently allocated, and how many are available on REDSOX, an I64 system. The last column in the display shows that are products are in compliance with their license unit requirements.

This appendix provides the following examples of license-related management tasks using the LICENSE commands:

• Registering a system integrated product ( Section B.1)
• Issuing LICENSE LIST and SHOW LICENSE commands ( Section B.2)
• Restricting product use ( Section B.3)

The following example provides a step-by-step procedure for registering a PAK for Volume Shadowing for OpenVMS, which is a System Integrated Product (SIP). This example uses command procedure VMSLICENSE.COM and the following PAK information:

ISSUER: DEC AUTHORIZATION NUMBER: ALS-WM-45789-6666 PRODUCT NAME: VOLSHAD PRODUCER: DEC NUMBER OF UNITS: 400 VERSION: 7.3 PRODUCT RELEASE DATE: KEY TERMINATION DATE: 31-DEC-2001 AVAILABILITY TABLE CODE: E ACTIVITY TABLE CODE: KEY OPTIONS: MOD_UNITS PRODUCT TOKEN: HARDWARE I.D.: CHECKSUM: 2-EBID-GOOD-NIGH-OJJG

Execute the VMSLICENSE.COM command procedure to register the Volume Shadowing PAK as follows:

1. Log in to the system manager's account, SYSTEM. Enter the command:

   $ @SYS$UPDATE:VMSLICENSE

   
   The procedure displays the following menu:

   VMS License Management Utility Options: 1. REGISTER a Product Authorization Key 2. AMEND an existing Product Authorization Key 3. CANCEL an existing Product Authorization Key 4. LIST the Product Authorization Keys 5. MODIFY an existing Product Authorization Key 6. DISABLE an existing Product Authorization Key 7. DELETE an existing Product Authorization Key 8. COPY an existing Product Authorization Key 9. MOVE an existing Product Authorization Key 10. ENABLE an existing Product Authorization Key 11. SHOW the licenses loaded on this node 12. SHOW the unit requirements for this node 99. EXIT this procedure Type '?' at any prompt for a description of the information requested. Press Ctrl/Z at any prompt to return to the main menu. Enter one of the above choices [1]

2. Enter 1. The procedure displays the following message:

   * Do you have your Product Authorization Key? [YES]:

3. Enter Y. The procedure displays the following information and prompts:

   Use the REGISTER option to add a new license to a license database. A Product Authorization Key (PAK) provides the product name and information you need to register the license. You must enter all the information provided by your PAK exactly as it appears. Type '?' at any prompt for a description of the information requested. Press CTRL/Z at any prompt to return to the main menu. Issuer [DEC]: Authorization Number []:

   
   If you do not have your PAK information at hand, you cannot continue at this point.

4. Press Return to specify DEC as the issuer.
5. Enter the authorization number from the PAK, ALS-WM-45789-6666. The procedure prompts for the following information:

   Product Name []:

6. Enter the product name string, VOLSHAD from the PAK. The procedure prompts for the producer:

   Producer [DEC]:

7. Press Return to specify DEC as the producer. The procedure prompts for the number of units:

   Number of Units []:

8. Enter the number of units, 400. The procedure prompts for the version:

   Version []:

9. Enter the version number from the PAK, 7.3. The procedure prompts for the key termination date:

   Key Termination Date []:

10. Enter the key termination date, 31-DEC-2001. The procedure prompts for the following information:

    Availability Table Code []: Activity Table Code []:

11. Enter the availability table code, E. Press Return after the Activity Table Code prompt. The procedure prompts for the following information:

    Key Options []: Product Token []: Hardware-Id []:

12. Enter the option MOD_UNITS after the Key Options prompt. Press Return after the Product Token prompt and the Hardware-ID prompt. The procedure prompts for the checksum:

    Checksum []:

13. Enter the checksum, 1-EBID-GOOD-NIGH-OJJG.

    Note The checksum string always begins with a number. The other 16 characters are always alphabetic characters from A through P.

    
    The procedure displays the information you entered. For example:

    Here is a list of the license information just entered: Issuer: DEC Authorization: ALS-WM-45789-6666 Producer: DEC Product Name: VOLSHAD Units: 400 Release Date: Version: 7.3 Termination Date: 31-DEC-2001 Availability: E Activity: Options: MOD_UNITS Token: Hardware ID: Checksum: 1-EBID-GOOD-NIGH-OJJG Is that correct? [YES]:

    
    

14. Compare the information on the screen with the information on the PAK. If the information is correct, enter Y. Otherwise enter N.

    Note If you enter any of the information incorrectly, you receive an error message, and the license is not registered. A checksum error can result when you enter incorrect information for other items on the PAK. If you get an error, carefully check all the data that you entered.

15. When the procedure displays the following question, enter Y.

    Do you wish to make corrections? [YES]:

16. To make corrections, the procedure steps you through all of the questions again with the data you just entered as defaults for each data field. If the data is correct, press Return. To replace incorrect data, enter the new data. To cancel data without entering new data, enter the backslash (\) character.
    If you entered all the information correctly, the procedure displays the following message:

    Registering VOLSHAD license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...

17. After the license is successfully registered, the procedure asks if you want to load the license on the current node, as follows:

    Do you want to LOAD this license on this system? [YES]:

    • If you registered the PAK on a standalone system and want to make the software available (active) immediately, enter Y.
    • If you registered the license in an OpenVMS Cluster environment but do not want to make it available (active) on the current node, enter N.
    
    In this example, assume the license is being registered in an OpenVMS Cluster environment and that you do not want it loaded on the current node. Enter N to complete this license registration. Note that you must load the Volume Shadowing license before you can use the product. See Step 18.
    The procedure returns you to the first menu and prompt as follows:

    VMS License Management Utility Options: 1. REGISTER a Product Authorization Key 2. AMEND an existing Product Authorization Key 3. CANCEL an existing Product Authorization Key 4. LIST the Product Authorization Keys 5. MODIFY an existing Product Authorization Key 6. DISABLE an existing Product Authorization Key 7. DELETE an existing Product Authorization Key 8. COPY an existing Product Authorization Key 9. MOVE an existing Product Authorization Key 10. ENABLE an existing Product Authorization Key 11. SHOW the licenses loaded on this node 12. SHOW the unit requirements for this node 99. EXIT this procedure Type '?' at any prompt for a description of the information requested. Press Ctrl/Z at any prompt to return to the main menu. Enter one of the above choices [1]

18. To register another PAK, enter 1. Then respond to the questions, again entering information from a license PAK. For this example assume you are finished. Enter 99 to exit the procedure. You have registered the license for Volume Shadowing.
19. Load the license on the desired node by logging in to that node and entering the LICENSE LOAD VOLSHAD command at the DCL prompt ($).

This example shows the differences between the LICENSE LIST command, which displays license information stored on disk, and the SHOW LICENSE command, which displays license information stored in memory. The first command registers a Fortran license, as follows:

$ LICENSE REGISTER FORTRAN /ISSUER=DEC /AUTHORIZATION=USA-10 - _$ /PRODUCER=DEC /UNITS=400 /VERSION=6.0 - _$ /AVAILABILITY=F /CHECKSUM=1-HIDN-INDA-COMP-DAHH

This command adds the license for the product Compaq Fortran to the default License Database. To see the information registered in the database, enter a LICENSE LIST command, as follows:

$ LICENSE LIST /FULL FORTRAN Use Ctrl/Z to exit, PF3-PF4 for Previous-Next Screen and Arrow keys to Scroll. License Management Facility V1.2 License Database File: SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB Created on: 17-AUG-2000 Created by user: GRAHAM Created by LMF Version: V1.2 ----------------------------------------------------- Issuer: DEC Authorization: USA-10 Product Name: FORTRAN Producer: DEC Units: 400 Version: 6.0 Release Date: (none) PAK Termination Date: (none) Availability: F (Layered Products) Activity: 0 Options: Hardware ID: Revision Level: 1 Status: Active Command: REGISTER Modified by user: LESH Modified on: 21-AUG-2000 14:32:23.41

Notice that for status the LICENSE LIST command displays Active. This means the registered license is enabled for loading, that it has not been disabled or canceled. It does not necessarily mean the Fortran license was loaded with a LICENSE LOAD command. Because the LICENSE LIST command sees only the License Database on disk, you must enter a SHOW LICENSE command to refer to the License Database in memory to determine whether a license is active on the current system. For example:

$ SHOW LICENSE/FULL Active licenses on node BIODTL: CRYPTICALMENT Producer: DEC Units: 400 Version: 7.3 Release Date: (none) Termination Date: 31-DEC-2001 Availability: E (System Integrated Products) Activity: 0 MOD_UNITS VAX-VMS Producer: DEC Units: 400 Version: 6.0 Release Date: (none) Termination Date: (none) Availability: A (VMS Capacity) Activity: 0 MOD_UNITS NO_SHARE

The SHOW LICENSE command in this example displays all the active licensed products on the current node named BIODTL; the Fortran license has not yet been loaded.

After you load the Fortran LICENSE, the SHOW LICENSE command displays the license. For example:

$ LICENSE LOAD FORTRAN LICENSE-I-LOADED, DEC FORTRAN was successfully loaded with 400 units $ SHOW LICENSE /FULL Active licenses on node BIODTL: CRYPTICALMENT Producer: DEC Units: 400 Version: 7.3 Release Date: (none) Termination Date: 31-DEC-2001 Availability: E (System Integrated Products) Activity: 0 MOD_UNITS FORTRAN Producer: DEC Units: 400 Version: 6.0 Release Date: (none) Termination Date: (none) Availability: F (Layered Products) Activity: 0 VAX-VMS Producer: DEC Units: 400 Version: 6.0 Release Date: (none) Termination Date: (none) Availability: A (VMS Capacity) Activity: 0 MOD_UNITS NO_SHARE