Figure 1 shows an example of the JCL and control statements that are required to print the initial monthly usage values for specific products before placing these products under Measured Usage License Charges (MULC). This example is important because it allows you to determine the product's initial usage value without committing to MULC (that is, without using the START keyword).

//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=&&SORT89,DISP=(OLD,DELETE)
//SYSHIN   DD  DUMMY,DCB=BLKSIZE=16384
//SYSHOUT  DD  DSN=MULC.HISTORY.#1234567(+1),DISP=(NEW,CATLG,DELETE),
//             DCB=(RECFM=VBS,LRECL=32760,BLKSIZE=16384),
//             UNIT=SYSDA,SPACE=(CYL,(2,2),RLSE)
//SYSIN    DD  *
*
  CUSTOMER(NAME('Acme Tulle and Dye Company'))
*
  VENDOR(PRODOWNER('IBM CORP')
         NAME('IBM Branch')
         CODE(1234567))
*
  PROCESSOR((9021,952,01111)
            PRODUCT (PRODOWNER('IBM CORP')
                     PRODNAME('CICS')
                     TESTDATE(19950407))
            PRODUCT (PRODOWNER('IBM CORP')
                     PRODNAME('TSO/E')
                     TESTDATE(19950407)))
/*  

• //STEPLIB references the IBM® library, SYS1.SIFALIB, that contains IFAURP and IBM product exits. The MULC PTF cover letters for both CICS® and TSO/E did not indicate that CICS or TSO/E required that an IBM vendor exit be installed either in this library or a concatenated library. 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.
• //SMFDATA references a file of SMF type 89 records that were sorted before this step. These type 89 records contain usage data for CICS, IMS™ TM and TSO/E starting on April 2, 1995, and were collected from 4 different LPARs on the customer's 9021-952 processor.
• //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 a history file named MULC.HISTORY.#1234567 that is created as a result of this job step. The last qualifier, #1234567, designates the IBM customer number for the processor from which the usage data was collected. In this example MULC.HISTORY.#1234567 is a Generation Data Group (GDG) and will be assigned the full name of MULC.HISTORY.#1234567.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 records have been processed and their data saved on this history file, the original type 89 records are no longer required as input to future executions of IFAURP.
• //SYSIN references the IFAURP control statements required to provide customer and vendor descriptions, as well as, to specify processors, sysplexes and products to be selected for MULC.
• CUSTOMER This control statement is required and must precede all other control statements.

  NAME

  This keyword identifies the customer as ‘Acme Tulle and Dye Company’ to the software vendor (IBM). This keyword is required.

• VENDOR This control statement associates the product usage being reported on SMF type 89 records with a specific vendor. Each vendor should supply the information required for each keyword on this control statement to the customer.

  PRODOWNER

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

  NAME

  This keyword identifies the name of the software vendor. Because the customer was still evaluating MULC, they chose to use an abbreviated name. This keyword is required.

  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 on that processor to be reported on.

  (9021,952,01111)

  This field is used to identify the specific processor for which the remainder of the keywords in this example apply. In the US the last 5 digits of the processor serial number are used to identify the processor. Outside the US this 5 digit serial number must be prefixed with a two digit manufacturing location.

  PRODUCT

  Each product, CICS and TSO/E, requires its own set of PRODOWNER, PRODNAME and TESTDATE keywords.

  PRODOWNER

  All IBM products require the value “IBM CORP” for this field.

  PRODNAME

  Identifies the product that the customer wants to see the calculated MULC usage value. Because the customer had satisfied the MULC conditions for CICS and TSO/E, both of these products were eligible for MULC and could be used as a valid PRODNAME value. The MULC PTFs for IMS TM, however, had not yet been installed and activated on all LPARs on this processor and so IMS TM is not yet eligible for MULC.

  TESTDATE

  The value of 19950407 signifies the fact that the customer would like to understand the usage for a product without actually starting Measured Usage License Charge billing. To ensure that the usage values correspond to the values that MULC would use, use a TESTDATE keyword value that is the same as the value used on the START keyword. The customer can determine the value used on the START keyword as follows:

  1. The customer has met all the MULC requirements by that date. April 7th was the first day after which the customer had applied and activated the CICS and TSO/E MULC PTFs on all LPARs on the specified processor and was collecting type 89 records from those LPARs.
  2. The date value is no earlier than 42 days before the date that this report was run. This is important, because dates earlier than 42 days can not meet the IBM requirement that it receive the Software Usage Report within 10 business days after the end of the measurement period (START date + 28-31 measurement days + 14 calendar days = 42-45 days).

                                                Measured Usage Software Report                                           Page   1
IFAURP  1.2.0                                        Software Usage Report                                            08 May 1995

------------------- Customer No: 1234567  -----------------           ------------  Software Vendor: IBM CORP      --------------
Acme Tulle and Dye Company                                            IBM Branch
Contact/Phone:

- Report -   --- Measurement Period End Dates ---   |   -------------------------- Processor -----------------------------
 Due Date    End Date  Product Name(s)   Function   |   Category    Type-Model  Serial        Begin-End Dates     SU Factor
 --------    --------  ----------------  --------   |   ----------  ----------  ------------  -----------------   ---------
                                                    |   Standalone  9021-952    011111        02Apr95 - 07May95   2565.3359

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

                                             -------------------------  Monthly Chargeable Product Values  ---------------------
------------------- Product ---------------  1995                                                           1996
NUMBER(S) NAME            VERSION  FUNCTION   APR    MAY    JUN    JUL    AUG    SEP    OCT    NOV    DEC    JAN
FEB    MAR
-------- ---------------- -------- --------  -----  -----  -----  -----  -----  -----  -----  -----  -----  -----  -----  -----
                          MAX MVS/ESA LPARS:     4      4    -      -      -      -      -      -      -      -      -      -
                      PERCENT MISSING HOURS:    12     80    -      -      -      -      -      -      -      -      -      -

5685-083 CICS             3.2                 2.67*  2.46#   -      -      -      -      -      -      -      -      -      -  (01)
         * 07Apr95-06May95

5665-013 IMS TM           4.1                 0.73   0.81#   -      -      -      -      -      -      -      -      -      -  (01)
5665-409                  3.1
         # 02Apr95

5685-025 TSO/E            2.4                 .093*  .078#   -      -      -      -      -      -      -      -      -      -  (01)
         8 07Apr95-06May95

  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  

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

  *   - Begin-End Dates of first month's usage data
  #   - 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)

       This report is documented in the publication "MVS/ESA Support for Measured Usage License Charges" GC28-1098.