The CHECKIN and CHECKOUT keywords indicate a license feature or capability checkin and checkout respectively. If you look closely at the details of these lines, you can gain some valuable statistics on overall license usage.

For each license checkout request, you will see at least two entries logged, one for the actual license feature that is checked out from FlexNet and one or more for the capability request to the Licensing Interconnect. (See the Capability definition in Glossary).

Example:

2012/09/20 12:42:36 CHECKOUT ane3fl 2024 R2 (2012.0814) 1/1/23/500 131/156/310068/310068   
     7060:7884:MECH:john@plum:winx64  65028:194.154.5.32 

In this example, one license for Ansys Multiphysics (ane3fl) is checked out by user john, by the Mechanical (MECH) application (with process ID 7060, Mast Process ID 7884 and Licensing Interconnect-assigned ID of 310068), from hostname plum (a Windows x64 system), on June 6, 2012 12:42:36. User john currently has only this license checked out. Of the 500 licenses of Ansys Multiphysics available, 23 are currently in use. There are currently 131 client applications connected to the license server. The highest number of concurrent connections to this license server is 156, with a total number of client applications served of 310068. The revision of the Ansys application being run is 2024 R2, built on June 3, 2012. The socket number and the IP address of the machine making the request are 65028 and 194.154.5.32, respectively.

2012/09/20 12:42:36 CHECKOUT MECH_STRUCT 2024 R2 (2012.0814) 1/1/17/-1 131/156/310068/310068  
     7060:7884:MECH:john@plum:winx64 65028:194.154.5.32 

This example is the capability checkout that corresponds to the above license feature checkout. A -1 in Field D should only occur for the capability checkout, not for the feature checkout. The -1 indicates that licenses are being used in shared mode.

The identifier (RESERVE) immediately following the license feature name indicates that the license checkin/checkout is for a license for a Design Point solve and is the time when the license is actually checked in or out.

This keyword is seen when the Licensing Interconnect is obtaining the license feature and FlexNet options file cache from another license server. You will typically see CACHE_SERVER lines appear in pairs. The first line indicates that the Licensing Interconnect is attempting to cache the license feature and FlexNet options file information of another license server. The second line indicates the status of the cache.

These messages provide a periodic status of the Licensing Interconnect. Information such as memory usage, uptime, etc. is given.

Depending on the verbosity setting of the Licensing Interconnect log file, you may see one of these entries for each client that connects to the Licensing Interconnect. The entry is logged as soon as the client’s socket is connected and prior to any processing.

This keyword will appear when the application explicitly informs the Licensing Interconnect that it is exiting; this triggers the check-in of any capabilities currently checked out by the application. See also CLIENT_SHUTDOWN.

This keyword will appear when the Licensing Interconnect has detected that the application has exited but has not explicitly passed the CLIENT_EXIT message. See also CLIENT_EXIT.

This keyword is seen when connecting to another license server for the cache information and that license server is down or unreachable.

This system memory information will appear each time the Licensing Interconnect allocates additional memory.

This keyword indicates that queuing has been initiated for the capability in question (regardless if it is FlexNet queuing or ALI queuing).

This keyword is displayed when the FLEXlm server grants the license.

This keyword indicates when a queue request is initiated to the FLEXlm server.

If the connection between the Licensing Interconnect and the client application has been lost, once the RECONNECT has occurred, this keyword will indicate that the license feature or capability has been checked out again.

If the connection between the Licensing Interconnect and the client application has been lost, this keyword will indicate that the communication has been restored.

This keyword indicates the locking mechanism is in play to prevent FLUENT and CFX from running in shared mode outside of the Workbench environment. It prevents you from running FLUENT and CFX Pre, Post and Solve concurrently outside of Workbench with a shared license. A SHARE_LOCKER checkout entry will appear any time one of these products is checked out.   This only applies to the products that will run cross-application, such as Ansys CFD.

A SPLIT_CHECKOUT will occur when there are license checkout requests for two or more of the same license feature.  The primary example where multiple licenses of the same feature are requested is for HPC products.

Example:

2012/09/20 15:05:23 SPLIT_CHECKOUT anshpc_pack 2024 R2(2012.0814) 2/6/10/500 152/165/314121/314121 
     7508:6652:ANS_SOLVER:ted@papaya:winx64 65028:194.154.5.32

2012/09/20 15:05:23 CHECKOUT ANS_SOLVER_HPC 2024 R2 (2012.0814) 16/44/56/184 152/165/314121/314121
     7508:6652:ANS_SOLVER:ted@papaya:winx64 65028:194.154.5.32

Similar to the regular CHECKOUT, this example shows the license feature SPLIT_CHECKOUT for anshpc_pack and the corresponding capability checkout for ANS_SOLVER_HPC.