HP OpenVMS systems documentation

In an OpenVMS Cluster, if you own multiple license types for a single product, you are limited to viewing the usage information for the license type loaded on the node from which you are executing the SHOW LICENSE/USAGE command. To find out the usage of the other license type loaded on another node, issue the command on that node. You can also use the System Management (SYSMAN) utility to do this.

In an OpenVMS Cluster, usage information is limited to the local license type. For example, VAX and Alpha availability licenses are considered by LMF to be different license types. If you are running both VAX and Alpha systems in a cluster, usage information for availability licenses is limited to the local system type. For example, if you have DEC C installed on all nodes in your OpenVMS Cluster, you can display DEC C license allocation on all the VAX nodes in the cluster from any VAX node with DEC C installed, but you cannot display the DEC C license allocation on the Alpha nodes.

Usage information is not available for unlimited licenses (a license with 0 units). Clusterwide usage information is not available for personal use or NO_SHARE licenses. Refer to the HP OpenVMS License Management Utility Manual for more information on license types.

/WARNING_INTERVAL=n

NOWARNING_INTERVAL

/WRAP

/NOWRAP (default)

The /NOWRAP qualifier extends lines beyond the width of the screen and can be seen when you use the scrolling (left and right) features provided by the /PAGE=SAVE qualifier.

Examples

$ SHOW LICENSE/FULLActive licenses on node WTPOOH: DVNETEND         Producer: DEC         Units: 0         Version: 0.0         Release Date: (none)         Termination Date: 25-DEC-2004         Availability: 0         Activity: 100         MOD_UNITS         Product Token:  OPENVMS-ALPHA         Producer: DEC         Units: 0         Version: 0.0         Release Date: (none)         Termination Date: 22-OCT-2004         Availability: 0         Activity: 100         MOD_UNITS         Product Token:        

The SHOW LICENSE command in this example displays all the active licenses on the current Alpha node, WTPOOH.

$ SHOW LICENSE/FULL Active licenses on node MACCHU:  C         Producer: HP         Units: 3         Version: 0.0         Release Date: (none)         Termination Date: 25-DEC-2004         Availability: 0         Activity: 1         MOD_UNITS         IA64_ALPHA         Product Token:  DVNETEXT         Producer: HP         Units: 20         Version: 0.0         Release Date: (none)         Termination Date:  6-FEB-2005         Per Processor License         Activity: 0         IA64         Product Token:  OPENVMS-I64-FOE         Producer: HP         Units: 2         Version: 0.0         Release Date: (none)         Termination Date:  25-DEC-2004         Per Processor License         Activity: 0         IA64         Product Token:       

The SHOW LICENSE command in this example displays all the active licenses on the current I64 node, MACCHU.

$ SHOW LICENSE/BRIEFActive licenses on node WTPOOH:  --- Product ID ----   ---- Rating ----- -- Version -- Product    Producer   Units Avail Activ Version Release Termination DVNETEND   DEC            0  0     100    0.0  (none)   (none) VAX-VMS    DEC            0  0     100    0.0  (none)   (none)             

The SHOW LICENSE command in this example displays a summary of all the active licenses on the current VAX node, WTPOOH.

$ SHOW LICENSE/UNIT_REQUIREMENTSVMS/LMF Charge Information for node PICCHUThis is a AlphaServer 8400 5/440, hardware model type 1567 Type: A, Units Required: 2700   (VAX/VMS Capacity or OpenVMS Unlimited or Base)Type: B, * Not Permitted *      (VAX/VMS F&A Server)Type: C, * Not Permitted *      (VAX/VMS Concurrent User)Type: D, * Not Permitted *      (VAX/VMS Workstation)Type: E, * Not Permitted *      (VAX/VMS System Integrated Products)Type: F, * Not Permitted *      (VAX Layered Products)Type: G, * Not Permitted *      (Reserved)Type: H, Units Required: 1150   (Alpha Layered Products)Type: I, Units Required: 1150   (Layered Products)       

In this example, the /UNIT_REQUIREMENTS qualifier displays information in the License Unit Requirement Table (LURT) for the Alpha node PICCHU.

