Sub-Capacity for z/VSE
With z/VSE V4 and later you have the option to allow z/VSE to produce SCRT89 accounting records. The SCRT89 records report sub-capacity MSUs on CPCs that are running z/VSE V4 or later. z/VSE uses the Capacity Measurement Tool (CMT) to produce SCRT89 accounting records. The CMT is shipped as part of z/VSE V4 and later.
Sub-capacity pricing is based on the four-hour rolling average utilization of the z/VSE LPARs or z/VM guests (or a combination of the two) observed within a one month reporting period. The reporting periods run from 00:00:00 on the second calendar day of the month through midnight (23:59:59) on the first calendar day of the following month.
If you run both z/VSE and z/OS on your participating CPC and have sub-capacity pricing for both z/VSE and z/OS, you must produce the sub-capacity report on the z/OS system. In this case use the SCRT89 records from your z/VSE systems and the SMF 70 / SMF 89 records from your z/OS systems as input to the same execution of SCRT, so that they appear on the same sub-capacity report for that CPC. Download the appropriate version of SCRT and follow the procedure in the "Processing SCRT89 data with z/OS" section of the SCRT Users Guide (PDF, 5.7MB).
If you only have sub-capacity pricing for z/VSE, you may produce the sub-capacity report by running SCRT on a z/VSE system (until October 2017, see below). Use the SCRT89 records from all of your z/VSE systems as input to the same execution of SCRT. SCRT produces a separate sub-capacity report for each CPC that it encounters in the SCRT89 records. Download the appropriate version of SCRT and follow the procedure in the "Processing SCRT89 data with z/VSE" section of the SCRT Users Guide (PDF, 5.7MB).
On 11 October 2016 IBM announced that the Classic version of SCRT which runs on a z/VSE system will no longer be supported after October 2017. Customers currently running SCRT on their z/VSE system should begin planning their migration to one of the Java version deliverables prior to October 2017. For more information about the Java versions of SCRT please see "Chapter 5. Using SCRT V24.10 on Windows and Linux systems" in the SCRT Users Guide (PDF, 5.7MB).
Additional information for z/VSE customers
Please note that z/VSE is only eligible for sub-capacity pricing when there are no versions of VSE prior to z/VSE V4 licensed to or running upon the same CPC. The following table illustrates the relationships between the commonly used names for the various versions of the VSE operating system and the Program ID (PID) numbers against which orders are placed for code delivery and against which billing is done.
|VSE Commonly Used Name||VSE Package PID (non-billing)||VSE Billing PID||VSE Billing PID Name|
|z/VSE V6||5609-VSE||5686-VS6||z/VSE V6|
|z/VSE V5||5609-ZV5||5686-CF9||VSE Central Functions V9|
|z/VSE V4||5609-ZV4||5686-CF8||VSE Central Functions V8|
|z/VSE V3||5609-ZVS||5686-CF7||VSE Central Functions V7|
|VSE/ESA V2||5690-VSE||5686-066||VSE Central Functions V6|
|VSE/ESA V1||5750-ACD||5686-028||VSE/SP Unique Code V5|
When a z/VSE machine has Sub-Capacity charges, and a version to version z/VSE migration is taking place, and if IBM has determined that the migration is eligible for the Migration Pricing Option (MPO), then charges for the previous version(s) are waived and the new version is charged at the combined concurrent peak MSUs for all versions of z/VSE reported on the customer's Sub-Capacity Report for that month.
On 14 February 2017 IBM announced Multi-Version Measurement (MVM) replaces Single Version Charging (SVC) for eligible z/OS and z/VSE software programs. MVM also replaces the Migration Pricing Option (MPO) and the IPLA Migration Grace Period.