Document revision date: 30 March 2001

This section provides the basic information you need to configure licensing software on client computers that are not in the same LAN as the License Server and that must acquire client-based licenses.

When the License Server that is to provide client-based licenses is not in the same LAN as the client system, the following two steps are required to set up the client system:

1. Configure the WAN protocol stack (DECnet or TCP/IP) to map the License Server's NetBIOS name (usually the node or host name with the prefix "PWRK$L") to the WAN address of the License Server system, as explained in Section 5.3.1, Configuring the WAN Protocol Stack for WAN Licensing.
2. Configure the licensing software components with the name of the License Server, as explained in Section 5.3.2, Configuring the License Server Name.

For the CLR to communicate with a License Server, the client system must be able to resolve the NetBIOS name of the License Server. Client computers on the same LAN as the License Server can use broadcasts to locate the License Server. However, client computers outside the local area network where the License Server is running must use one of the following methods to resolve the NetBIOS name of the License Server:

• Using TCP/IP
  • WINS (Windows Internet Name Service)
    If the License Server is configured as a WINS client, the License Server name will be registered on the WINS server. Clients can then use WINS to resolve the License Server name. For more information about configuring the License Server as a WINS client, refer to the Server Administrator's Guide for your Advanced Server product. This configuration is supported in Microsoft TCP/IP network environments on Windows 95, Windows 98, Windows NT V4.0, and Windows 2000.
  • LMHOSTS file
    If the client is using Microsoft TCP/IP, an LMHOSTS file may be used to map TCP/IP addresses to NetBIOS names.
    Search for the file LMHOSTS. If it does not exist, search for the file LMHOSTS.SAM and make a copy in the same directory, naming the copy "LMHOSTS."
    Edit LMHOSTS using whatever text editor you like and add the following line:

    tcp-address PWRK$Lname #PRE

    
    For example, if the License Server system has a TCP/IP address of 12.34.56.78, and the License Server is running on node "ZIPHED", add the following line:

    12.34.56.78 PWRK$LZIPHED #PRE

• Using DECnet
  If the client computer is running DECnet, a Remote Adapter Name can be defined to translate the License Server name to a DECnet address.
  At the command prompt, issue the following command:

  NCP DEFINE REMOTE-ADAPTER-NAME PWRK$Lname NODE decnet-address

  
  For example, if the License Server system has a DECnet address of 12.345, and the License Server is running on node "ZIPHED", enter the following line:

  NCP DEFINE REMOTE-ADAPTER-NAME PWRK$LZIPHED NODE 12.345

Once the WAN protocol stack has been configured to map the NetBIOS name of the License Server to the WAN address of the License Server system, configure the licensing software on the client, specifying the NetBIOS name of the License Server. On Windows 95, Windows 98, Windows NT V4.0, or Windows 2000 clients, run the program PNLCFG.EXE and add the License Server to the list of "Remote License Servers" in the dialog box.

This appendix explains the event messages that are logged to the License Server and License Registrar log files as well as the Event Logger (ADMIN/ANALYZE). It provides the License Server and License Registrar messages, an explanation of these messages, and corrective action if appropriate. It includes the following topics:

• Section A.1, License Component Log Files, describes the types of log files.
• Section A.2, License Server Events, describes events logged to the OpenVMS License Server log file.
• Section A.3, License Registrar Events, describes events logged to the License Registrar log file.
• Section A.4, Event Logger (ADMIN/ANALYZE) Messages, describes how to check the events logged to the Event Logger (ADMIN/ANALYZE) during file server operations.

For information on client licensing messages, such as the system error message you receive when you attempt to access the file server without a license, or the messages you receive when you run the Client Transponder or Client Requester software, see the appropriate client online help utilities.

A.1 License Component Log Files

Log files are stored in a directory defined by the PWRK$LOGS logical name. The two types of log files are:

• License processing-related log files
• License component program log files

The names of the license processing-related log files are as follows:

• License Server log file:

  PWRK$LOGS:PWRK$LICENSE_SERVER_name1.LOG

  
  where name1 is either the OpenVMS Cluster alias name or the name of the node on which the License Server is running.
  In most cases, name1 is also used to form the License Server name on the local system:

  PWRK$Lname2

  
  where name2 is the same as name1.

• License Registrar log file:

  PWRK$LOGS:PWRK$LICENSE_REGISTRAR_name.LOG

  
  The name is the system name.

The names of the license component program log files are as follows:

