Fixing ABEND S322 (CPU Time Limit Exceeded) and S222 (Job Cancelled) in Long-Running Batch
Quick Diagnostic Summary: What Causes Fixing ABEND S322 (CPU Time Limit Exceeded) and S222 (Job Cancelled) in Long-Running Batch?
ABEND S322 occurs when a batch job exceeds its allocated CPU time limit (due to an infinite loop, massive dataset scans, or inadequate JCL TIME parameters). Learn how to tune TIME parameters, optimize loops, and handle S222 operator cancellations.
1 Incident Symptoms: What Triggers Fixing ABEND S322 (CPU Time Limit Exceeded) and S222 (Job Cancelled) in Long-Running Batch?
An overnight database rebuild job runs for 4 hours and crashes:
IEF373I STEP /STEP020 / START 2026270.0100
IEF374I STEP /STEP020 / STOP 2026270.0500 CPU 240MIN 00.12SEC
IEF450I DBREBD01 STEP020 - ABEND=S322 U0000 REASON=00000000
Database indexes are left in rebuild-pending state, blocking morning online transaction systems.
2 Technical Root Cause & Architecture Mechanics
- ABEND S322: The job step consumed more CPU time than authorized by the JCL
TIMEparameter or system SMF default (JWT/ Job Wait Time inSMFPRMxx). - ABEND S222: The system operator or an automated console monitor issued the
CANCELcommand against the job due to excessive execution duration or lock blocking.
3 Step-by-Step Diagnostic & Code Resolution
# 1. Increase JCL TIME Parameter
For legitimately long-running batch extraction or utility jobs, specify sufficient CPU time:
//STEP020 EXEC PGM=DBREBD01,TIME=(600,00)
-
TIME=(600,00): Grants 600 CPU minutes (10 hours) and 00 seconds. -
TIME=1440orTIME=NOLIMIT: Disables the job CPU timer completely (use with caution).
# 2. Isolate Infinite Loops in Program Code
If the program should execute in 5 minutes but burns hours:
1. Examine the program PSW in the dump.
2. Check for missing read advances in PERFORM UNTIL loops:
* BAD: Never reads next record inside loop!
PERFORM UNTIL WS-EOF = 'Y'
PERFORM 2000-PROCESS-DATA
* MISSING: READ INPUT-FILE AT END MOVE 'Y' TO WS-EOF
END-PERFORM.
# 3. Add Intermediate Checkpoint Commits
Ensure long-running batch jobs commit periodically to avoid lock contention that triggers operator cancellations.
Diagnostic Reference Matrix
| Attribute | Specification |
|---|---|
| Target Subsystem | IBM z/OS 2.4 - 3.1 • ABENDS & Diagnostics |
| Error Signature | JCL, ABEND S322, ABEND S222 |
| Resolution SLA | < 15 Minutes via Verified StackMF Runbook |
| Technical Reviewer | Anshu, Chief Technology Architect • StackMF Architecture Pod |
Architectural Prevention & Performance Tuning Checklist
- Never specify `TIME=1440` on untested batch programs.
- Monitor SMF Type 30 records to establish historical CPU run-time baselines.
- Use automated alerts when batch jobs exceed 2x their standard historical elapsed time.
? Frequently Asked Questions
What is the root cause of Fixing ABEND S322 (CPU Time Limit Exceeded) and S222 (Job Cancelled) in Long-Running Batch? ↓
How do you resolve Fixing ABEND S322 (CPU Time Limit Exceeded) and S222 (Job Cancelled) in Long-Running Batch in production? ↓
How can teams prevent Fixing ABEND S322 (CPU Time Limit Exceeded) and S222 (Job Cancelled) in Long-Running Batch 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%.