z/VSE capacity measurement / sub-capacity reporting
Ingolf24 120000DRN3 Visits (2685)
Since z/VSE version 4 we support sub-capacity reporting. Sub-capacity reporting is required for the price metrics Midrange Workload License Charge (MWLC) with sub-capacity option for zEC12, z196, z10 and z9 processors as well as the price metrics Advanced Entry Workload License Charge (AEWLC) with sub-capacity option for zBC12 and z114 processors.
For z/VSE installations the Sub-Capacity Reporting Tool (SCRT) - an IBM tool - reports the capacity information of sub-capacity products. Those are charged based on the four hour rolling average utilization of your workload. The four hour rolling average utilization is gathered by z/VSE's Capacity Measurement Tool (CMT) and recorded in sequential files on ECKD, FBA or SCSI disks.
SCRT uses that data to generate the reports, which can be send to the License Management System (LMS - via email or the web application).
With the zBC12 you may limit the physical processor capacity of an LPAR (absolute capping), which helps to achieve your sub-capacity targets. This is transparently reflected in the measured data.
z/VSE's Query Virtual Server (QVS) API may also retrieve the measurement data, that may be used for license management. QVS supports absolute capping with the z/VSE V5.1 APAR DY47479. When running as a z/VM guest you need z/VM APAR VM65360 in addition.
More information on sub-capacity measurement is here.