IBM License Metric Tool V7.5.0.10

Audit Reports

Use this window to create new reports or delete existing audit reports. By clicking a report, you can drill down to view its summary, and then further down to view its details.

Audit report statuses
Some report statuses reflect situations that you can affect; others are simply information about system status.
Ready - The report is ready to be signed. Review and sign the report if it matches the processor value unit (PVU) or systems capacity, as measured in PVUs and CPUs, available to the licensed products.
Signing - The report is being signed. It is not possible to make any changes that would affect the report's PVU or CPU values. If the signing process fails, the audit report status will change to ready again. You will be able to check the reason why it was not signed in the log files.
Signed - The report has been signed. You must keep it for two years.
Pending - You must sign the reports in chronological order. There is a ready report that must be signed before you can sign this one.
Waiting - You can view this report but cannot sign it until the finalization period is over. The finalization period defines the number of days during which agents can continue reporting on the period covered by this report. If any agents have not yet sent their data to the server, the contents of this report might still change.
Running - Data for the report is not available at the moment because it is being collected or recalculated.
Note: When the service provider feature is enabled, data is also not available if essential periodic calculations for the corresponding report group are not triggered. You can trigger essential periodic calculations for a report group in the Manage Software Inventory panel. If essential periodic calculations are not triggered, the report status does not change from running.
Data can also be unavailable if you have performed one of the following actions:
  • new manual or scheduled report generation (if the report covers the period when data has not been aggregated)
  • software bundle management
  • product instance classification
Try again later to view this report.
The time you need to wait for the report to be generated depends on the following factors:
  • the value of the maxAggregateUsageAge parameter of the setserverconf command in case of report generation. This parameter specifies the age of the data (in days) before it is processed and consolidated by the server. The setting is used to ensure that all the information relevant for aggregation has arrived at the server, taking into account the frequency with which it is uploaded from the agent.
  • the size of your IT infrastructure which influences the time a given report is in the running state.
  • the amount of data processed in the software bundle management or product instance classification.
View only - You cannot sign this report because its reporting period overlaps with that of a signed report. However, you can still use the report as a reference (or delete it). Note that this report does not provide any additional information in the Details expandable section and about the PVU and tier table version.
Non-continuous - There is a gap between the end date of the last signed report or the server installation date (or the first day after the end date of the last migrated Tivoli® License Compliance Manager 2.3 report) and the start date of this one. To sign this report, you must first create and sign a report that covers the gap because the reports must be signed in chronological order. Use the info command to view the server installation date and the date of the next report.

The diagram shows the relationships between the statuses:

Diagram with additional explanation of audit report statuses.

Select Action
Use the drop-down list to select the action that you want to carry out.
Add Report
Creates new audit report.
Open
Opens the chosen audit report.
Delete
Deletes the chosen audit report. Reports with a Signed status can only be deleted after they are two years old.

To view the description of actions that you can perform with the table, see Table actions list.