S/MF
StackMF Knowledge Base • z/OS
DB2 SQL & Performance 11 min read 2026-09-27

Decoding the SCRT Report: Identifying 4HRA Spikes and Sub-Capacity Pricing Anomalies

A
Reviewed by Anshu
Chief Technology Architect & Mainframe Systems SME
Enterprise Modernization Advisory
Google AI Overview & Featured Snippet Quick Answer

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

jcl
//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:

text
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:

sql
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

? Frequently Asked Questions

What is the root cause of Decoding the SCRT Report: Identifying 4HRA Spikes and Sub-Capacity Pricing Anomalies? ↓
IBM bills software based on the highest simultaneous Rolling 4-Hour Average (4HRA) across the month:.
How do you resolve Decoding the SCRT Report: Identifying 4HRA Spikes and Sub-Capacity Pricing Anomalies in production? ↓
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.
How can teams prevent Decoding the SCRT Report: Identifying 4HRA Spikes and Sub-Capacity Pricing Anomalies in enterprise pipelines? ↓
Audit SCRT reports weekly using predictive tools rather than waiting for the end of the month.

Recommended Technical Runbooks

Authoritative Reference Documentation

Official IBM manuals, Redbooks, and vendor technical advisories:

Related Topics: SCRT4HRAMLCCost OptimizationWLMCapacity Planning
Diagnostic Runbook Notice & Nominative Fair Use Disclaimer

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 →

Enterprise Advisory

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%.