$ SHOW LICENSE/CHARGE_TABLEOpenVMS I64/LMF Charge Information for node MACCHU  This is an HP rx2600  (900MHz/1.5MB), with 2 CPUs active, 2 socket(s) Type: PPL,   Units Required: 2  (I64 Per Processor)       

In this example, the CHARGE_TABLE information for an I64 node MACCHU with 2 active CPUs is displayed.

$ SHOW LICENSE/CHAR/CLUSTER VMS/LMF Cluster License Unit Requirements Information    1-APR-2004 13:56:45.61  Node                A     B     C     D     E     F     G     H     I  PPL  FISH                 20     -     -     -     -     -     -  1050  1050    - SWORD                15     -     -     -     -     -     -  1050  1050    - SALMON               12     -     -     -     -     -     -  1050  1050    - MONGER               12     -     -     -     -     -     -  1050  1050    - GORDON               15     -     -     -     -     -     -  1050  1050    - ARTIST                -     -     -     -     -     -     -     -     -    2 PAINTS                -     -     -     -     -     -     -     -     -    1  Total Cluster Unit RequirementsType: A, Units Required: 74     (VAX/VMS Capacity or OpenVMS Unlimited or Base)Type: B, * Not Permitted *      (VAX/VMS F&A Server)Type: C, * Not Permitted *      (VAX/VMS Concurrent User)Type: D, * Not Permitted *      (VAX/VMS Workstation)Type: E, * Not Permitted *      (VAX/VMS System Integrated Products)Type: F, * Not Permitted *      (VAX Layered Products)Type: G, * Not Permitted *      (Reserved)Type: H, Units Required: 5250   (Alpha Layered Products)Type: I, Units Required: 5250   (Layered Products)Type: PPL, Units Required: 3  (I64 Per Processor)        

In this example, the display shows how many license units are required for each license type (A, B, etc. on Alpha and VAX and PPL on I64) 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/OE Current Operating Environment on node MACCHU at  1-APR-2004 14:00:09.70:  --------- Operating Environment ---------- ------ Units ------  Name     Description            Type Level   Loaded      Total   MCOE     Mission Critical         H    2          1          1            

This example shows the currently operating environment (MCOE) on an I64 node MACCHU.

$ SHOW LICENSE/HIER/FULL                     Operating Environment Hierarchy                      -------------------------------  --------- Operating Environment ---------- ------ Units ------  Name     Description            Type Level   Loaded      Total   MCOE     Mission Critical         H    2          2          2       RTR-SVR   VMSCLUSTER   VMSCLUSTER-CLIENT EOE      Enterprise               H    1          -          2      DECRAM   RMSJNL   AVAIL_MAN   VOLSHAD   SYSMGT FOE      Foundation               H    0          2          4      OPENVMS-I64   OPENVMS-USER   DVNETEND   DW-MOTIF       

This example displays information about the available operating environments, the hierarchy among them, and the products contained in each OE on an I64 system.

$ SHOW LICENSE/OE=FOE/FULL--------- Operating Environment ---------- ------ Units ------  Name     Description            Type Level   Loaded      Total   FOE      Foundation               H    0          2          3      OPENVMS-I64   OPENVMS-USER   DVNETEND   DW-MOTIF   UCX   TDC   DCOM-MIDL   X500-ADMIN-FACILITY        

This example shows all the products included in the Foundation Operating Environment (FOE) on an I64 node.

$ SHOW LICENSE OPENVMS-I64-MCOEActive licenses on node MACCHU:  ------- Product ID --------    ---- Rating ----- -- Version -- Product            Producer    Units PPL   Activ Version Release    Termination OPENVMS-I64-MCOE   HP             20  1     0      0.0  (none)       6-FEB-2005       

This example shows licensing information for the MCOE environment currently active on an I64 node MACCHU.

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, 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 ShadowingPAK 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 FORTRANUse 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 FORTRANLICENSE-I-LOADED, DEC FORTRAN was successfully loaded with 400 units $ SHOW LICENSE /FULLActive 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