SCRT is
a no-charge IBM® tool that reports
required license capacity for sub-capacity eligible
products that run on z/OS®,
z/TPF, or z/VSE® operating
systems. SCRT analyzes
a month's worth of utilization data for IBM z Systems™ CPCs and produces a sub-capacity report.
The sub-capacity report indicates
the required license capacity (in MSUs) of each sub-capacity eligible
product running on the z/OS,
z/TPF, or z/VSE systems.
z/TPF and z/VSE support
for sub-capacity differs
from z/OS
support, for example, by using SCRT89 records instead of SMF records.
Unless specifically noted, the same concepts described for z/OS
also apply to z/TPF and z/VSE.
For details about z/TPF support and its unique considerations,
go to the Sub-Capacity
Corner for z/TPF page.
For details about z/VSE support
and its unique considerations, go to the Sub-Capacity Corner for z/VSE page.
Traditional
sub-capacity pricing
is based on the four-hour rolling average utilization of the LPARs
in which the
sub-capacity products
execute. For each hour in the reporting period,
SCRT determines
the required license capacity by examining:
- The four-hour rolling average utilization, by LPAR
- Which eligible products were active in each LPAR
SCRT then cross-references
LPAR utilization and product execution by LPAR to determine the maximum
concurrent LPAR four-hour rolling average utilization—the highest
combined utilization of LPARs where each product executes during the
reporting period.
Products whose capacity is adjusted by Integrated Workload Pricing
and products eligible for Getting Started Sub-Capacity Pricing use
capacity algorithms that differ from those for traditional sub-capacity pricing.
See Using the Sub-Capacity Reporting Tool for
a description of these algorithms.
SCRT processes
the following data:
- In z/OS environments: System
Management Facilities (SMF) data, specifically, SMF type 70, subtype
1 (CPU Activity) records and SMF type 89, subtypes 1 and 2 (Product
Use) records
- In z/TPF and z/VSE environments:
SCRT89 records
SCRT uses
the data sets specified in the JCL as input, and has a single data
set as output. To comply with
sub-capacity pricing
terms and conditions, the input data sets must contain one reporting
period of SMF type 70 and type 89 records for all the z/OS images and SCRT89 records for all z/TPF
images on a zArchitecture CPC. (For more information about the reporting
period, see
Analyzing the sub-capacity report.) The output
can be:
- A partitioned data set (PDS) with one member
for each CPC found in the input data stream. Each member is one sub-capacity report. The report
is a text file in comma-separated value (.csv) format, which can most
easily be read by a spreadsheet program. For more information, see Using the Sub-Capacity Reporting Tool.
- A sequential data set that contains a single text file in comma-separated
value (.csv) format. This file contains all the reports for the CPCs
in the input stream to SCRT and can be
used to submit reports to the license management support (LMS) application.
For details on how to set this up, see the description of the OUTPUT
DD statement in Using the Sub-Capacity Reporting Tool.
SCRT also does
the following:
- Provides a simple, non-intrusive means for you to generate sub-capacity reports that show
required license capacity for all eligible sub-capacity products
that execute on a CPC
- Allows IBM to receive, view
and store sub-capacity reports received
from customers
- Allows IBM to generate customer
bills according to the sub-capacity reports received
from customers