HP OpenVMS Systems Documentation

The OpenVMS Galaxy Software Architecture on OpenVMS (OpenVMS Galaxy) is a system integrated product (SIP). That is, OpenVMS Galaxy code is integrated and delivered with the OpenVMS operating system.

The License Management Facility (LMF) Product Authorization Keys (PAKs) representing OpenVMS Galaxy licenses allow you to access and use OpenVMS Galaxy software.

6.1 OpenVMS Galaxy Licensing Requirements

The following list summarizes OpenVMS Galaxy licensing requirements:

• One OpenVMS Operating System License for a Galaxy system
• One SMP Extension License for each CPU after the first CPU
• One OpenVMS Galaxy License for each CPU in a Galaxy system
• No changes to how HP layered products are licensed:
  • One capacity license per system
  • One user license per use

The following sections describe these requirements in more detail.

6.1.1 OpenVMS Operating System License

When an AlphaServer system is configured as an OpenVMS Galaxy system, there are no changes in how a system is licensed for the OpenVMS operating system.

One OpenVMS Base License is required for the Galaxy system, plus one SMP Extension License for each CPU after the first CPU.

6.1.2 OpenVMS Galaxy License

To create and run multiple instances, one OpenVMS Galaxy License is required for each CPU in a Galaxy system.

License rights for running a single-instance Galaxy on any Alpha system are provided by the OpenVMS Base License.

6.1.3 OpenVMS Layered Products License

HP software layered products on OpenVMS Galaxy configurations continue to use standard license types: Traditional, Concurrent Use, and Personal Use.

• One Traditional Capacity License will continue to license the system, regardless of the number of instances. The license is based on the system class of the hardware system.
• Concurrent Use Licenses will continue to license one concurrent use of the product.
• Personal Use Licenses will continue to license one named user on the system.

Instances in an OpenVMS Galaxy computing environment can be clustered with other instances in a single system, with instances in other Galaxy systems, or with non-Galaxy systems. Each type of clustering has different licensing requirements, as described in the following sections.

6.2.1 Clustering in a Galaxy System

In an OpenVMS Galaxy computing environment, instances can be clustered with other instances within a Galaxy system. Clustered instances use the shared-memory cluster interconnect to communicate with each other.

The licensing and functionality for clustering within a Galaxy system is provided under the OpenVMS Galaxy License.

6.2.2 Clustering Outside a Galaxy System

Instances in an OpenVMS Galaxy computing environment can be clustered with instances in another OpenVMS Galaxy system or with cluster nodes in non-Galaxy systems. Instances clustered outside of a Galaxy system use traditional cluster interconnects.

Each system that is clustered with another system must be licensed for OpenVMS Cluster Software. Clustering outside the OpenVMS Galaxy system is not covered by the OpenVMS Galaxy License.

6.3 License Databases

When an OpenVMS Galaxy system is configured with more than one instance, a license database must be set up for each independent instance or cluster of instances. The PAKs representing the licenses on the OpenVMS Galaxy configuration can be loaded on multiple license databases, as follows:

• OpenVMS Base, SMP Extensions, and OpenVMS Galaxy Licenses
  For full use of the OpenVMS Galaxy functionality, the PAKs representing your OpenVMS Base, SMP Extensions, and OpenVMS Galaxy Licenses must be loaded on each license database within the OpenVMS Galaxy on a single system.
• HP Layered Product Traditional Capacity Licenses
  The PAKs representing these licenses can be loaded on each license database within the OpenVMS Galaxy on a single system.
• HP Concurrent Use Licenses
  The PAKs representing these licenses can be loaded on the license database where the license will be used.
  For PAKs representing multiple concurrent uses (for example, a 50-use license) the PAK can be loaded on multiple license databases within the OpenVMS Galaxy on a single system. However, the PAK must be modified down on each license database so that the total number of license units does not exceed the total license units on the License PAK.
• HP Personal Use Licenses
  The PAKs representing these licenses can be loaded on each license database within the OpenVMS Galaxy on a single system; however, the number of actual uses must not exceed the licensed number of personal uses.

OpenVMS Galaxy PAK names are as follows:

• OpenVMS Operating System Base PAK: OPENVMS-ALPHA (base license)
• OpenVMS Operating System User PAK: OPENVMS-ALPHA-USER
• OpenVMS Galaxy PAK: OPENVMS-GALAXY

