Resolving ASRA ABENDs in IBM CICS TS: Command-Level Debugging & CEDF Analysis
Quick Diagnostic Summary: What Causes Resolving ASRA ABENDs in IBM CICS TS: Command-Level Debugging & CEDF Analysis?
CICS ASRA is the general transaction abend code indicating a program check (S0C4, S0C7, S0C1, etc.) inside an online transaction. Learn how to locate the execution offset in the CICS Transaction Dump, use CEDF and CEBR to inspect storage, and fix transaction failures.
1 Incident Symptoms: What Triggers Resolving ASRA ABENDs in IBM CICS TS: Command-Level Debugging & CEDF Analysis?
A customer service representative enters transaction TX40 on a 3270 terminal. The screen flashes:
DFHAC2206 14:15:02 CICS01 TRANSACTION TX40 ABENDED ASRA IN PROGRAM CUSTINQ.
UPDATES TO RECOVERABLE RESOURCES WILL BE BACKED OUT.
CICS writes a transaction dump to DFHDMPA/DFHDMPB. End users report the transaction unavailable, and the CICS region log shows repetitive ASRA occurrences under load.
2 Technical Root Cause & Architecture Mechanics
CICS intercepts all hardware program checks (operating system interrupts 01 through 15) and classifies them as transaction abend ASRA:
- Interrupt 07 (Data Exception / S0C7): 65% of all ASRAs. Caused by non-numeric data in packed fields in
DFHCOMMAREAor TS queues. - Interrupt 04 (Protection Exception / S0C4): 30% of ASRAs. Caused by bad pointers, unallocated
CONTAINERstorage, or subscript overruns. - Interrupt 01 (Operation Exception / S0C1): 5% of ASRAs. Bad module linking or corrupt branch vectors.
Because CICS shields the operating system from crashing, it invokes the CICS Condition Handler, captures diagnostic registers, backs out recoverable database changes via Dynamic Transaction Backout (DTB), and issues message DFHAC2206.
3 Step-by-Step Diagnostic & Code Resolution
# 1. Identify the Exact PSW and Program Offset
Open the CICS Transaction Dump in IPCS or your dump viewer (e.g., IBM Fault Analyzer or Sysview):
1. Locate the PSW AT ENTRY TO ABEND:
PSW: 078D1000 85A21480
2. Locate the load point of the program CUSTINQ:
PROGRAM CUSTINQ LOAD POINT: 85A20000
3. Compute the offset:
85A21480 - 85A20000 = +001480
4. Open the compiler listing for CUSTINQ generated with LIST or OFFSET. Look up offset +001480 to find the exact source statement (e.g., line 412).
# 2. Interactive Debugging with CEDF
In your CICS test region, activate the Execution Diagnostic Facility:
CEDF
Then initiate transaction TX40. CEDF intercepts every CICS command:
- Press
PF5to inspect Working-Storage. - Check the values of Commarea variables before calling dependent services.
- When the crash occurs, CEDF displays the exact instruction, registers, and memory dump before abending.
# 3. Inspect Temporary Storage with CEBR
If the program reads records from a CICS TS Queue, inspect the queue contents:
CEBR TSQ_CUST_DATA
Verify whether any record contains non-printable EBCDIC garbage or un-cleared null bytes.
Diagnostic Reference Matrix
| Attribute | Specification |
|---|---|
| Target Subsystem | IBM z/OS 2.4 - 3.1 • ABENDS & Diagnostics |
| Error Signature | CICS, ASRA, CEDF |
| Resolution SLA | < 15 Minutes via Verified StackMF Runbook |
| Technical Reviewer | Anshu, Chief Technology Architect • StackMF Architecture Pod |
Architectural Prevention & Performance Tuning Checklist
- Implement automated boundary checks on all CICS Channel and Container payloads before parsing.
- Enable CICS Storage Protection and Transaction Isolation (`TRANISO=YES`) in the SIT to isolate buggy transactions.
- Use IBM Fault Analyzer or modern OpenTelemetry CICS agents to automatically capture source-level stack traces.
- Enforce strict Commarea contract validation using OpenAPI schemas when integrating via z/OS Connect.
? Frequently Asked Questions
What is the root cause of Resolving ASRA ABENDs in IBM CICS TS: Command-Level Debugging & CEDF Analysis? ↓
How do you resolve Resolving ASRA ABENDs in IBM CICS TS: Command-Level Debugging & CEDF Analysis in production? ↓
How can teams prevent Resolving ASRA ABENDs in IBM CICS TS: Command-Level Debugging & CEDF Analysis in enterprise pipelines? ↓
Recommended Technical Runbooks
Resolving ABEND S0C7 (Data Exception) in COBOL Packed-Decimal (COMP-3) Fields
Debugging ABEND S0C4 (Protection Exception) in COBOL Linkage Section & Pointers
Mastering SB37, SD37, and SE37 Out-of-Space ABENDs in z/OS Sequential & PDS Datasets
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%.