Description and analysis of the software usage report generated by Example 13

The IFAURP report level appears in the top left corner of the report and indicates that the level is 3.1.0. This is the minimum IFAURP level required to support S/390® Usage Pricing Charges. The "Customer No" section contains the customer name, address, contact and phone number as provided by the subparameters of the CUSTOMER control statement. The customer number that is listed was provided by the CODE value from the VENDOR statement.

The "Software Vendor" section contains the abbreviated vendor name, "IBM® CORP" as registered by each product shown on this report. The vendor name and address appear as provided by the values supplied on the VENDOR control statement's NAME and ADDRESS parameters.

The "Report Date Due" section contains the date 14Feb99. This date is calculated by IFAURP based on the START date of the products appearing in the "Billing" section of the report. This is the date by which IBM must receive this Software Usage Report (based on START dates of 01Dec98). IBM will not accept this report after 14Feb99 for setting the S/390 Usage Pricing Charges for the products in the "Billing" section of the report.

The "Measurement Period End Dates" section contains the date 31Jan99. This date is also calculated by IFAURP based on the START date of the products appearing in the "Billing" section and represents the last full day for which usage measurement data must be processed by IFAURP. At least one additional hour of usage data beyond this date must be processed by IFAURP before IFAURP considers the measurement data complete for the initial measurement period.

The "Processor" section lists the specific IBM processor (9672-R65 #04984) for which usage values are being listed on this report. The Begin-End Dates field indicate the earliest date (01Dec98) and last date (01Feb99) for which the data collected on this processor has been processed by IFAURP.

The "PERCENT MISSING HOURS" section indicates the percentage of usage hours for which no SMF type 89-1 records were processed by IFAURP for the month indicated. This percentage is based on the number of LPARs listed on the line immediately above this section. The Software Outage Report lists the specific hours, which IFAURP considers missing, by LPAR. IBM is likely to require an explanation when this value is higher than 20%. The report's values of 10% and 9% are acceptable for the initial measurement period (December and January). Since IBM will not use the values listed under the month of February, the percent missing hours listed for that month (90%) will be ignored.

The "Billing" section of the report contains a list of all the products, which have a PRODUCT statement with a START parameter and which have usage to report. The products in this section are listed alphabetically by product name. The vertical bars between the months of May and June indicate that:

The measurement period immediately after the initial two month measurement period ends the last day of May 1999.
The second "Billing" period starts July 1, 1999 (1 full calendar month after the last day of the previous measurement period). This is done to give the customer time to generate the next required Software Usage Report and to give IBM time to set the S/390 Usage Pricing Charges for the next "Billing" period, while the customer is still being charged the price established for the initial "Billing" period.

The start of the second "Billing" period was established by the ALIGN value of "07" (July), as provided by the customer. If an ALIGN parameter was not provided, IFAURP would have established a default 12 month initial "Billing" period which would have placed vertical bars before the month of December 1998 and between the months of November and December 1999.

The "X", which appears in the "Billing" sections, has the following significance:

IFAURP considers the initial 2 month measurement period complete.
The usage value immediately to the left of the "X" is the value to be used to set the S/390 Usage Pricing Charges price for that product.
The usage values for the first two months correspond to the initial measurement period that is preceded by an "X" and listed just below the product name.

Because CICS® V4 is being used and OS/390® V2 is being used on at least one LPAR on this processor sometime during the initial measurement period, CICS is eligible for S/390 Usage Pricing Charges. The CICS usage value under the January column (10.4 MSUs) is followed by an "X", which indicates that IBM will use this value to establish the S/390 Usage Price for CICS V4, for CICS's initial "Billing" period. Because IFAURP lists the end date for CICS's initial measurement collection as 31Jan99, CICS's initial S/390 Usage Pricing "Billing" period starts on January 1, 1999 (the first day of the month in which the measurement ends), and the "Billing" period ends June 30, 1999 (per the ALIGN value of "07"). If the customer licensed any CICS priced features on this processor, those priced features would also be placed under S/390 Usage Pricing Charges for the same "Billing" period. The feature price would be set based on the CICS usage value.

Because IMS™ TM V6 is being used and OS/390 V2 is being used on at least one LPAR on this processor sometime during the initial measurement period, IMS TM is eligible for S/390 Usage Pricing Charges. The IMS TM usage is listed as the aggregated usage of both IMS TM V5.1 and V6.1. The IMS TM usage value listed in the December column (8.97) is followed by an "X" and will be used to establish the S/390 Usage Pricing Charge for IMS TM V6 and for IMS TM's ETO feature. Under S/390 Usage Pricing, IBM does not charge for the IMS TM V5 base feature. Since IMS TM has the same START date as CICS, it has the same initial measurement end date and, therefore, the same initial "Billing" period.

Note: Although IMS DB and IMS TM are both base features in the same product, they collect usage separately and can be placed under S/390 Usage Pricing Charges independently of each other. In this example IMS TM has been placed under S/390 Usage Pricing, while IMS DB has not.

Because OS/390 V2 is being used on at least one LPAR on this processor sometime during the initial measurement period, MQM is eligible for S/390 Usage Pricing. The MQM usage value which IBM will use to establish MQM's S/390 Usage Pricing Charge is in the December column, since that value (5.50) is the MQM value which is followed by an "X". Like IMS TM, MQM has the same START date as CICS, which means that it has the same initial measurement end date and, therefore, has the same initial "Billing" period.

Note: The Begin-End dates listed for MQM is followed by the value MQM#9501. This value represents the value of the MQM report exit that was invoked by IFAURP and used when processing MQM usage data. See the discussion for the //STEPLIB JCL statement in Example 12: Deciding which products to select for S/390 usage pricing charges for additional information about this exit.

The "Collection" section of the report contains the usage values for all the products which collect usage but do not have PRODUCT statements with START parameters. IBM will not provide S/390 Usage Pricing Charges for products appearing in this section of the report. DB2® is listed in this section and is not eligible for S/390 Usage Pricing Charges, because it is not an eligible DB2 version.

Since IMS DB V6 is being used and OS/390 V2 is being used on at least one LPAR on this processor sometime during the initial measurement period, IMS DB is eligible for S/390 Usage Pricing. IMS DB appears in the "Collection" section because the customer did not provide the required IMS DB PRODUCT statement with a START parameter, since the OS/390 Usage Price for IMS DB was higher than its PSLC price as determined in Example 12: Deciding which products to select for S/390 usage pricing charges.

Note: The IMS DB usage value for December (30.2) is followed by an "X" and IMS DB has a set of Begin-End dates listed immediately below its name. This occurred due to the IMS DB PRODUCT statement with a TESTDATE parameter that was used in Example 12: Deciding which products to select for S/390 usage pricing charges and saved on IFAURP's history file. If the //SYSHIN file is DUMMYed and no PRODUCT control statement is provided for IMS DB, the IMS DB usage value in the December column will be followed by an "#" and only a Begin date will be listed.

The usage value for the TSO/E component of OS/390 V2 is also listed on this report, because TSO/E continues to report usage even though TSO/E is now included with OS/390 and not priced as a separate feature, as indicated by its footnote number printed on the far right of the TSO/E usage line.

Note: This Software Usage Report must be received by IBM no later than February 14th, together with a signed IBM Customer Agreement Attachment for S/390 Usage Pricing in order for IBM to use this report to place the requested products under S/390 Usage Pricing Charges.