SHOW, LICENSE, Examples
*Conan The Librarian (sorry for the slow response - running on an old VAX)
|
/sys$common/syshlp/helplib.hlb SHOW, LICENSE, Examples *Conan The Librarian (sorry for the slow response - running on an old VAX) |
|
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
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)
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
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
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)
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
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.
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
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: ***
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
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.
|
|
