OpenVMS License Management Utility Manual

Document revision date: 30 March 2001

OpenVMS License Management Utility Manual

Contents

Index

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.

/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

Displays information in the License Unit Requirement Table (LURT). 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.

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 OpenVMS License Management Utility Manual for more information on license types.

/WARNING_INTERVAL=n

NOWARNING_INTERVAL

Displays a warning stating the number of licenses that will terminate in n days. The default is 30 days.

/WRAP

/NOWRAP (default)

Use with the /PAGE=SAVE qualifier to limit the number of columns to the width of the screen and to wrap lines that extend beyond the width of the screen to the next line.

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.

Description

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.

Examples

#1
$ SHOW LICENSE/FULL Active licenses on node WTPOOH: DVNETEND Producer: DEC Units: 0 Version: 0.0 Date: (none) Termination Date: (none) Availability: E (System Integrated Products) Activity: 0 MOD_UNITS VAX-VMS Producer: DEC Units: 0 Version: 0.0 Date: (none) Termination Date: (none) Availability: A (VMS Capacity) Activity: 0 MOD_UNITS NO_SHARE

$ SHOW LICENSE/FULL
Active licenses on node WTPOOH: 
         
DVNETEND 
       Producer: DEC 
       Units: 0 
       Version:  0.0 
       Date:  (none) 
       Termination Date: (none) 
       Availability: E (System Integrated Products) 
       Activity:  0 
       MOD_UNITS 
       
VAX-VMS 
       Producer: DEC 
       Units: 0 
       Version:  0.0 
       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 licenses on the current node, WTPOOH.

#2
$ SHOW LICENSE/BRIEF Active licenses on node WTPOOH: --- Product ID ---- ---- Rating ----- -- Version -- Product Producer Units Avail Activ Version Release Termination DVNETEND DEC 0 E 0 0.0 (none) (none) VAX-VMS DEC 0 A 0 0.0 (none) (none)

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

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

#3
$ SHOW LICENSE/OUTPUT=SYS$LOGIN:ACTIVE_LICENSES_OCT30.DAT

The SHOW LICENSE command in this example writes all the active licenses to the file named SYS$LOGIN:ACTIVE_LICENSES_OCT30.DAT.

#4
$ SHOW LICENSE/FULL PERSONAL Active licenses on node PICCHU: PERSONAL Producer: DEC Units: 100 Version: 0.0 Release Date: (none) Termination Date: (none) Availability: 0 Activity: 100 RESERVE_UNITS Reserve: RANCE

$ SHOW LICENSE/FULL PERSONAL
Active licenses on node PICCHU: 
 
PERSONAL 
       Producer: DEC 
       Units: 100 
       Version: 0.0 
       Release Date: (none) 
       Termination Date: (none) 
       Availability: 0  
       Activity: 100 
       RESERVE_UNITS 
       Reserve: RANCE

The SHOW LICENSE command in this example displays information about the product PERSONAL, as well as the name RANCE attached to the product license (known as the RESERVE list).

#5
$ SHOW LICENSE/TERM=10-JAN-2014 test0% Active licenses on node PICCHU: --- Product ID ---- ---- Rating ----- -- Version -- Product Producer Units Avail Activ Version Release Termination TEST01 DEC 0 A 0 0.0 (none) (none) TEST02 DEC 0 B 0 0.0 10-JAN-2014 12-NOV-2014 TEST03 DEC 0 C 0 0.0 30-DEC-2014 (none) TEST04 DEC 0 D 0 0.0 (none) 25-AUG-2015 TEST05 DEC 0 E 0 0.0 14-NOV-2016 14-AUG-2016 $ SHOW LICENSE/RELEASE=10-JAN-2014/SINCE test0% Active licenses on node PICCHU: --- Product ID ---- ---- Rating ----- -- Version -- Product Producer Units Avail Activ Version Release Termination TEST02 DEC 0 B 0 0.0 10-JAN-2014 12-NOV-2014 TEST03 DEC 0 C 0 0.0 30-DEC-2014 (none) TEST05 DEC 0 E 0 0.0 14-NOV-2016 14-AUG-2016 $ SHOW LICENSE/RELEASE=10-JAN-2014/BEFORE test0% Active licenses on node PICCHU: --- Product ID ---- ---- Rating ----- -- Version -- Product Producer Units Avail Activ Version Release Termination TEST01 DEC 0 A 0 0.0 (none) (none) TEST04 DEC 0 D 0 0.0 (none) 25-AUG-2015

$ SHOW LICENSE/TERM=10-JAN-2014 test0%
Active licenses on node PICCHU: 
 
--- Product ID ----  ---- Rating ----- -- Version -- 
Product    Producer  Units Avail Activ Version Release    Termination 
TEST01     DEC           0  A     0      0.0  (none)      (none)      
TEST02     DEC           0  B     0      0.0  10-JAN-2014 12-NOV-2014 
TEST03     DEC           0  C     0      0.0  30-DEC-2014 (none)      
TEST04     DEC           0  D     0      0.0  (none)      25-AUG-2015 
TEST05     DEC           0  E     0      0.0  14-NOV-2016 14-AUG-2016 
                    
 
$ SHOW LICENSE/RELEASE=10-JAN-2014/SINCE test0%
Active licenses on node PICCHU: 
 
