IBM® usage pricing note: The only report that is required for usage pricing participation is the Software Usage Report.

Seven reports are available with the usage report program:

The IFAURP messages report lists the IFAURP control statements and all the error messages related to this execution of IFAURP. See The IFAURP messages report for an example of this report and an explanation of the fields and their meanings. You should use this report to determine what, if any, error conditions IFAURP encountered and if any errors ended the program. Be aware that early program termination does not necessarily prevent the other IFAURP reports from being generated, even though these reports may be incomplete.

IFAURP error processing will also write hexadecimal printouts of the SMF type 89 records involved in specific error conditions to the IFAURP Messages Report, as a diagnostics aid. Be prepared to provide the IFAURP Messages Report to the IBM Support Center, if requested for problem determination.

The software usage report is produced for each unique occurrence of a sysplex, or stand-alone processor, and vendor name. The report lists the usage of each product and product function. See The software usage report for an example of the report and an explanation of the fields in the report and their meanings.

While the customer is responsible for generating and sending this report to IBM to participate in usage pricing, this report is primarily intended for IBM to use to set the usage band for participating MULC products, or the usage level for participating ULC products. (See the MULC Announcement Letter for a description of the usage band. See the ULC Announcement Letter for a description of the usage level.) You can, however, use this report to determine whether to start, continue, or stop usage pricing for the IBM products listed in the report.

The report can reflect the change that occurs when a product (like TSO/E) that was shipped and licensed separately is now covered under the z/OS® license.

The software product registration report lists all the products that SMF type 89 records (both subtype 1 and subtype 2) indicate are in use. The report thus includes both products that have registered with SMF for usage data collection and products that have registered with MVS™ as running on a particular system. See Figure 1 for an example of the report and an explanation of the fields in the report and their meanings.

The software summary report summarizes the processors, LPARs and products for which SMF type 89 subtype 1 records were gathered. Each time the usage report program, IFAURP, is run, the Software Summary Report is produced. See The software summary report for an example of the report and an explanation of the fields in the report and their meanings. You can use this report to audit the number of SMF type 89 records that were generated by each processor or sysplex for which data was provided to IFAURP. The report also indicates a list of all the products for which usage data was processed by IFAURP execution.

When the SMF input data set contains usage data for 2 partial months (04MAR94-23APR94) the Summary, Outage and Statistics Reports are generated for both March and April beginning March 1st and ending April 30th. The data for March 1st through 6th is obtained from the history file (if the data exists in the history file). However, if the last data in the history file was collected in February, the Summary, Outage, and Statistics Reports will also contain data for February as well.

The software outage report is produced for each processor and LPAR. It shows the hours in the reporting period when no SMF type 89 records were found. You can use this report to check for missing data. See The software outage report for an example of the report and an explanation of the fields in the report and their meanings. You can also use this report to verify that IFAURP has processed all the SMF type 89 records collected for each processor participating in usage pricing and running in single image mode or for each LPAR when running under PR/SM™.

The software statistics report is produced for each unique occurrence of a customer-defined SYSPLEX or stand-alone processor, and product owner name. The report shows the history of the usage of each product. See The software statistics report for an example of the report and an explanation of the fields in the report and their meanings. You can use this report to track the hour when the highest product usage occurred for each day on the processor or sysplex.

The time period report is produced for each unique occurrence of a customer-defined sysplex or stand-alone processor, product owner, product name, product function, for all products included in the Software Usage Report. It lists the measurement and billing periods and the “report due” data, by stand-alone processor and parallel sysplex name, for each product name and function for the product owner “IBM CORP” and for all other product owners. See The time period report for an example of the report and an explanation of the fields in the report and their meanings. You can use this report to simplify the scheduling of usage reporting by consolidating all the report due dates, measurement period and billing period begin-end dates, for all products running on all the processors and sysplexes associated with a particular history file, into a single report.

The valid processor report lists the processors presently supported by your level of the usage report program. See The valid processor report for an example of the report.

The processor capacity audit report shows changes that have occurred in the processor data. A new line is generated in the report for each change in Processor type, serial number, model, or SU factor. See The processor capacity audit report for an example of the report.