OpenVMS Galaxy customers must have at least one OPENVMS-ALPHA PAK, plus one additional OPENVMS-ALPHA PAK for each additional processor (CPU) after the first CPU (which is included in the Base Operating System License).

The OPENVMS-ALPHA and OPENVMS-ALPHA-USER PAKs can now be shared by multiple Galaxy instances. To implement this in the License Management Facility (LMF), include all OpenVMS Galaxy instance names in the PAK INCLUDE list.

For example, suppose that a customer has a system named ANDA1A in an OpenVMS Cluster. The OPENVMS-ALPHA license PAK currently has an INCLUDE list on it that has SCS node name ANDA1A in it. If that system is changed to an OpenVMS Galaxy running three instances named ANDA1A, ANDA2A, and ANDA3A, the OPENVMS-ALPHA license PAK must be modified so that all instances can share the NO_SHARE OPENVMS-ALPHA license.

The command to modify the OPENVMS-ALPHA license PAK is:

$ LICENSE MODIFY OPENVMS-ALPHA/AUTHORIZATION=xxxxx - 
_$ /INCLUDE=(ANDA1A,ANDA2A,ANDA3A) 

Because this example assumes that ANDA1A was already in a cluster, the authorization number is required to identify the one PAK of many OPENVMS-ALPHA license PAKs in the License Database (.LDB) file.

This appendix describes the syntax of the following License Management utility (LICENSE) and SHOW LICENSE commands:

• LICENSE COPY
• LICENSE CREATE
• LICENSE DELETE
• LICENSE DISABLE
• LICENSE ENABLE
• LICENSE ISSUE
• LICENSE LIST
• LICENSE LOAD
• LICENSE MODIFY
• LICENSE MOVE
• LICENSE REGISTER
• LICENSE START
• LICENSE UNLOAD
• SHOW LICENSE

LICENSE COPY

Copies licenses from one License Database to another. When you use LICENSE COPY, LMF disables the source license and registers a copy in the destination License Database as if it were a new license. If the terms and conditions of your license contract allow it, you can re-enable the source database license by using LICENSE ENABLE.

LICENSE COPY cannot be used to create a copy of a license in the same database as the source of the copy.

Format

LICENSE COPY product-name[,...] output-database

Parameters

product-name[,...]

Name or names of products with a license to be copied to the output License Database.

output-database

File specification of the License Database to which the license or licenses should be copied. This database must have been created previously using LICENSE CREATE.

If you enter a partial file specification (for example, specifying only a directory), LMF$LICENSE is the default file name, and .LDB is the default file type. If you do not specify a device or directory, the current default device and directory are used.

Qualifiers

/ALL

Positional qualifier.

Specifies that all licenses with the given product name should be copied. This qualifier affects only the product name that immediately precedes it in the command string.

/AUTHORIZATION=string

Positional qualifier.

Specifies a string that helps identify the license you want to copy. You must enter the authorization string exactly as it appears on your PAK. Use this optional qualifier only if you need it to identify the license. This qualifier affects only the product name that immediately precedes it in the command string.

/DATABASE=filespec

Specifies the location of the License Database from which the license should be copied. The default file specification is defined by the logical name LMF$LICENSE, which points to SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB on an unmodified OpenVMS system. Use this optional qualifier only if you do not use the default License Database name and location.

/ISSUER=string

Positional qualifier.

Specifies the name of the company (for example, HP) that issued the PAK for the product. Use this optional qualifier only if you need to identify the license. This qualifier affects only the product name that immediately precedes it in the command string.

/LOG

/NOLOG (default)

Controls whether LICENSE COPY displays the name of each license that it copies.

/PRODUCER=string

Positional qualifier.

Specifies the name of the company (for example, HP) that owns the product for which you have a license. Use this optional qualifier only if you need to identify the license. This qualifier affects only the product name that immediately precedes it in the command string.

Description

To copy a license from one database to another, use LICENSE COPY. The following conditions apply to a LICENSE COPY transaction:

• The status of the source database license changes to disabled.
• Network copies are supported within the limits of remote FAL access. If you use access control strings, such as "USERNAME password" within the file specification, the actual password string is not stored.
• LICENSE COPY does not transfer any user-supplied data such as reservation lists, modified termination dates, modified units, include or exclude node lists, or comments.