• License Server process:

  PWRK$LOGS:PWRK$LICENSE_S_name1.LOG

  
  where name1 is either the OpenVMS Cluster alias name or the name of the node on which the License Server is running.
  In most cases, name1 is also used to form the License Server name on the local system:

  PWRK$Lname2

  
  where name2 is the same as name1.

• License Registrar process:

  PWRK$LOGS:PWRK$LICENSE_R_name.LOG

  
  The name is the system name.

This section describes events logged to the License Server log file (PWRKS$LOGS:PWRK$LICENSE_SERVER_name.LOG). Note that all the messages posted to the log file begin with a date/timestamp. Use the License Manager to control what events are logged. The types of events that the License Server posts to the License Server log file include:

• INIT_LOGFILE
• CLIENT_LICENSE_VALID
• CLIENT_LICENSE_INVALID
• CLIENT_ADDRESS_CHANGE
• SERVER_LICENSE_ASSIGNED
• SERVER_LICENSE_RELEASED
• MESSAGE
• FATAL_ERROR

ALERT_LEVEL_REACHED:
Product = product-name Group = group-name Alert Level = alert-level-number Allocation = number-of-licenses-allocated
Explanation: The number of licenses currently in use for this product exceeds the alert level. If the group-name is <none>, the alert level for all the product's licenses has been exceeded. Otherwise, the alert level for the licenses in the specific group has been exceeded.
User Action: Review the current license distribution. Remove licenses from clients that no longer use the product, redistribute the available product licenses, or add new product licenses.

CLIENT_ADDRESS_CHANGE:
Client Id = client-id-number Old Client Addr = old-address New Client Addr = new-address
Explanation: The current client's address is different from when the license was assigned. Typically, this message indicates a license has been moved from one client to another.
User Action: Make sure that the change of client ID is valid.

CLIENT_ID_CHANGE:
Client Id = client-id-number Old Client ID = old-id New Client ID = new-id Old Client Addr = old-address New Client Addr = new-address
Explanation: The current ID of the client is different from the ID it had when the license was assigned. The client ID is the address of the Ethernet adapter. Typically, this message indicates that a license has been reassigned from one client to another.
User Action: Make sure that the Ethernet address change is valid.

CLIENT_LICENSE_ASSIGNED:
Client ID = client-id-number Client Addr = client-address Transport = transport-name Product = product-name Group = group-name
Explanation: A product license was granted to the client from the group specified.
User Action: None required.

CLIENT_LICENSE_DENIED:
Client ID = client-id-number Client Addr = client-address Transport = transport-name Product = product-name Group = group-name Reason = explanation-string
Explanation: The client's request for assignment of a license could not be processed as requested.
User Action: If the reason is an incorrect product or group, check to be sure the license type exists and reconfigure the client to obtain a valid license. If there are not enough licenses, the administrator must add, reallocate, or revoke licenses to create available ones.

CLIENT_LICENSE_INVALID:
Client ID = client-id-number Client Addr = client-address Transport = transport-name Product = product-name Group = group-name Reason = explanation-string
Explanation: The license presented for verification to the License Server by the client is no longer valid.
User Action: If the reason is an incorrect product, group, or license, the data on the client may no longer be valid (for example, the group may have been deleted), or the license may have been revoked. Reboot the client to obtain a valid license. If the license is in use by another client, this may be a case of illegal copying of license data between clients and should be investigated.

CLIENT_LICENSE_RELEASED:
Client ID = client-id-number Client Addr = client-address Transport = transport-name Product = product-name Group = group-name
Explanation: The system manager released the product license from the specified group.
User Action: None required.

CLIENT_LICENSE_REVOKED:
Client ID = client-id-number Client Addr = client-address Product = product-name Group = group-name Reason = explanation-string
Explanation: The product license from the specified group was revoked or removed. The reason string indicates whether it was due to an action taken by the License Manager, or due to changes in the OpenVMS License Management Facility (LMF) database. This action can explain why a client's license is considered invalid in a later log event.
User Action: You may have to add, reallocate, or revoke currently allocated licenses to allow this client to use the file server in the future.

CLIENT_LICENSE_UPGRADE_ON_ASSIGN:
Client Id = client-id-number Client Addr = client-address Transport = transport-name Group = group-name Current Product = version-product-name, for example PWLMDOSCC06.00, PWLMXXCA06.00 Upgrade Product = product-name, for example, PWLMXXXCA06.00
Explanation: The client requested a PWLMDOSCC06.00 license and the License Server has defined the logical so the License Server upgraded and assigned the PWLMXXXCA06.00 license. The license returned to the client will be a virtual license. (See the description under Explanation for message, VIRTUAL_CLIENT_LICENSE_RETURNED_ON_ASSIGN.)
User Action: None required.

