HP OpenVMS Systems

HP Advanced Server for OpenVMS
Guide to Managing Advanced Server Licenses

The following examples provide step-by-step instructions for using Advanced Server licensing software and PAKs.

2.4.1 Setting Up Client-Based Licensing in a LAN

Configuration:

• The file server is running the Advanced Server in a LAN. The License Server is on the file server system.
• Clients have supported version of Microsoft Windows software already installed.

Components:

• Advanced Server for OpenVMS media and documentation kit.
• A PAK for 750 Advanced Server for OpenVMS Client Access (CA) licenses (PWLMXXXCA07.03).

Procedure:

The following example demonstrates how to set up a License Server to support client-based and server-based licensing in a WAN.

Configuration:

• The file server is running the Advanced Server for OpenVMS product, and the License Server is running on the file server system.
• Some clients are running Windows 2000 and Windows XP client software.
• Some clients are running PATHWORKS 32 client software.
• Some clients have client licensing software and will request client-based licenses.
• Some clients do not have client license software; they will require server-based licensing.

Components:

• Advanced Server for OpenVMS media kit and documentation.
• PATHWORKS 32 media kit and documentation.
• A PAK for 125 Advanced Server for OpenVMS Client Access (CA) licenses (PWLMXXXCA07.03).
• A PAK for PATHWORKS 32 client software (PWXXWINAT07.01), to grant the right to run the PATHWORKS 32 client software.

Procedure:

Clients requesting assignment of a client-based license will obtain client-based licenses and others will use server-based licenses.

2.4.3 Setting up a V6 Server to Allow Clients to Request PATHWORKS V5 for OpenVMS (LAN Manager) Licenses

The following example demonstrates how to configure the License Server so that clients can use PATHWORKS V5 for OpenVMS (LAN Manager) licenses.

Configuration:

• The file server is already running PATHWORKS V5 for OpenVMS (LAN Manager). The License Server is not running on the file server system.
• A License Server is running standalone using PATHWORKS V5 for OpenVMS (LAN Manager) software, which will be upgraded to use PATHWORKS V6.1 for OpenVMS (Advanced Server) software.
• Clients are using PATHWORKS V6.0 for DOS and Windows software. They have PATHWORKS V6.0 for DOS and Windows CCS licenses (PWLMDOSCC06.00).

Components:

• PATHWORKS V5 for OpenVMS (LAN Manager) media and documentation kit (already installed on both the file server system and the standalone License Server system).
• PATHWORKS V6.1 for OpenVMS (Advanced Server) media and documentation kit.
• PATHWORKS V6.0 for DOS and Windows media and documentation kit.
• A PAK for 500 PATHWORKS V6.0 for DOS and Windows (LAN Manager) CCS licenses (PWLMDOSCC06.00) already registered and loaded on the standalone License Server system.

Procedure:

The following example demonstrates how to set up server-based licensing in a LAN or WAN.

Configuration:

• The file server is running Advanced Server for OpenVMS.
• The License Server is not running on the same system that the file server is running on.
• Clients have Microsoft Redirector software already installed.
• All clients use Advanced Server for OpenVMS Client Access (CA) licenses (PWLMXXXCA07.03) as server-based licenses.

Components:

• Advanced Server for OpenVMS media and documentation kit.
• A PAK for 180 Advanced Server for OpenVMS Client Access (CA) licenses (PWLMXXXCA07.03).

Procedure:

If you are upgrading the file server from one version to the next, note the following:

1. Any client accessing a new version of the file server must be sufficiently licensed for access; unlicensed clients or clients without a sufficient level of licensing will not be allowed access.
2. A higher-level license is required to access the new file server than is required to access the previous version of the file server.

The license required depends on the version of the server that the clients need to access, as listed in Table 1-1, File Server Licenses.

When you plan the migration of the file server, assess the environment and decide the best procedure to ensure that clients who need to access the file server are sufficiently licensed. Upgrade procedures for client-based licenses are described in the following sections:

• Section 2.5.1, Configuring Client License Upgrades Individually
• Section 2.5.2, Replacing All Licenses
• Section 2.5.3, Upgrading Client Licenses Automatically

Individually configuring specific clients to request a new license requires modifying the client configuration for the licenses the client requests. This procedure works best when:

• There are very few clients that will access the new version of the file server.
• Migration of clients to using the new version of the file server will be slow and done over a long period of time.

The procedure for configuring clients individually is described in the README.TXT file provided with the Advanced Server PWLICENSE share on the file server.

2.5.2 Replacing All Licenses

This procedure works best if you choose to remove all the old licenses from the License Server system. If some old licenses are still needed on the License Server system, in addition to new Client Access licenses, set up automatic license upgrading, as described in Section 2.5.3, Upgrading Client Licenses Automatically.

If new licenses have been loaded onto the License Server system, the License Server, through normal license version look-up procedures, will not find an old license, but will find a new license and assign it to the client instead. For a discussion of how license lookup works, see Section 3.3, Controlling License Version Lookup.

If the old license PAKs are removed from the License Server system, all clients that had previously been assigned licenses by this server will automatically have their licenses revoked. The next time these clients attempt to verify their licenses, they will be informed that their previously assigned license is now invalid. The client license requester will automatically attempt to acquire a new license. (Some older client license requesters may need to be manually run again to request a new license.)

