Created On:  16 February 2011


How do you check the number of licenses available and/or currently in use in the Visual COBOL runtime?


You can do this by using the lsmon tool on the machine where the licenses are installed.  You simply open a command prompt and run c:\Program Files (x86)\Common Files\SafenetNet Sentinel\Sentinel RMS Licnese Manager\WINNT\lsmon localhost

This will display the licenses in the server, who is using them and also how many licenses are in use or are left available.

A similar GUI utility is c:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WINNT\wlmadmin.exe.  Add the localhost to the defined server list and you will be able to see which licenses are installed.

For historial analysis you can analyse the lservrc.log file in the directory programdata\Micro Focus

The license server generates a usage log file with the following format:
No relevance to our implementation
No relevance to our implementation
 The date the entry was made, in the format: Day-of-week Month Day Time (hh:mm:ss) Year
 The time stamp of the entry.
 Name of the feature.
 Version of the feature.
 The transaction type. 0 indicates an issue, 1 a denial, and 2 a release.
0 Issue
1 Denied
2 Expired
3 Queue
4 QueueDenialLog
5 EngageLog
6 ConvertLog
7 QueueExpiredLog
8 CommuterCheckOut
9 CommuterCheckIn
 The number of licenses in use after the current request/release. (Encrypted if encryption level is set to 3 or 4.)
 How long, in seconds, the license was issued. Only applicable after a license release.
 The user name of the application associated with the entry.
 The host name of the application associated with the entry.
 The version of the Sentinel RMS Development Kit license server.
 The number of licenses handled during the transaction. (Encrypted if encryption level is set to 3 or 4.)
 The text passed in by the licensed application

Another way of analysing the log is by using the lsusage tool which is available in c:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WINNT

Running this against the log file will give you the required output.
Incident #2502559