CLIENT_LICENSE_VALID:
Client ID = client-id-number Client Addr = client-address Transport = transport-name Product = product-name Group = group-name Reason = explanation-string
Explanation: The license presented for verification to the License Server by the client is valid.
User Action: None required.

FATAL_ERROR:
module-name: module-name and explanation-string
Explanation: An irrecoverable error has occurred that will cause the License Server to terminate. The message may return the name of the module in which the error occurred and an explanation of the possible cause.
User Action: Notify your Compaq service representative or local authorized reseller. Please save the log file so that it may be used to help diagnose the problem.

INIT_LOGFILE:
Reason = explanation-string
Explanation: A new version of the log file was created. The reason string indicates whether it was done because the server started, or because of a License Manager request.
User Action: None required.

MESSAGE: message-text
Explanation: The message displayed describes diagnostic log event information.
User Action: None required.

SERVER_STATE_CHANGE:
Old State = previous-state-name New State = new-state-name Reason = explanation-string
Explanation: The License Server has been either enabled to serve the client requests or disabled. The reason always indicates that it was at the request of the License Manager.
User Action: None required.

VIRTUAL_CLIENT_LICENSE_RETURNED_ON_ASSIGN:
Client ID = client-id-number Client Addr = client-address Group = group-name Product = product-name Virtual Product = virtual-product
Explanation: The license requested by the client was a LAN Manager license, for example, PWLMDOSCC06.00. The license software looks for a higher version of the product than requested either through license version lookup (described in Section 3.3, Controlling License Version Lookup) or license upgrade (described in Section 2.5, Upgrading Client Licenses). A license was assigned to that client, for example, PWLMXXXCA06.00. Because the client will only accept a license name in the format of the license requested, the License Server returns a "virtual license" to the client that conforms to the original format requested. So the virtual license returned is in the form, PWLMDOSCC07.00. The client will accept it as simply a higher version of the PWLMDOSCC06.00 that it requested.
User Action: None required.

A.3 License Registrar Events

This section describes the various events that can be logged to the License Registrar log file (PWRK$LOGS:PWRK$LICENSE_REGISTRAR_nodename.LOG) and the control logicals available to control the posting of events to the log file.

The types of events that the License Registrar posts to the License Registrar log file include:

• INIT_LOGFILE
• CLIENT_LICENSE_VALID
• CLIENT_LICENSE_INVALID
• CLIENT_ADDRESS_CHANGE
• SERVER_LICENSE_ASSIGNED
• SERVER_LICENSE_RELEASED
• CLIENT_NOT_LICENSED
• MESSAGE
• FATAL_ERROR

By default, the License Registrar logs only the most significant events to prevent the log file from growing too rapidly. If no control logicals are used to indicate that additional events should be logged, the default behavior is to post only the following types of events to the License Registrar log file:

• INIT_LOGFILE
• CLIENT_ADDRESS_CHANGE
• MESSAGE
• FATAL_ERROR

On occasion, it may be necessary to reconfigure the License Registrar to post more detail about requests being processed. Should this become necessary, use the following control logicals to control the type of events posted to the License Registrar log file. These logicals determine the License Registrar's configuration parameter values while it is running.

• PWRK$LrLogVerbose
  Turning this control logical on for the License Registrar causes messages for all event types to be posted to the License Registrar log file.
  If the PWRK$LrLogVerbose control logical is not turned on, the following logging control logicals may be used to enable specific types of additional logging.
• PWRK$LR_Log_ClientBased_Activity
  Turning this control logical on will enable the posting of messages related to the result of querying a client for a client-based license appropriate for accessing the file server (CLIENT_LICENSE_VALID and CLIENT_LICENSE_INVALID events).
• PWRK$LR_Log_ClientBased_Successes
  Turning this control logical on will enable the posting of messages when the License Registrar successfully validates a client-based license (CLIENT_LICENSE_VALID events).
• PWRK$LR_Log_ClientBased_Failures
  Turning this control logical on will enable the posting of messages when the License Registrar does not receive a client-based license appropriate for accessing the file server after querying a client running client licensing software (CLIENT_LICENSE_INVALID events). In this case, the client may not have returned any license or none of the licenses returned by the client are valid for accessing the file server.
