Parsing z/OS SMF Type 30 (Job Accounting) and Type 110 (CICS Telemetry) Records with REXX
Executive Summary: Parsing z/OS SMF Type 30 (Job Accounting) and Type 110 (CICS Telemetry) Records with REXX
System Management Facilities (SMF) records are the black box of z/OS. Discover how to write high-speed REXX scripts that decode SMF Type 30 (CPU/Job accounting) and Type 110 (CICS transaction metrics) without purchasing expensive third-party reporting tools.
1 Problem Statement & Architecture Context: Parsing z/OS SMF Type 30 (Job Accounting) and Type 110 (CICS Telemetry) Records with REXX
IT leadership demands daily reports showing top CPU-consuming batch jobs and CICS transaction counts, but licensing costs for third-party reporting tools (SAS, MICS, MXG) are prohibitive.
2 Technical Root Cause & Architecture Mechanics
z/OS writes all execution metrics into raw binary SMF datasets:
- SMF records contain standard headers followed by self-defining sections (triplets: Offset, Length, Number of sections).
- Using REXX functions like
C2D(Character to Decimal) andC2X(Character to Hex), binary SMF records can be decoded directly into human-readable CSV or JSON files.
3 Implementation Guide & Modernization Strategy
# 1. Extract SMF Records via IFASMFDP
Dump Type 30 records to a sequential dataset:
//SMFDUMP EXEC PGM=IFASMFDP
//SYSPRINT DD SYSOUT=*
//DUMPIN DD DSN=SYS1.MAN1,DISP=SHR
//DUMPOUT DD DSN=&&SMF30,DISP=(NEW,PASS),SPACE=(CYL,(50,10))
//SYSIN DD *
INDD(DUMPIN,OPTIONS(DUMP))
OUTDD(DUMPOUT,TYPE(30))
/*
# 2. Decode Binary Headers in REXX
/* REXX - DECODE SMF TYPE 30 RECORD */
"EXECIO * DISKR SMFFILE (STEM REC. FINIS"
Do i = 1 To REC.0
record = REC.i
smf_len = C2D(Substr(record, 1, 2))
smf_type = C2D(Substr(record, 6, 1))
If smf_type = 30 Then Do
/* Extract Job Name from Identification Section */
job_name = Strip(Substr(record, 19, 8))
user_id = Strip(Substr(record, 27, 8))
/* Extract CPU Time (Hundredths of a second) */
cpu_offset = C2D(Substr(record, 41, 4))
cpu_raw = Substr(record, cpu_offset + 1, 4)
cpu_seconds = C2D(cpu_raw) / 100
Say "Job: " job_name " User: " user_id " CPU: " cpu_seconds "s"
End
End
Exit 0
Technical Specifications Matrix
| Attribute | Specification |
|---|---|
| Target Environment | IBM z/OS • DevOps & Automation |
| Key Technologies | REXX, SMF, Telemetry |
| Delivery SLA | Accelerated Sprint Delivery via StackMF Pods |
| Technical Reviewer | Anshu, Chief Technology Architect • StackMF Architecture Pod |
Production Readiness & Verification Checklist
- Verify SMF triplet offsets dynamically rather than hardcoding record positions.
- Filter SMF records during `IFASMFDP` extraction to keep REXX input files manageable.
- Stream parsed SMF metrics into Elasticsearch or Grafana for modern cloud dashboarding.
? Frequently Asked Questions
What is the root cause of Parsing z/OS SMF Type 30 (Job Accounting) and Type 110 (CICS Telemetry) Records with REXX? ↓
How do you resolve Parsing z/OS SMF Type 30 (Job Accounting) and Type 110 (CICS Telemetry) Records with REXX in production? ↓
How can teams prevent Parsing z/OS SMF Type 30 (Job Accounting) and Type 110 (CICS Telemetry) Records with REXX in enterprise pipelines? ↓
Recommended Technical Runbooks
Migrating from Broadcom Endevor to Git & Modern CI/CD using Zowe CLI and IBM DBB
Broadcom CA-7 / CA-11 Decoupling: Migrating 20,000+ JCL Batch Schedules to Stonebranch or Control-M
Building Enterprise REXX Automation: Scripting TSO/E, ISPF Panels, and SDSF Job Parsing
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%.