lsusage - Displays the License Manager Log File
lsusage displays a summary of application usage, providing information on license transactions contained in the License Manager usage file.
Use lsusage in the following format:
lsusage [options]
One or more of the following options must be specified:
Option | Description |
---|---|
-l usage log file |
Selects the License Manager log file to display. Must be specified. If this is the only option, the summary will be displayed on the screen. |
-c CSV format file |
Specifies the name of an output file to which the output will be written in Comma-Separated Values (CSV) format. NOTE For information on the fields that appear in the usage log in CSV format, refer Contents of the usage log in CSV format. |
-f
feature1[,version1]: |
Specifies feature(s) and version(s) to be included in the output. Note that version is optional. If this option is not supplied, the output will contain all features and versions in the log file. |
-m start month (MM) |
Specifies the first month (1-12) of the time period to be included in the output. If not specified, then the -a option is ignored and January 1 is assumed for the start month and start day. |
-a start day (DD) |
Specifies the first day (1-31) of the month to be included in the output. For example, if you have specified March as the start month, specifying a start day of 1 means that the output will be for a time period beginning with March 1. If not included, and the -m option is included, a start day of 1 is assumed. |
-y start year (YYYY) |
Specifies the first year of the time period to be included in the output. Use four digits to specify the year. If not included, then -m and -a are ignored and the output begins with the first data in the file. |
-M end month (MM) |
Specifies the last month (1-12) of the time period to be included in the output. If not specified, then the -A option is ignored and the default value of December 31 is assumed. |
-A end day (DD) |
Specifies the last day (1-31) of the month to be included in the output. If not included, and the -M option is included, an end day of 31 is assumed. |
-Y end year (YYYY) |
Specifies the last year of the time period to be included in the output. Use four digits to specify the year. If not included, then -M and -A are ignored, and the output ends with the last data in the log file. |
-h |
Displays a list of all options that can be used. |
The lsusage display looks something like this:
Application Usage Summary |
||||||||
---|---|---|---|---|---|---|---|---|
%age |
%age |
Total Tokens Issued |
%age |
%age |
Min.App. |
Avg.App |
Max.App |
Total Capacity Issued |
For Feature Name: bounce, Version: Non-Capacity |
||||||||
0.00 |
100.00 |
2 |
0.00 |
0.00 |
2.35 |
3.08 |
3.82 |
- |
For Feature Name: bounce, Version: Non-Pooled Capacity, 4000 |
||||||||
0.00 |
100.00 |
2 |
0.00 |
0.00 |
2.35 |
3.08 |
3.82 |
8000 |
LOG REPORT FOR SESSION:0
where:
The application usage summary elements are described in the table below where:
>Feature Name and Version identify the license for which this entry was made.
>LOG REPORT FOR SESSION displays the session numbers for this License Manager that were logged in this file.
Element | Description |
---|---|
%age Denied |
The percentage of requests for this license that were denied (usually because the hard limit of the license had already been reached), or if license queuing is enabled, this is the percentage of queued requests denied. |
%age Issued |
The percentage of requests for this license that were granted. |
Total Tokens Issued |
The number of tokens for this license that were issued. NOTE The maximum supported value will be 4,294,967,294 (short form: ~4B), even if the cumulative sum of tokens for a single feature version goes beyond ~4B in lservsta or usage file. |
%age Queued Granted |
The percentage of queued license requests that were granted. |
%age QRequest |
The percentage of license requests that were placed in the license queue. (License requests are queued only if license queuing is enabled for this license.) |
Min. App. Duration |
The minimum number of minutes the application for this license was in use. |
Avg. App. Duration |
The average number of minutes the application for this license was in use. |
Max. App. Duration |
The maximum number of minutes the application for this license was in use. |
Total Capacity Issued |
The total capacity issued for the specific feature and version. |
**WARNING** lsusage will not display license transactions that are encrypted to level 3 and 4. For information on encrypted log file transactions, see Setting Usage Logging.
Regarding Multi-byte Characters
If the Sentinel RMS log file contains characters that are not 7-bit ASCII (for example, if a user name contains multi-byte characters such as Japanese Kanji characters), those characters will not be viewable when looking directly at the log file. However, if you use the lsusage -c option to create CSV-format output from the log file, you will be able to view the multi-byte characters if you view the CSV-format file with an appropriate text editor on an operating system that displays the multi-byte language. Also, when anonymous usage logging option is enabled, that multi byte user and host names will be logged anonymously.
The following fields appear in the usage log in CSV format. Refer to Contents of the Usage Log for description of these fields:
>Feature name
>Feature version
>Day of week
>Date
>Time
>Transaction ID
>Keys out
>Lifetime
>Username
>Client’s hostname
>License Manager version
>Number of tokens
>Log string
>Qkey ID
>Absolute position
>Group position
>Group name
>Time stamp
>Client ID