• PWRK$LR_Log_ServerBased_Activity
  Turning this control logical on will enable the posting of
  messages related to the assignment and release of server-based licenses by the License Registrar (SERVER_LICENSE_ASSIGNED, SERVER_LICENSE_RELEASED and CLIENT_NOT_LICENSED events).
• PWRK$Lr_License_Report_Interval
  Setting this logical determines how often a license report is generated and posted in the License Registrar log file. Set the logical by specifying a numerical value, representing the intervals in seconds that reports are generated. Each report lists all the clients currently connected to the file server using server-based licenses. By default, no license report is generated. For more information about setting this logical, see Section A.3.1, Monitoring Consumption of Server-Based Licenses.

Each of these control logicals can be turned on by defining the logical to a value of one (1). They can be turned off by leaving them undefined or defining them to a value of zero (0). If the logical is defined, the logical name must be defined in such a way as to make the definition available to the License Registrar process (by defining a system logical or defining the control logical in the License Registrar startup command procedure SYS$STARTUP:PWRK$LICENSE_R_START.COM). For example, to always log events related to server-based licensing, turn on the PWRK$LR_Log_ServerBased_Activity by defining the following system logical:

$ DEFINE/SYSTEM PWRK$LR_Log_ServerBased_Activity 1

Note that these parameters affect reporting of individual events as they happen. For example, when a client takes or releases a license, an event message is logged reporting that activity. To generate reports that provide statistics such as the number of server-based licenses currently in use, see Section A.3.1, Monitoring Consumption of Server-Based Licenses.

CLIENT_ADDRESS_CHANGE:
Old Client Addr = old-address-name New Client Addr = new-address-name
Explanation: The current network address of the client is different from the one it had when the license was granted. This change may be valid, or it may indicate the illegal copying of license data from the old client to the new client.
User Action: Make sure that the change of address is valid.

CLIENT_LICENSE_INVALID:
Client ID = client-id-number Client Addr = client-address Product = product-name Group = group-name Reason = explanation-string
Explanation: The product license specified is no longer valid for the client.
User Action: If the reason is an incorrect product, group, or license, the data on the client may no longer be valid (for example, the group may have been deleted). Reconfigure the client to obtain a valid license. If the license is in use by another client, this may be a case of illegal copying of license data between clients and should be investigated.

CLIENT_LICENSE_VALID:
Client ID = client-id-number Client Addr = client-address Product = product-name Group = group-name Reason = explanation-string
Explanation: The product license from the group specified is still valid. The reason string indicates whether the client license was actually inspected or whether there was a cache entry match.
User Action: None required.

CLIENT_NOT_LICENSED:
Client ID = client-id-number Client Addr = client-address Transport = transport-name Reason = explanation-string
Explanation: The client is not licensed to access the file server. The client does not have a client-based license that grants it the right to access the services provided by the file server and there are no server-based licenses available for the License Registrar to assign to the client to give the client access rights to the file server.
User Action: Either configure the client to acquire a client-based license to access the file server or make server-based licenses available on the file server system, which can then be used to license the client.

FATAL_ERROR: module-name: module-name and explanation-string
Explanation: An irrecoverable error has occurred that will cause the License Registrar to terminate.
User Action: Notify your Compaq service representative or local authorized reseller.

INIT_LOGFILE:
Reason = explanation-string
Explanation: A new version of the log file was created. The reason string always indicates that it was done when the License Registrar started.
User Action: None required.

MESSAGE: message-text
Explanation: The message displayed describes diagnostic event information.
User Action: None required.

SERVER_LICENSE_ASSIGNED:
Product = product-name Client Addr = client-address Client ID = client-id-number Allocation = total-number-of-server-based-licenses-assigned
Explanation: The client indicated did not have a client-based license sufficient to access the local file server and was assigned a server-based product license, granting the client the right to access the local file server. The allocation indicates the number of server-based licenses in use after assigning the license.
User Action: None required.

SERVER_LICENSE_RELEASED:
Product = product-name Client Addr = client-address Client ID = client-id-number Allocation = total-number-of-server-based-licenses-assigned
Explanation: A client, previously assigned a server-based product license, has disconnected from the file server. The server-based license previously assigned to this client has been released. The allocation indicates the current number of server-based licenses in use after the release of the license.
User Action: None required.

	privacy and legal statement
6554PRO_006.HTML