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:
| Element | Description |
|---|---|
|
Feature name/ Version |
Identifies the license for which this entry was made. |
|
%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. |
|
%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. |
|
LOG REPORT FOR Session: x |
The session numbers for this license server that were logged in this file. |
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.
Note: 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 multibyte characters if you view the CSV-format file with an appropriate text editor on an operating system that displays the multi-byte language. You can also create Microsoft Access reports from the CSV-format file that can be viewed on a computer using the appropriate multi-byte operating system. We suggest you to read through Creating License Server Use Reports for more information on creating reports from log file CSV-format output.