This section describes the various events which can be logged to the License Registrar log file and the control logicals available to control the posting of events to the log file.

The types of events which 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 request 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:

• 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).

Each control logical can be turned either ON or OFF. Defining the logical to a value of one (1) turns the control logical ON; the control logical is considered OFF if it is undefined or defined 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

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.

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 Computer Corporation 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.

B.4 Event Logger (ADMIN/ANALYZE) Messages

The Event Logger (ADMIN/ANALYZE) logs events during file server operation. If a client is denied access to the file server, an entry is posted to the event log. To check the event log, enter the following command:

$ ADMIN/ANALYZE

Look through the events displayed for access denied messages. For example:

No server license for client---access denied.
Explanation: The client is not licensed and no server licenses are available; therefore, the client is denied access.
User Action: Obtain additional client-based or server-based licenses.

This appendix describes the client licensing process. This section includes the following topics:

• Section C.1, Client Licensing Software Algorithm, describes the specific steps in the client licensing process.
• Section C.2, License Determination Algorithm, describes the algorithm that the CLR uses to determine what license to request.

Table C-1, Client Licensing Software Process, describes the specific steps in the client licensing process. For more information, refer to Chapter 5, Configuring Client Software.

Table C-1 Client Licensing Software Process

Step	What Happens
1.	When the client is booted, the client license transponder (CLT) initializes the network (and, for Windows NT, writes an entry in the Application Event log), and then listens on the network for a license request. The client license requester (CLR) then looks for a license on the client.
	If... Then... A license is found on the client The CLR attempts to verify the license by connecting to the license server that issued the license. Result:   The license is verified. Go to step 5. The CLR could not connect to the license server. The CLR assumes that the license on the client is valid. Go to step 5. The license is invalidated by the license server. Go to step 2. For each license that is not on the client, or is revoked by the server Go to step 2. In each case, the CLR logs a message.
2.	The CLR determines whether the user specified a license server name. The CLR queries the local area network (LAN) for the license server until one or more license server names are returned. The CLR creates a list of license servers, starting with the license server specified by the user.
	Note: For license acquisition over a wide area network (WAN), the client must be configured to specify the license server name.
3.	The CLR steps through the list of license servers, querying each license server to determine whether the license has been assigned to the user. The client license data file is updated with the new information.
	If... Then... The client has the requested license Go to step 5a. If the client is missing any requested license Go to step 4.
4.	The CLR sends an assign request to the license server.
	If... Then... A license is available Go to step 5a. A license is not available The CLR prints a message to notify the user that it was unable to obtain a license. (On Windows NT, an event is written to the Application Event log.) Go to step 6.
5a.	The CLR loads the license into the CLT memory and updates the client license data file. The user is notified of the license status. Go to step 6.
5b.	The CLR deletes the invalid licenses from the CLT memory and updates the license data file. Go to step 6.
6.	Are there redundant or unnecessary licenses?
	If... Then... Yes The CLR clears the data file, releasing redundant or unnecessary licenses. Go to step 7. No Go to step 7.
7.	Exit.

C.2 License Determination Algorithm

The CLR uses the algorithm shown in Table C-2, Client Licensing Software License Determination Algorithm , to determine what license to request.

Table C-2 Client Licensing Software License Determination Algorithm

Step	The Client License Requester...
1.	Looks for an existing license data file.
	Is the license stored on the client?
	If... Then... Yes Verify the license. Go to Step 5. No Go to step 2.
2.	Looks for license information in the license configuration file. (This step is configuration-dependent. Refer to Section 5.2.3.1, License Configuration File, for more information.) Did the user specify a license configuration file at run time?
	If ... Then ... Yes Use the license information specified in the license configuration file. Go to step 5. No Go to step 3.
3.	Looks for a license configuration template file (CFG xxxx.TPL) stored on the client. (This step is configuration-dependent. Refer to Section 5.2.3.1, License Configuration File, for more information.) Is there a specified license to request in the license configuration template file?
	If... Then... Yes Use the license information specified in the license configuration template file. Go to step 5. No Go to step 4.
4.	Automatically look for an appropriate license based on the client's configuration. Is there an appropriate license based on the client's configuration?
	If... Then... Yes Use the appropriate license information. Go to step 5. No A license is requested. Go to step 5.
5.	End