| Previous | Contents | Index |
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.
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.
| #1 |
|---|
$ SHOW LICENSE/FULL
Active licenses on node WTPOOH:
DVNETEND
Producer: DEC
Units: 0
Version: 0.0
Release Date: (none)
Termination Date: 31-DEC-2012
Availability: 0
Activity: 100
MOD_UNITS
Product Token:
OPENVMS-ALPHA
Producer: DEC
Units: 0
Version: 0.0
Release Date: (none)
Termination Date: 31-DEC-2012
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.
| #2 |
|---|
$ SHOW LICENSE/FULL
Active licenses on node MACCHU:
C
Producer: HP
Units: 3
Version: 0.0
Release Date: (none)
Termination Date: 31-DEC-2012
Availability: 0
Activity: 1
MOD_UNITS
IA64_ALPHA
Product Token:
DVNETEXT
Producer: HP
Units: 4
Version: 0.0
Release Date: (none)
Termination Date: 31-DEC-2012
Per Core License
Activity: 0
IA64
Product Token:
OPENVMS-I64-BOE
Producer: HP
Units: 4
Version: 0.0
Release Date: (none)
Termination Date: 31-DEC-2012
Per Core License
Activity: 0
IA64
Product Token:
|
The SHOW LICENSE command in this example displays all the active licenses on the current Integrity server node, MACCHU.
| #3 |
|---|
$ SHOW LICENSE/BRIEF
Active 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.
| #4 |
|---|
$ 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.
| #5 |
|---|
$ 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).
| #6 |
|---|
$ 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.
| #7 |
|---|
$ SHOW LICENSE/UNIT_REQUIREMENTS
VMS/LMF Charge Information for node PICCHU
This 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.
| #8 |
|---|
$ SHOW LICENSE/CHARGE_TABLE
OpenVMS 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)
Type: PCL, Units Required: 2 (I64 Per Core)
|
This example displays the CHARGE_TABLE information for an Integrity server node MACCHU with two active processor cores.
| #9 |
|---|
$ SHOW LICENSE/CHAR/CLUSTER
VMS/LMF Cluster License Unit Requirements Information 14-MAR-2010 06:39:41.54
Node A B C D E F G H I PCL
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 Requirements
Type: 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)
Type: PCL, Units Required: 3 (I64 Per Core)
|
In this example, the display shows how many license units are required for each license type (A, B, etc. on Alpha and VAX and PCL on Integrity servers) 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.
| #10 |
|---|
$ SHOW LICENSE/OE
Current Operating Environment on node MACCHU at 8-MAR-2010 16:12:51.72
--------- Operating Environment ---------- ------ Units ------
Name Description Type Level Loaded Total
HAOE High Availability H 5 4 4
|
This example shows the currently operating environment (HAOE) on an Integrity server node MACCHU.
| #11 |
|---|
$ SHOW LICENSE/HIER/FULL
Operating Environment Hierarchy
-------------------------------
--------- Operating Environment ---------- ------ Units ------
Name Description Type Level Loaded Total
HAOE High Availability H 5 2 2
GWLM
MCOE Mission Critical H 4 - 2
RTR-SVR
VMSCLUSTER
VMSCLUSTER-CLIENT
EOE Enterprise H 3 - 2
AVAIL-MAN
RMSJNL
VOLSHAD
BOE Base H 2 - 2
DECRAM
OMS
FOE Foundation H 1 - 2
OPENVMS-I64
OPENVMS-USER
DVNETEND
DW-MOTIF
UCX
TDC
X500-ADMIN-FACILITY
X500-DIRECTORY-SERVER
CIFS
|
This example displays information about the available operating environments, the hierarchy among them, and the products contained in each OE on an Integrity servers system.
| #12 |
|---|
$ SHOW LICENSE/OE=BOE/FULL
--------- Operating Environment ---------- ------ Units ------
Name Description Type Level Loaded Total
BOE Base H 2 4 7
DECRAM
OMS
OPENVMS-I64
OPENVMS-USER
DVNETEND
DW-MOTIF
UCX
TDC
X500-ADMIN-FACILITY
X500-DIRECTORY-SERVER
CIFS
|
This example shows all the products included in the Base Operating Environment (BOE) on an Integrity server node.
| #13 |
|---|
$ SHOW LICENSE OPENVMS-I64-HAOE
Active licenses on node MACCHU:
------- Product ID -------- ---- Rating ----- -- Version --
Product Producer Units PCL Activ Version Release Termination
OPENVMS-I64-HAOE HP 4 1 0 0.0 (none) 10-MAR-2011
|
This example shows licensing information for the HA-OE environment currently active on an Integrity server node MACCHU.
| #14 |
|---|
$ 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.
| #15 |
|---|
$ 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.
| #16 |
|---|
$ 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_PERIf this product is used in a cluster environment, you may use the SYSMAN utility to unload and load the license.
| #17 |
|---|
$ 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_CAPThe 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.
| #18 |
|---|
$ 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.
| #19 |
|---|
$ SHOW LICENSE/USAGE
View of loaded licenses from node REDSOX 8-MAR-2010 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-BOE HP 2 2 0 Yes
OPENVMS-I64-HAOE 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 Integrity servers system. The last column in the display shows that are products are in compliance with their license unit requirements.
| #20 |
|---|
$ SHOW LICENSE/USAGE
View of loaded licenses from node HOVMS2 8-MAR-2010 08:38:17.13
------- Product ID -------- ---- Unit usage information --------
Product Producer Loaded Allocated Available Compliance
OPENVMS-I64-HAOE HP Virtual Machine guest, no usage information
|
Issuing the SHOW LICENSE/USAGE command from an OpenVMS guest cluster member displays the text "Virtual Machine guest, no usage information" for PCL licenses loaded on the system. There is essentially no usage charge against the license units for OpenVMS guest nodes since multiple guests can run on the same host using the same license units.
| Previous | Next | Contents | Index |