Examples

$ LICENSE COPY FORTRAN BACKUP_DATA:BACKUP.LDB
      

This command copies the Fortran license in the default License Database to the BACKUP_DATA:BACKUP.LDB License Database. This command fails if there is more than one Fortran license in the default database.

$ LICENSE COPY FORTRAN /DATABASE=BACKUP_DATA:BACKUP.LDB -
_$ BACKUP_DATA2:BACKUP2.LDB
      

This command copies the Fortran license in the source License Database to the BACKUP_DATA2:BACKUP2.LDB License Database. This command fails if there is more than one Fortran license in the source database.

$ LICENSE COPY FORTRAN /ALL BACKUP_DATA:BACKUP.LDB
      

This command copies all Fortran licenses in the default License Database to the BACKUP_DATA:BACKUP.LDB License Database.

$ LICENSE COPY FOR*  BACKUP_DATA:BACKUP.LDB
      

This command copies all licenses whose product names begin with the string "FOR" from the default License Database to the BACKUP_DATA:BACKUP.LDB License Database. In this case, using the wildcard character (*) implies the use of /ALL.

$ LICENSE COPY * BACKUP_DATA:BACKUP.LDB
      

This command copies all licenses from the default License Database to the BACKUP_DATA:BACKUP.LDB License Database. In this case, using the wildcard character (*) implies the use of /ALL.

$ LICENSE COPY * /PRODUCER=DEC BACKUP_DATA:BACKUP.LDB
      

This command copies all licenses with the producer name DEC from the default License Database to the BACKUP_DATA:BACKUP.LDB License Database. In this case, using the wildcard character (*) implies the use of /ALL.

$ LICENSE COPY D%%  BACKUP_DATA:BACKUP.LDB
      

This command copies all licenses beginning with a "D" followed by exactly two characters from the default License Database to the BACKUP_DATA:BACKUP.LDB License Database. In this case, using the wildcard character (%) implies the use of /ALL.

Creates a License Database with no license records. Because LMF provides a default License Database in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB when OpenVMS is installed, you do not typically need to use this command.

To use LMF, you must have a License Database file and the appropriate number of units for your system. On OpenVMS Alpha and VAX, the units are located in the License Unit Requirement Table (LURT) file (SYS$COMMON:[SYSEXE]LMF$LURT.DAT), which comes installed with OpenVMS. On OpenVMS Integrity servers, the units are based on the number of processor cores and the class of the machine specified in the PAK you receive with the license.

Format

LICENSE CREATE

Parameters

None.

Qualifier

/DATABASE=filespec

Specifies the location of the License Database. The default file specification is defined by the logical name LMF$LICENSE, which points to SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB on an unmodified OpenVMS system.

Example

$ LICENSE CREATE /DATABASE=SYS$MANAGER:LMF$LICENSE.LDB
 
      

This command creates the License Database named LMF$LICENSE.LDB in the directory SYS$MANAGER.

Deletes one or more licenses and all history information for those licenses from the License Database.

Format

LICENSE DELETE product-name[,...]

Parameter

product-name[,...]

Name or names of products with a license to be removed from the License Database. You can delete only licenses that have been registered.

Qualifiers

/ALL

Positional qualifier.

Specifies that all licenses with the given product name should be deleted. This qualifier affects only the product name that immediately precedes it in the command string.

/AUTHORIZATION=string

Positional qualifier.

Specifies a string that helps identify the license you want to delete. You must enter the authorization string exactly as it appears on your PAK. Use this optional qualifier only if you need it to identify the license. This qualifier affects only the product name that immediately precedes it in the command string.

/DATABASE=filespec

Specifies the location of the License Database from which the license or licenses should be deleted. The default file specification is defined by the logical name LMF$LICENSE, which points to SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB on an unmodified OpenVMS system. Use this optional qualifier only if you do not use the default License Database name and location.

/ISSUER=string

Positional qualifier.

Specifies the name of the company (for example, HP) that issued the PAK for the product. Use this optional qualifier only if you need it to identify the license. This qualifier affects only the product name that immediately precedes it in the command string.

/LOG

/NOLOG (default)

Controls whether LICENSE DELETE displays the name of each license that it deletes.

/PRODUCER=string

Positional qualifier.