--- Product ID ----  ---- Rating ----- -- Version -- 
Product    Producer  Units Avail Activ Version Release    Termination 
TEST02     DEC           0  B     0      0.0  10-JAN-2014 12-NOV-2014 
TEST03     DEC           0  C     0      0.0  30-DEC-2014 (none)      
TEST05     DEC           0  E     0      0.0  14-NOV-2016 14-AUG-2016 
       
 
$ SHOW LICENSE/RELEASE=10-JAN-2014/BEFORE test0%
Active licenses on node PICCHU: 
 
--- Product ID ----  ---- Rating ----- -- Version -- 
Product    Producer  Units Avail Activ Version Release    Termination 
TEST01     DEC           0  A     0      0.0  (none)      (none)      
TEST04     DEC           0  D     0      0.0  (none)      25-AUG-2015

In these examples, the SHOW LICENSE command uses the /TERM, /RELEASE, /SINCE and /BEFORE qualifiers.

#6
$ SHOW LICENSE/UNIT_REQUIREMENTS VMS/LMF Charge Information for node PICCHU This is a VAX 6000-420, hardware model type 160 Type: A, Units Required: 93 (VMS Capacity) Type: B, * Not Permitted * (VMS Server) Type: C, * Not Permitted * (VMS Concurrent User) Type: D, * Not Permitted * (VMS Workstation) Type: E, Units Required: 400 (System Integrated Products) Type: F, Units Required: 1200 (Layered Products) Type: G, * Not Permitted * (VMS Reserved) Type: H, * Not Permitted * (Alpha Layered Products) Type: I, Units Required: 1200 (Layered Products)

$ SHOW LICENSE/UNIT_REQUIREMENTS
VMS/LMF Charge Information for node PICCHU
This is a VAX 6000-420, hardware model type 160
 
Type: A, Units Required: 93      (VMS Capacity)
Type: B, * Not Permitted *       (VMS Server)
Type: C, * Not Permitted *       (VMS Concurrent User)
Type: D, * Not Permitted *       (VMS Workstation)
Type: E, Units Required: 400     (System Integrated Products)
Type: F, Units Required: 1200    (Layered Products)
Type: G, * Not Permitted *       (VMS Reserved)
Type: H, * Not Permitted *       (Alpha Layered Products)
Type: I, Units Required: 1200    (Layered Products)

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

#7
$ SHOW LICENSE/WARNING_INTERVAL=8000 test0% Active licenses on node PICCHU: --- Product ID ---- ---- Rating ----- -- Version -- Product Producer Units Avail Activ Version Release Termination TEST01 DEC 0 A 0 0.0 (none) (none) TEST02 DEC 0 B 0 0.0 10-JAN-2014 12-NOV-2014 TEST03 DEC 0 C 0 0.0 30-DEC-2014 (none) TEST04 DEC 0 D 0 0.0 (none) 25-AUG-2015 TEST05 DEC 0 E 0 0.0 14-NOV-2016 14-AUG-2016 %SHOW-I-TERMIMM, 3 licenses will terminate in 8000 days

$ SHOW LICENSE/WARNING_INTERVAL=8000 test0%
Active licenses on node PICCHU: 
 
--- Product ID ----  ---- Rating ----- -- Version -- 
Product    Producer  Units Avail Activ Version Release    Termination 
TEST01     DEC           0  A     0      0.0  (none)      (none)      
TEST02     DEC           0  B     0      0.0  10-JAN-2014 12-NOV-2014 
TEST03     DEC           0  C     0      0.0  30-DEC-2014 (none)      
TEST04     DEC           0  D     0      0.0  (none)      25-AUG-2015 
TEST05     DEC           0  E     0      0.0  14-NOV-2016 14-AUG-2016 
%SHOW-I-TERMIMM, 3 licenses will terminate in 8000 days

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

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

#9
$ 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

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

#10
$ 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: ***

#10

$ 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 OpenVMS License Management Utility Manual.

#11
$ 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)

#11

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

#12
$ 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: ***

#12

 $ 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 OpenVMS License Management Utility Manual.

#13
$ 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)

#13

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

Appendix B
Examples

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)

B.1 Registering a System Integrated Product

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 Shadowing PAK as follows:

$ @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]

Enter 1. The procedure displays the following message:

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

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.

Press Return to specify DEC as the issuer.
Enter the authorization number from the PAK, ALS-WM-45789-6666. The procedure prompts for the following information:
Product Name []:
Enter the product name string, VOLSHAD from the PAK. The procedure prompts for the producer:
Producer [DEC]:
Press Return to specify DEC as the producer. The procedure prompts for the number of units:
Number of Units []:
Enter the number of units, 400. The procedure prompts for the version:
Version []:
Enter the version number from the PAK, 7.3. The procedure prompts for the key termination date:
Key Termination Date []:
Enter the key termination date, 31-DEC-2001. The procedure prompts for the following information:
Availability Table Code []: Activity Table Code []:
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 []:
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 []:

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]:

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.

When the procedure displays the following question, enter Y.
Do you wish to make corrections? [YES]:
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...

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:

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.
Load the license on the desired node by logging in to that node and entering the LICENSE LOAD VOLSHAD command at the DCL prompt ($).