 |
Figure 1 shows JCL and control statements
that are used to place CICS® and
TSO/E under the MULC option, by reporting the usage values for both
products in the “Billing” section of the Software Usage Report.
This example is a follow-up to the previous example where the CICS and TSO/E usage values were
reported in the “Collection” section of the Software Usage Report.
The customer has decided to place both products under the MULC option
and will use the same date for the START keyword that was used for
TESTDATE in the previous example. Because the usage values for all
products are recalculated on each execution of the usage report program,
using the same date will result in the calculation of the same usage
values, because the identical measurement period was chosen.
Figure 1. Example
JCL and control statements used to place CICS and TSO/E under MULC option//IFAURP EXEC PGM=IFAURP,REGION=0M
//STEPLIB DD DSN=SYS1.SIFALIB,DISP=SHR
//SYSMSGS DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SMFDATA DD DUMMY,DCB=BLKSIZE=4096
//SYSHIN DD DSN=MULC.HISTORY.#1234567(0),DISP=OLD
//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')
ADDRESS('155 Main Street',
'New London, CT 05512')
CONTACT('Fred Tulle')
PHONE('(203) 555-1212 ex 54'))
*
VENDOR(PRODOWNER('IBM CORP')
NAME('IBM Branch Office')
ADDRESS('1133 Westchester Avenue',
'Major City, Sample State 10604',
'FAX: 1-800-555-1212 ATTN: Usage Pricing')
CODE(1234567))
*
PROCESSOR((9021,952,01111)
PRODUCT (PRODOWNER('IBM CORP')
PRODNAME('CICS')
START(19950407))
PRODUCT (PRODOWNER('IBM CORP')
PRODNAME('TSO/E')
START(19950407)))
/*
- //STEPLIB references the IBM® library,
SYS1.SIFALIB, which 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 was not necessary to concatenate any vendor libraries to SYS1.SIFALIB.
- //SYSMSGS references the file where the IFAURP Messages Report
is written. Use this report lists the control statements processed
by the usage report program and all error messages issued during its
execution. Use this report 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 has been specified as DD DUMMY, because all the SMF
type 89 records have already been processed on a previous execution
of IFAURP. If this example showed the first time that IFAURP was run,
this DD statement must point to a data set containing SMF type 89
records.
- //SYSHIN references the previous copy of the history file, because
it contains all the usage data collected since April 2, 1995. If
this was the first time run of IFAURP, this DD statement must be specified
as DD DUMMY.
- //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.
MULC.HISTORY.#1234567 is a generation data group (GDG) and will be
assigned the full name of MULC.HISTORY.#1234567.G0002V00. This new
history file will contain the control statements used for this execution
and the usage data of the SYSHIN file and the SMFDATA file(s).
- //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. The customer has provided values
for the NAME, ADDRESS, CONTACT and PHONE keywords.
- VENDOR Because the customer will send this Software Usage
Report to IBM, he obtained the
PRODOWNER, NAME and ADDRESS values for this control statement from
his 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 to be reported on.
- (9021,952,01111)
- This field is used to identify the specific processor for which
the remainder of the keywords 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 each product for which the customer wants the calculated
MULC usage value. Because the customer was interested in CICS and TSO/E, these were the
values entered on a specific set of PRODUCT parameters.
- START
- This keyword actually begins processing the associated product
as a measured usage product by listing the product and its usage values
in the “Billing” section of the Software Usage Report. The value
of 19950407 signifies the fact that the customer has met both key
requirements of the START keyword on that date:
- April 7th was the first full day that 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. While the customer could have selected
a date later than April 7th for the START value, any START value earlier
than that date would have been invalid, because the MULC PTFs would
not have been activated for either CICS or
TSO/E on all LPARs on that processor.
- The date value is no earlier than 42 days of 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).
- ALIGN
- Because this execution contained the first product to START on
this processor, the customer could have used the ALIGN keyword with
the first PRODUCT statement. However, because the customer had no
reason to request that his billing period be aligned to any specific
month, this keyword was not used.
Figure 2. Software
Usage Report Generated for Example 2 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 Office
155 Main Street 1133 Westchester Avenue
New London, CT 05512 Major City, Sample State 10604
Contact/Phone: Fred Tulle (203) 555-1212 ex 54 FAX: 1-800-555-1212 ATTN: Usage Pricing
- Report - --- Measurement Period End Dates --- | -------------------------- Processor -----------------------------
Due Date End Date Product Name(s) Function | Category Type-Model Serial Begin-End Dates SU Factor
-------- -------- ---------------- -------- | ---------- ---------- ------------ ----------------- ---------
20May95 06May95 ***ALL*** | Standalone 9021-952 01111 02Apr95 - 07May95 2565.3359
=================================================== For Billing Purposes =========================================================
------------------------- 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 | | |
| | |
5685-025 TSO/E 2.4 | .093* .078# - - - - | - - - - - - |01)
* 07Apr95-06May95 | | |
---------------------------------------------------------------------------------------------------------------------------------
I certify that the values circled on this report indicate months for which that product was under test allowance.
-------------------------------------------- -------------------------------------------------- ------------------------
Name Signature Date
=============================================== For Collection Purposes Only =====================================================
| |
5665-013 IMS TM 4.1 | .732 .821# - - - - | - - - - - - (01)
5665-409 3.1 | |
# 02Apr95 | |
=========================================================== 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.
|
z/OS MVS Product Management
Copyright IBM Corporation 1990, 2014