Welcome to the System z Software Sub-Capacity Corner. This website describes details related to Sub-Capacity: terms & conditions, procedures and technology.
How to Update the NO89 DD section in the SCRT JCL
The SCRT JCL contains a NO89 DD section which lists the sub-capacity eligible MLC programs and IPLA Execution-based programs which do not create SMF89 or SCRT89 records. Customers must modify each entry in the NO89 DD section to indicate the name(s) of the LPAR(s) where that program ran at any time during the reporting period, or use the keywords *NONE or *ALL as appropriate. Only the MLC programs and IPLA Execution-based programs included by IBM in the NO89 DD section are supported by the SCRT release which came with that release of the JCL. If new NO89 programs are announced it will be necessary to download a new release of SCRT to support them, it is not possible to manually add new product ids into the old JCL without updating the release of SCRT. Products which are supported with SMF89 or SCRT89 data records cannot be added into the NO89 DD section.
It is also not necessary and not possible to add the product ids of any IPLA z/OS-based or IPLA Reference-based programs into the NO89 DD section in order to cause them to be reported by SCRT. It is also not possible to delete individual product ids from the NO89 DD section, although z/OS customers who do not run z/VSE may delete the entire set of z/VSE NO89 product ids if they wish.
How to Submit Sub-Capacity Reports
Sub-Capacity Reports may be submitted in one of two ways: via the web or via email. New Sub-Capacity customers should submit their SCRT report(s) via the Internet submission procedures described on the SCRT Submit page. Existing Sub-Capacity customers may migrate to the Internet process now, or continue to use their current process until notified by IBM that they must migrate. It is IBM's intent to eventually require all customers to submit via the web.
When to Submit Sub-Capacity Reports
Sub-Capacity Reports, whether submitted via email or via the web, must be submitted to IBM by the close of business of the 9th day of the month. The billable MSUs listed in the Product Summary Section of the Sub-Capacity Report affect customer billing the month after the report is received. Failure to submit a Sub-Capacity Report for a given month will result in one month of Full-Capacity charges for that machine.
For example, if you are collecting data from January 2nd - February 1st, then your submission deadline for this reporting period (January 2nd through February 1st) is February 9th. The billable MSUs listed in this Sub-Capacity Report will be used to establish the billing, effective March 1st for the month of March. In this case, if the January 2nd - February 1st Sub-Capacity Report is not received by IBM by February 9th, then the billable MSUs for March would be based upon the full MSU rated capacity of the machine. Full-machine billing would continue until the next Sub-Capacity Report is submitted.
Handling Sub-Capacity Reports for a Machine Upgrade
The Sub-Capacity Reporting Tool (SCRT) can handle machine model upgrades without any intervention. The Sub-Capacity Report will indicate with a comment that the machine model has changed, and the MSU values on the report will be used to set the billing as usual.
However, in cases when the machine type and/or the serial number changes there will be two Sub-Capacity Reports generated. SCRT will interpret the data as being from two different machines even though the data represents only one customer workload for the month. The customer should indicate in the "Customer Comments" field of both Sub-Capacity Reports that a migration has occurred, for example, "2097-12345 has migrated to 2817-34567". IBM will check to see that the Data Collection % on the first Report plus the Data Collection % on the second Report sum to 95% or more. For each product on both Reports IBM will use the higher of the two MSU numbers reported as the billing value for that product that month (capped, if appropriate, by the Full-Capacity MSU value of the target machine). Customers must complete the migration within a calendar month. The original box should no longer be installed or functional in future months.
Handling Sub-Capacity Reports for Machine Consolidations
The case when one or more machines are consolidated onto a different machine is similar to the Machine Upgrade scenario in some respects. For example, with a Consolidation from Box1 and Box2 onto Box3:
Customers must complete the consolidation to Box3 within a calendar month, Box1 and Box2 should no longer be installed or functional in future months.
|No Report for
Using the example Sub-Capacity Reports from the month before the consolidation, the applied rules would render the following billing the month after the consolidation:
z/OS = 100+50 = 150
DB2 = 98+46 = 144
CICS = 87+49 = 136
Applied to machine serial 2817-33333
Using the example Sub-Capacity Reports from the month of the consolidation, the applied rules would render the following billing the second month after the consolidation:
z/OS = (100+50) vs. 155= 155
DB2 = (97+47) vs. 135 = 144
CICS = (88+48) vs. 125 = 136
Applied to machine serial 2817-33333
For help with the Sub-Capacity Reporting Tool (SCRT) or questions related to Sub-Capacity pricing, please see the System z Software Pricing Help page.