Specifies the name of the company (for example, HP) that owns the product for which you have a license. Use this optional qualifier only if you need it to identify the license. This qualifier affects only the product name that immediately precedes it in the command string.

/STATUS=[(keyword)[,...]]

Positional qualifier.

Selects licenses to be deleted according to the product-name parameter specified and one or more license status keywords from the following list:

• ALL (default)---Deletes all specified licenses in the database.
• ACTIVE---Deletes all specified enabled licenses in the database. ACTIVE status means that the registered license is enabled for loading. For backward compatibility, the LICENSE LIST command identifies enabled licenses as having a status of active.
• DISABLED---Deletes all specified disabled licenses in the database.
• EXTINCT---Purges specified license information by deleting all extinct license records in the database. Extinct records are history records retained after a license is modified.
• CANCELED---Deletes all specified canceled licenses in the database. Note that current versions of LMF do not set license status to canceled. Old licenses may have this status.

If you enter more than one keyword, separate them with commas, and enclose the list in parentheses. You can abbreviate each option to the minimum number of characters needed to uniquely identify it.

Description

Use LICENSE DELETE to delete licenses from the License Database. To tailor your command, use options to the /STATUS qualifier and wildcard characters in product name strings.

File space is not released following LICENSE DELETE commands. For information on retrieving Record Management Services (RMS) file space, see the OpenVMS Record Management Utilities Reference Manual.

Examples

$ LICENSE DELETE FORTRAN
      

This command deletes the Fortran license from the default License Database.

$ LICENSE DELETE FORTRAN, COBOL, PASCAL
      

This command deletes the Fortran, COBOL and Pascal licenses from the default License Database.

$ LICENSE DELETE FORTRAN /DATABASE=MY$DISK:MYDATA.LDB
      

This command deletes the Fortran license from the MY$DISK:MYDATA.LDB License Database.

$ LICENSE DELETE FORTRAN /ISSUER=XYLASOFT
      

This command deletes all licenses for the product named Fortran issued by XYLASOFT from the default License Database. If there are licenses for products named Fortran issued by companies other than XYLASOFT, they are not deleted.

$ LICENSE DELETE * /STATUS=(EXTINCT)
      

This command deletes all license records with a status of EXTINCT from the database. This is effectively a purge of all historical information.

Disables a license currently registered in the License Database.

Format

LICENSE DISABLE product-name[,...]

Parameter

product-name[,...]

Name or names of products with a license that you want to disable. You can disable only licenses that currently exist in the License Database. Enter the product name exactly as it appears on your Product Authorization Key (PAK).

Qualifiers

/ALL

Positional qualifier.

Specifies that all licenses with the given product name should be disabled. This qualifier affects only the product name that immediately precedes it in the command string.

/AUTHORIZATION=string

Positional qualifier.

Specifies a string that helps identify the license you want to disable. You must enter the authorization string exactly as it appears on your PAK. Use this optional qualifier only if you need it to identify the license. This qualifier affects only the product name that immediately precedes it in the command string.

/DATABASE=filespec

Specifies the location of the License Database. The default file specification is defined by the logical name LMF$LICENSE, which points to SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB on an unmodified OpenVMS system. Use this optional qualifier only if you do not use the default License Database name and location.

/ISSUER=string

Positional qualifier.

Specifies the name of the company (for example, HP) that issued the PAK for the product. Use this optional qualifier only if you need it to identify the license. This qualifier affects only the product name that immediately precedes it in the command string.

/LOG

/NOLOG (default)

Controls whether LICENSE DISABLE displays the name of each license that it disables.

/PRODUCER=string

Positional qualifier.

Specifies the name of the company (for example, DEC) that owns the product for which you have a license. Use this optional qualifier only if you need it to identify the license. This qualifier affects only the product name that immediately precedes it in the command string.

Description

LICENSE DISABLE does not immediately affect loaded licenses. To affect a loaded license, you must first enter a LICENSE UNLOAD command, which unloads the license, but allows current processes to finish using the product. Note that to immediately disable all loaded licenses, you must shut down the system.

You cannot use LICENSE LOAD to activate a disabled license; you must first use LICENSE ENABLE.

LMF does not display error messages when either you or the system attempts to unload a disabled license.

Example

$ LICENSE DISABLE ABCD /PRODUCER=DEC
      

This command disables the license for ABCD software produced by HP. Because no database is specified, LMF uses the default database.