2.5.3 Upgrading Client Licenses Automatically

By default, the License Server will not perform license upgrades. You can configure a License Server to upgrade licenses automatically. For example, if configured appropriately, the License Server will automatically upgrade a PATHWORKS V5 for OpenVMS (LAN Manager) client license request or a PATHWORKS V6 Advanced Server license request to an Advanced Server for OpenVMS (PWLMXXXCA07.03) license. Follow this procedure to enable the License Server to upgrade licenses automatically:

1. Load new license PAKs on the License Server.
2. Edit the License Server start-up command file
   SYS$STARTUP:PWRK$LICENSE_S_START.COM to include the appropriate logical name definition, depending on which licenses will be available:

   License PAK	Logical Name Definition
   PWLMXXXCA06.00	$ DEFINE/SYSTEM PWRK$LS_V6_ACCESS_UPGRADE 1
   PWLMXXXCA07.03	$ DEFINE/SYSTEM PWRK$LS_V7_ACCESS_UPGRADE 1

   
   Be sure to define the logicals before the following RUN command:

   $ RUN SYS$SYSTEM:PWRK$LICENSE_SERVER

If a logical name is disabled (undefined or defined to be zero), the License Server will not automatically upgrade licenses to the appropriate new license. If the logical name is defined to the value 1 (or any numeric value other than zero), clients requesting assignment or verification of licenses will have their licenses upgraded automatically to new licenses, if sufficient new licenses exist.

The first time the License Server is started after an upgrade, the License Server state file will be modified to remove all old licenses from the Server-Based license group that do not provide access to the current file server. (The state file keeps track of licenses that are loaded, groups that are created, and licenses assigned to each group.) The Advanced Server License Server still assigns and verifies client-based licenses.

When an upgrade operation occurs, the License Server logs both the assignment of the new license and the name of the license returned to the client in the License Server log file
PWRK$LOGS:PWRK$LICENSE_SERVER_node-name.LOG. This license returned to the client is called a virtual license, as described in Section 2.5.4, Virtual Licenses.

Configuring the License Server to automatically upgrade old license requests affects all clients requesting or verifying a license. If the License Server is configured to automatically upgrade licenses, client-based licenses are upgraded to new licenses when either of the following occurs:

• A client requests assignment of an old license.
• A client requests verification of a previously assigned license.

The License Server automatically assigns the client a new license (even if it has requested assignment or verification of an old license), and returns an equivalent new license to the client.

2.5.4 Virtual Licenses

Before the introduction of Client Access (CA) licenses, the file server required older style licenses (such as FP or CC licenses). Requests for these older style licenses will be upgraded properly. However, the client will only accept licenses of the type requested with the requested version number or higher. To get the client to accept a Client Access license, the License Server returns a different name than that assigned.

If a client requests an earlier form of the PATHWORKS license (such as FP or CC licenses), the upgrade returns a "virtual license," that is, an equivalent Client Access license with a name that does not match the name of the license assigned to the client.

For example, if a client requests assignment of a PWLMXXXFP05.00 license from the License Server, the License Server upgrades the request to a Client Access license and assigns a new license (if one is available).

From the client's perspective, the license assigned is PWLMXXXFPmm.nn and the client will accept that. The symbols mm.nn represent any valid license version number. From the License Server's perspective (as displayed by the License Manager), the client was assigned a PWLMXXXCAmm.nn license. Table 2-1, Virtual License Names, lists the names of the licenses returned to clients due to upgrade operations.

When the license assigned is different from the license returned to the client, the License Server log file contains two messages:

• One message indicates the name of the license assigned to the client.
• The other message indicates the name of the license returned to the client.

When the License Server and License Registrar run, complete descriptions of the configuration parameters used by these processes are contained in the following command procedures:

• SYS$STARTUP:PWRK$LICENSE_S_START.COM
• SYS$STARTUP:PWRK$LICENSE_R_START.COM

For descriptions of the License Registrar configuration parameters and the logicals that determine their values, see Section A.3, License Registrar Events.

As part of their startup sequence and announcement, the License Server and License Registrar place tables of their configuration parameters in their respective log files related to license processing:

• PWRK$LOGS:PWRK$LICENSE_SERVER_servername.LOG, where servername is usually the OpenVMS Cluster alias or the node name of the system on which the License Server runs
• PWRK$LOGS:PWRK$LICENSE_REGISTRAR_nodename.LOG, where nodename is the node name of the system (the file server) on which the License Registrar runs

For each parameter in the table, the following information is recorded:

• Parameter name
• Parameter type
• Whether the parameter is dynamic
• The current value being used
• Whether that value is the default value for the parameter

Dynamic configuration parameters allow the value of a parameter to be changed using a system logical, without having to restart the Advanced Server for OpenVMS. The license component that uses the parameter obtains the changed value while the component is running.

When the value of a dynamic configuration parameter is changed by redefining the control logical associated with the configuration parameter, the change might not take effect immediately. The license components periodically check the values of their dynamic configuration parameters to see if the value of any parameter has changed. When the license component detects a change to the value of a dynamic configuration parameter, a message is recorded in the component's log file when the new value is put into use. By default, the components check for changes to dynamic parameter values every 10 minutes.