Step 4: For either a colocated or dedicated solution, use SCRT to collect billing data and report to IBM

To collect billing data and report back to IBM, update SCRT with the solution ID. (For a dedicated solution, you can specify the solution ID in parmlib instead.) When creating the next report, SCRT reads appropriate SMF records and reports MSU use for each container. The report includes the solution ID for all defined solutions and, as appropriate, data about the tenant resource groups and other identifying information for each product.

When the system programmer sends the SCRT report to IBM, the IBM uses the solution ID to correlate the workload with the entitled Tailored Fit Pricing solution for that client, validates the workload and its entitled capacity, and handles software billing based on the report.

z/OS clients run the SCRT job monthly to prepare a report of CPU consumed on behalf of workloads run on the system.

For colocated solutions, the CPU resource reported for the address spaces and independent enclaves that are defined to Tailored Fit Pricing are subtracted by SCRT from the LPAR 4- hour rolling average reported for billing purposes. This allows Tailored Fit Pricing workloads to be deployed to existing z/OS systems, colocated with existing workloads, without impacting the monthly license charges that are associated with z/OS and other middleware running on the same system.

For more information, see Using SCRT for Tailored Fit Pricing.