This manual, "OpenVMS License Management Utility Manual" (April 2001, for OpenVMS Alpha/VAX Version 7.3), serves as a guide for system managers to use the License Management Facility (LMF). LMF is the primary software license management tool for the OpenVMS operating system.
The document covers:
Overview of LMF and Licensing Concepts:
- Core Process: To use software, users must obtain a Product Authorization Key (PAK), register its information into the License Database, load the license into memory, and install the product.
- Key Components: Introduces the LICENSE utility (command-line interface), VMSLICENSE.COM (menu-driven procedure), the License Database (where license records are stored, including history), and License Unit Requirement Tables (LURTs) which define processor-specific unit requirements for licenses.
- License Types: Explains various license types, including Availability (system-wide), Activity (concurrent uses), Personal Use (named users), User (concurrent users), and Group licenses, detailing how units are allocated and shared.
- License Combination: Describes how multiple combinable licenses can pool their units to provide greater product availability.
Using LMF for License Management:
- Registration: Details how to register licenses using either the interactive
VMSLICENSE.COM procedure or direct LICENSE REGISTER commands, including handling PAK information and checksums.
- Loading: Explains how licenses are loaded from the database into memory, making products available, and how this happens automatically at system startup or manually with
LICENSE LOAD.
- Post-Registration Management: Covers advanced tasks such as:
- Restricting Use: Disabling (
LICENSE DISABLE), unloading (LICENSE UNLOAD), or permanently deleting (LICENSE DELETE) licenses.
- Controlling Access: Using
LICENSE MODIFY with /INCLUDE or /EXCLUDE qualifiers to manage node access in OpenVMS Clusters, or /RESERVE to control user access via reservation lists.
- Modifying Units: Adjusting license units with
LICENSE MODIFY /UNITS for licenses with the MOD_UNITS option.
- Transferring Licenses: Commands like
LICENSE COPY and LICENSE MOVE for transferring licenses between databases, and LICENSE ISSUE to create a PAK replica for registration elsewhere.
- Troubleshooting: Using
LICENSE LIST (disk database info) and SHOW LICENSE (in-memory info) to diagnose problems.
OpenVMS Galaxy Licensing:
- Outlines specific licensing requirements for OpenVMS Galaxy systems, including distinct licenses for the operating system, SMP extensions, and Galaxy instances per CPU, and how layered products are licensed within this environment.
The manual primarily targets system managers responsible for ensuring software products are correctly licensed and available on OpenVMS systems, including standalone and cluster environments.