Processor capacity = SU factor x 3600 x number of CPs in the processor model
                                           1,000,000

2378.4748 x 3600 x 6 / 1,000,000 = 51.4 MSUs

S/390 Usage Pricing requires two months of usage measurement data, from all system images (LPARs and VM guest systems) on the processor for which S/390 Usage Pricing is being requested, to set the initial S/390 Usage Pricing Charges price for each of the requested products. If any of the usage is from a Parallel Sysplex® then the measurement data must be from all the system images in the Parallel Sysplex. In this example the customer has a 9672-R65 processor which is not in a Parallel Sysplex and from which the customer has collected at least the required 2 months of usage data plus 1 day of additional usage data, which will be reported separately as the third and incomplete usage values (ones followed by a '#' on the report).

   //IFAURP   EXEC PGM=IFAURP,REGION=0M
   //STEPLIB  DD  DSN=SYS1.SIFALIB,DISP=SHR
   //SYSMSGS  DD  SYSOUT=*
   //SYSUDUMP DD  SYSOUT=*
   //SYSPRINT DD  SYSOUT=*
   //SMFDATA  DD  DSN=USAGE.SORTED89.DECJAN99,DISP=(OLD,KEEP)
   //SYSHIN   DD  DUMMY,DCB=BLKSIZE=16384
   //SYSHOUT  DD  DSN=USAGE.HISTORY.PHILA(+1),DISP=(NEW,CATLG,DELETE),
   //             DCB=(RECFM=VBS,LRECL=32760,BLKSIZE=16384),
   //             UNIT=SYSDA,SPACE=(CYL,(2,2),RLSE)
   //SYSIN    DD  *
    CUSTOMER(NAME('Liberty Bell Services')
             ADDRESS('22 Clapper Plaza',
                     'Philadelphia, Pa. 19101')
             CONTACT('Bennet Franklin')
             PHONE('(610) 555-1212'))
   *
    VENDOR(PRODOWNER('IBM CORP')
           NAME('IBM Corporation')
           ADDRESS('Philadelphia Branch Office',
                   'FAX: (610) 555-IBM1  Attn: Sally Sales')
           CODE(0012345))
   *
    PROCESSOR((9672,R65,04984)
               PRODUCT (PRODOWNER('IBM CORP')
                        PRODNAME('CICS')
                        TESTDATE(19981201))
               PRODUCT (PRODOWNER('IBM CORP')
                        PRODNAME('IMS DB')
                        TESTDATE(19981201))
               PRODUCT (PRODOWNER('IBM CORP')
                        PRODNAME('IMS TM')
                        TESTDATE(19981201))
               PRODUCT (PRODOWNER('IBM CORP')
                        PRODNAME('MQM MVS/ESA')
                        TESTDATE(19981201)))
   /*

• //STEPLIB references the IBM library, SYS1.SIFALIB, that contains IFAURP and the IFAURP reporting exits supplied with some IBM products, like MQM. The installation logic for MQM requires that MQM's CSQ8UBEX module and its IFAUMQM# alias be copied from MQM's .SCSQLOAD library to the SYS1.SIFALIB library. This must be done or the Software Usage Report will not list the MQM usage values correctly. Because no software vendors have provided product exit libraries for their products in this example, it is not necessary to concatenate any vendor libraries to SYS1.SIFALIB.
• //SYSMSGS references the file where the IFAURP Messages Report is written. This report lists the control statements processed by the usage report program and all error messages issued during its execution. This report should be used to assess the validity of all the other reports produced by this execution of the usage report program.
• //SYSPRINT references the file where all the other reports are written, including the Software Usage Report.
• //SMFDATA references a file of SMF type 89 records that were sorted before this step. See Figure 2 for sample JCL for the sort step and sample sort control statements. SMF type 89 records consist of subtype 1 records which contain the usage data for usage products and subtype 2 records which were introduced with OS/390 and contain registration statistics for products using z/OS Product Registration Services. These registration statistics are printed on IFAURP's Software Product Registration Report. The SMF type 89-2 records can be substantially larger than the SMF type 89-1 records and are not required to generate the Software Usage Report. All these examples will cover only the use of SMF type 89-1 records.
  In this example all of the SMF type 89-1 records, which have been collected from the 9672-R65 (04984) processor for December 1, 1998 to and including February 1, 1999, have been merged and sorted for the customer's three OS/390 V2 LPARs into the the sorted file named USAGE.SORTED89.DECJAN99. The Software Usage Report program must see at least one hour's usage more than the initial measurement period to consider the initial measurement period complete and place asterisks * after the initial measurement values. The usage data beyond the measurement period will be reported separately under a different month.

  Note: This sorted usage data is being saved since it may optionally be used in Example 13: Placing products under S/390 usage pricing charges.
• //SYSHIN must be specified as DD DUMMY, because this is the first time that the customer has run IFAURP and thus no history file exists.
• //SYSHOUT references the IFAURP output history file named USAGE.HISTORY.PHILA that is created as a result of this job step. The last qualifier, PHILA, designates the customer's data center location for the processor from which the usage data was collected. In this example USAGE.HISTORY.PHILA is a generation data group (GDG) and will be assigned the full name of USAGE.HISTORY.PHILA.G0001V00. See z/OS DFSMS Using Data Sets. for a detailed explanation of GDGs. This new history file will contain the control statements used for this execution and the usage data of the SYSHIN file and the SMFDATA files. Once these SMF type 89-1 records have been processed and their data saved on this history file, the original type 89-1 records are no longer required as input to future executions of IFAURP.
  Note: you can optionally choose to DUMMY this file when generating the Software Usage Report for the initial price quote, provided you keep the USAGE.SORTED89.DECJAN99 file as input to Example 13: Placing products under S/390 usage pricing charges, which indicates how to actually request OS/390 Usage Pricing Charges.
• //SYSIN references the IFAURP control statements required to provide customer and vendor descriptions, as well as, to specify the processor and products to be selected for S/390 Usage Pricing Charges.
• CUSTOMER This control statement is required and must precede all other control statements.

  NAME

  This parameter supplies the customer name to each vendor and is required for IFAURP to execute. IBM recommends that customers use the name by which they are known to IBM for this field.

  ADDRESS, CONTACT, PHONE

  These parameters provide the customer's mailing address, the name of the customer representative to be contacted if IBM has questions about the report and the contact's phone number.

  Note: The customer provided all these parameter values in this example, since it is easy enough to do when creating the original control statement. Supplying all the CUSTOMER parameters for the price quote eliminates the risk that these parameters will be missing from any of the follow on reports which must be sent to IBM.

• VENDOR This control statement associates the product usage being reported on SMF type 89-1 records with a specific vendor. Each vendor should supply the information required for each keyword on this control statement to the customer. Since this example is for IBM products, all the VENDOR information will be for IBM.

  PRODOWNER

  This parameter specifies the value used by the vendor to identify all their products on type 89-1 records. "IBM CORP" appears because IBM identifies all its products with this value. This keyword is required.

  NAME

  This parameter identifies the name of the software vendor. This parameter is required and should be supplied by your IBM client representative.

  ADDRESS

  This parameter provides the vendor's mailing address and or telephone or FAX number. This information should be supplied by your IBM client representative.

  CODE

  This value represents the customer number under which all of the processors on the following PROCESSOR or SYSPLEX control statements are known to IBM (that is, all the processors for which usage data has been placed in this history file). Processors with different customer numbers must be placed in separate history files.

• PROCESSOR This control statement identifies the specific processor and products for which a pricing quote is being requested. Since this example is for a processor that not in a Parallel Sysplex, the PROCESSOR statement is used instead of the SYSPLEX statement.

  (9672,R65,04984)

  This field is used to identify the specific processor for which the remainder of the subparameters on this PROCESSOR control statement apply.

  Note: You must obtain the type and model values from Type-model values for IBM and non-IBM processors. Hitachi processors must use a model value for the appropriate Hitachi processor (for example, PILOT65). In the United States, the last 5 digits of the processor serial number are used to identify the processor. Outside the United States, this 5–digit serial number must be prefixed with a 2–digit manufacturing location.

  PRODUCT

  CICS, IMS and MQM are all eligible for S/390 Usage Pricing Charges on the 9672-R65, because at least one LPAR has OS/390 V2 and CICS, IMS and MQM each have an eligible S/390 Usage Pricing Charges version (such as CICS V4, IMS V6 and MQM V1). Since IMS V6 is being used, usage from IMS V5 and IMS V6 will be aggregated and the aggregated usage will be used to set the S/390 Usage Pricing Charge for IMS V6. There will be no charge for IMS V5, since its usage is being charged for under IMS V6. IMS TM's ETO feature will also be placed under S/390 Usage Pricing, whenever the base IMS TM feature is placed under S/390 Usage Pricing Charges. In this example, DB2 does not qualify for S/390 Usage Pricing since the customer is running DB2 V4.1. DB2 eligibility for S/390 Usage Pricing starts with DB2 V5.

  Each product for which a S/390 Usage Pricing Charges price quote is being requested (for example, CICS, IMS DB, IMS TM and MQM MVS/ESA) requires its own set of PRODOWNER, PRODNAME and TESTDATE keywords.

  Note:

  1. Although IMS DB and IMS TM are base features of the same product, each can be placed on S/390 Usage Pricing independently of the other; therefore, each requires its own control statement.
  2. Each product feature (for example, IMS TM ETO) must have the same pricing option has its base product. Such features, however, do not appear on PRODUCT control statements.
  3. TSO/E is a part of z/OS and not separately priced. Therefore, TSO/E is not eligible for S/390 Usage Pricing Charges.

  PRODOWNER

  All IBM products require the value "IBM CORP" for this field.

  PRODNAME

  Identifies each product that the customer wants to request an S/390 Usage Pricing price quote for. Since it is only for a price quote. the customer has chosen all of their eligible S/390 Usage Pricing products.

  TESTDATE

  The value of 19981201 signifies the fact that the customer would like to obtain the usage value, and might also want a price quote, for a product without actually starting S/390 Usage Pricing Charges billing. To ensure that the usage values correspond to the values that S/390 Usage Pricing would use, use a TESTDATE value that is the same as the value that would be used for the START parameter. The value used for the START parameter can be determined as follows:

  1. The customer has met all the S/390 Usage Pricing requirements by that date.
     1. December 1, 1998 is the earliest initial measurement start date which can be used to place a product under S/390 Usage Pricing Charges.
     2. SMF data must be collected from all of the OS/390 and z/OS® LPARs on the processor on or before the START date.
     3. If DB2 is being placed under S/390 Usage Pricing Charges, all copies of DB2 on that processor must be restarted, after SMF type 89-1 record collection has been activated on all the OS/390 and z/OS LPARs on that processor.
  2. The START value is no earlier than 72 days before the date that this report was run. This is important, because START dates earlier than 72 days can not meet the IBM requirement that IBM receive the Software Usage Report within 10 business days after the end of the measurement period (START date + 28+30 measurement days (2 months) + 14 calendar days = 72 days).

  Note: Some IBM geographies will accept the usage collected during a new product's last month under test allowance for the first month of the 2–month initial measurement period.

                                    Measured Usage and S/390 Usage Pricing Charges                                          PAGE   1
 IFAURP 3.1.2                                    Software Usage Report                                               2 FEBRUARY 1999

 ------------------- Customer No: 0012345  -------------------      -------------- Software Vendor: IBM CORP         ---------------
 Liberty Bell Services                                              IBM Corporation
 22 Clapper Plaza                                                   Philadelphia Branch Office
 Philadelphia, Pa. 19101                                            FAX: (610) 555-IBM1  Attn: Sally Sales
 Contact/Phone: Bennet Franklin / (610) 555-1234

 - Report -   --- Measurement Period End Dates ---   |   ---------------------------- Processor ----------------------------
  Due Date    End Date  Product Name(s)   Function   |   Category    Type-Model   Serial       Begin-End Dates     SU Factor
  --------    --------  ----------------  --------   |   ----------  ----------   -----------  -----------------   ---------
                                                     |   Machine     9672-R65     04984        01Dec98 - 01Feb99   2378.4748
                                                     |   9672 CEC    9672-R65     04984        01Dec98 - 01Feb99   2378.4748

 =================================================== For Collection Purposes Only ===================================================

                                              ------------------------ Monthly Chargeable Product Values -----------------------
 ---------------- Product -----------------    1998  1999
 NUMBER(S) NAME           VERSION  FUNCTION     DEC   JAN   FEB   MAR   APR   MAY   JUN   JUL   AUG   SEP   OCT   NOV   DEC
 -------- --------------- -------- --------    ----  ----  ----  ----  ----  ----  ----  ----  ----  ----  ----  ----  ----
                          MAX MVS/ESA LPARS:      3     3     3     -     -     -     -     -     -     -     -     -     -
                      PERCENT MISSING HOURS:     10     9    90     -     -     -     -     -     -     -     -     -     -

 5655-018 CICS            4.1                  9.91  10.4X 10.7#    -     -     -     -     -     -     -     -     -     -      (01)
          X 01Dec98-31Jan99

 5695-DB2 DB2             4.2.1                10.2# 9.90  9.75#    -     -     -     -     -     -     -     -     -     -      (01)
          # 01Dec98

 5655-158 IMS DB          6.1                  30.2X 28.5  28.4#    -     -     -     -     -     -     -     -     -     -      (01)
 5695-176                 5.1
          X 01Dec98-31Jan99

 5655-158 IMS TM          6.1                  8.97X 8.95  8.77#    -     -     -     -     -     -     -     -     -     -      (01)
 5695-176                 5.1
          X 01Dec98-31Jan99

 5695-137 MQM MVS/ESA     1.2                  5.50X 5.34  4.57#    -     -     -     -     -     -     -     -     -     -      (01)
          X 01Dec98-31Jan99        (MQM#9501)

 5647-A01 OS/390          02.04.00 TSO/E       22.8# 20.7  21.9#    -     -     -     -     -     -     -     -     -     -      (02)
          # 01Dec98


 ============================================================= Notes ================================================================

   X  - Begin-end dates of the initial measurement period
   #  - Data not collected for a full month.
   <  - Value to the left is the largest value of complete months shown.
 (01) - Hourly rate in millions of CPU Service Units (MSUs).
 (02) - Not eligible for Measured Usage charges