The Herb Garden

This document outlines the steps needed to produce Sub Capacity Reports using the Sub Capacity Reporting Tool (SCRT). Once they are produced, these reports should be checked for reasonableness and sent to IBM via the License Management Support (LMS) website for billing purposes.

SMF records 70 (subtype 1) and 89 are to be collected.

The reporting periods are currently fixed by IBM. A reporting period starts at 00:00 on the second day of one month and runs through 24:00 on the first day of the next month. The SCRT discards data from any days outside the chosen reporting period. For example, on the 2^nd March, the data for February will be eligible for processing.

 The reports MUST be sent to IBM by the 9^th of each month by the registered member of staff.

Transmitting weekly TSAD data is part of the Terms and Conditions for subcapacity pricing. The data is required for audit purposes. TSAD is sent using the IBM zSeries Remote Support Facility (RSF).

At the beginning of each month visit http://www.ibm.com/zseries/swprice/scrt to check for a more recent version of SCRTTOOL. Currently (June 2007) the version is 13.1 but new versions are released on a fairly regular basis. IBM will only accept data produced on the most recent version (the release shouldn't matter).

It is recommended that you download and use "Using the Subcapacity Reporting Tool SCRT Version 13.1.0" as a reference. It can be found as a pdf document on the website above.

In order to download a new release always follow the latest instructions but typically they will follow this pattern:

1. On the above website click on “Download SCRT Vx.y” (where x.y represents the latest version) to download scrtool.exe (it is a relatively small download).
2. You will need to logon to the IBM site with your IBM userid and password.
3. Once this file is on your workstation double click it to expand it to SCRTOOL.BIN.
4. Use ftp to upload this file in binary mode to the z/OS system as an LRECL=80,BLKSIZE=0,RECFM=FB dataset. This file contains the object module and the JCL and parameters to run it.
5. Edit the JCL (be sure to leave CAPS OFF) as detailed in the imbedded comments e.g. the jobcard, the SMF input dataset(s) and the parameters. The SMF datasets can be a concatenated, do not need to be pre-sorted and can contain data from before and after the reporting period.
6. Submit the job. The result is either a pds or a flatfile containing csv data.
7. ftp the csv data back to your workstation and view it using Microsoft Excel (or a similar spreadsheet application) making sure it looks reasonable (see Section 3 of this document).
8. When satisfied, and before the 9^th of the month, send the file to IBM via the website (see Section 4 of this document).

If you currently have the most recent version you probably need to start in step 5 above ensuring you specify the relevant SMF datasets.

The NO89 DD statement

Use this parameter to enter information about any listed products STW are using that do not produce SMF type 89 records. The JCL is delivered with a list of such products already coded.

You must enter a valid value for each product in the list of z/OS NO89 control statements.

• If you do not have a product installed or are not using that product on the CPC(s) being processed by that execution of the SCRT, enter *NONE next to the product number. Do not delete products from the list of z/OS NO89 control statements.
• If a product in the list runs in all LPARs in your configuration, enter *ALL.
• If a product runs in one or more LPARs, enter a list of the LPAR names in which the product runs.

Once this list has been coded for STW it is likely that changes will be rare.

REPORT VERIFICATION

Customers have the primary responsibility for preventing uncontrolled loops, operator errors, or unwanted utilization spikes. However, IBM understands that occasionally situations that could not be prevented (especially situations related to disaster recovery) may cause exceptional utilization values. In these situations, IBM does not expect our customers to pay for the increased utilization associated with the unusual situation.

You re permitted to use your best judgement to determine if an unusual situation has occurred. IBM does not publish a list of unusual situations because they will by their nature be unpredictable. Indicate an unusual situation by writing the correct number of MSUs, per product, in the Customer MSUs field of the subcapacity report. Describe the reason for using the Customer MSUs field in the Customer Comments field.

IBM trusts your judgement when you indicate an unusual situation has occurred. However, if you repeatedly override the Tool MSUs (for example, you always have unusual situations occur at quarter close) or if large discrepancies are found during IBM audits (IBM Call Home TSAD data is compared with data from subcapacity reports), IBM will contact you at the time the pattern is noticed.

Note: If an unusual situation occurs, please do not delete any SMF records from the SCRT input data set and do not change any values in the Tool MSUs column of the report

SENDING OUTPUT TO IBM

Once the reports have been produced and reviewed they MUST be sent to IBM by the 9^th of the month.

To do this go to the IBM website at URL www.ibm.com/software/lms

• z/OS