Decoding the SCRT Report: Identifying 4HRA Spikes and Sub-Capacity Pricing Anomalies
Executive Summary: Decoding the SCRT Report: Identifying 4HRA Spikes and Sub-Capacity Pricing Anomalies
IBM Monthly License Charges (MLC) are dictated by your monthly Sub-Capacity Reporting Tool (SCRT) submission. Learn how to parse SCRT CSV logs, identify which LPAR and batch workload caused the peak billing hour, and implement capacity caps.
1 Problem Statement & Architecture Context: Decoding the SCRT Report: Identifying 4HRA Spikes and Sub-Capacity Pricing Anomalies
The enterprise CIO receives an unexpected 20% spike on the monthly IBM software invoice. Nobody on the mainframe team can identify which job or business event caused the peak billing hour to jump.
2 Technical Root Cause & Architecture Mechanics
IBM bills software based on the highest simultaneous Rolling 4-Hour Average (4HRA) across the month:
- The SCRT tool scans SMF Type 70 (CPU activity) and Type 89 (product usage) records across all LPARs in the sysplex.
- It identifies the single peak hour where combined MSU consumption was highest.
- An unconstrained batch extraction job overlapping with online transaction processing during the peak window permanently sets the monthly software bill at a higher tier!
3 Implementation Guide & Modernization Strategy
# 1. Execute and Generate the Monthly SCRT Report
//SCRTSTEP EXEC PGM=ISRSCRT
//SYSPRINT DD SYSOUT=*
//SMFDATA DD DSN=PROD.SMF.MONTHLY,DISP=SHR
//OUTPUT DD DSN=PROD.SCRT.REPORT.CSV,DISP=(NEW,CATLG,DELETE),
// SPACE=(CYL,(5,1))
# 2. Locate the Peak 4HRA Billing Hour in the Report
Open the generated CSV report. Search for section:
Product Max / Peak Utilization:
Product: 5650-ZOS (z/OS V2)
Peak MSU: 1,420
Peak Date/Time: 2026-09-18 02:00:00 UTC
Contributing LPARs: LPAR1 (920 MSU), LPAR2 (500 MSU)
This isolates the exact date and hour of the spike: September 18 at 02:00 UTC.
# 3. Cross-Reference Peak Hour with SMF Type 30 Records
Query SMF Type 30 records between 00:00 and 04:00 UTC on September 18 to list jobs consuming the highest CPU:
SELECT JOBNAME, SUM(CPUTIME)
FROM SMF_TYPE30_TABLE
WHERE START_TIME BETWEEN '2026-09-18 00:00:00' AND '2026-09-18 04:00:00'
GROUP BY JOBNAME
ORDER BY 2 DESC;
Offending job identified: UNLOAD_ALL_CUSTOMERS ran concurrently with nightly database reorgs!
# 4. Implement WLM Defined Capacity and Schedule Staggering
1. Shift UNLOAD_ALL_CUSTOMERS to 04:30 AM (outside the 4HRA peak window).
2. In WLM, configure Defined Capacity on LPAR1 to 850 MSUs, capping billing peaks automatically.
Technical Specifications Matrix
| Attribute | Specification |
|---|---|
| Target Environment | IBM z/OS • DB2 SQL & Performance |
| Key Technologies | SCRT, 4HRA, MLC |
| Delivery SLA | Accelerated Sprint Delivery via StackMF Pods |
| Technical Reviewer | Anshu, Chief Technology Architect • StackMF Architecture Pod |
Production Readiness & Verification Checklist
- Audit SCRT reports weekly using predictive tools rather than waiting for the end of the month.
- Use WLM Group Capacity Limits across Parallel Sysplex LPARs.
- Recompile top CPU batch consumers with Enterprise COBOL `OPT(3)` to lower base MSU burn.
- Contact StackMF for our specialized Mainframe 4HRA Optimization Assessment.
? Frequently Asked Questions
What is the root cause of Decoding the SCRT Report: Identifying 4HRA Spikes and Sub-Capacity Pricing Anomalies? ↓
How do you resolve Decoding the SCRT Report: Identifying 4HRA Spikes and Sub-Capacity Pricing Anomalies in production? ↓
How can teams prevent Decoding the SCRT Report: Identifying 4HRA Spikes and Sub-Capacity Pricing Anomalies in enterprise pipelines? ↓
Recommended Technical Runbooks
Resolving DB2 SQLCODE -911 (Reason 00C90088 / Deadlock) and -904 Resource Unavailable
DB2 z/OS Query Optimization: Converting Stage 2 (Residual) into Stage 1 (Indexable) Predicates
How Outdated RUNSTATS Cause Catastrophic Tablespace Scans in DB2 for z/OS
Authoritative Reference Documentation
Official IBM manuals, Redbooks, and vendor technical advisories:
This diagnostic runbook is published by StackMF Technologies LLP for educational and architectural reference only. All code snippets, JCL, and procedures are provided "AS IS" without warranty of any kind. Always test changes thoroughly in non-production sysplex environments prior to production rollout.
IBM, z/OS, CICS, Db2, IMS, RACF, and IDz are registered trademarks of International Business Machines Corporation. Broadcom, CA-7, and Endevor are trademarks of Broadcom Inc. All other trademarks belong to their respective owners and are referenced under the Nominative Fair Use Doctrine (US Lanham Act 15 U.S.C. ยง 1125 / Section 30 of the Indian Trade Marks Act, 1999) solely for technology compatibility and diagnostic identification. StackMF Technologies LLP is an independent consulting entity not affiliated with or endorsed by these vendors. View Full Legal & IP Policy →
Struggling with Critical Mainframe Incidents or Vendor Renewal Pressure?
StackMF deploys certified Senior Mainframe Engineers fluent in both z/OS legacy internals (COBOL, DB2, CICS, VSAM, CA-7, Endevor) and modern cloud stacks (React, Kafka, AWS, Git). Onboard dedicated pods in 48 hours or cut Broadcom licensing by 60%.