Mastering SB37, SD37, and SE37 Out-of-Space ABENDs in z/OS Sequential & PDS Datasets
Quick Diagnostic Summary: What Causes Mastering SB37, SD37, and SE37 Out-of-Space ABENDs in z/OS Sequential & PDS Datasets?
Space ABENDs (SB37, SD37, SE37) crash critical overnight batch jobs when datasets exceed volume, extent, or catalog limits. Discover how to configure secondary allocations, RLSE, SMS Dataclasses, and Extended Format attributes to prevent volume exhaustion.
1 Incident Symptoms: What Triggers Mastering SB37, SD37, and SE37 Out-of-Space ABENDs in z/OS Sequential & PDS Datasets?
A critical end-of-month batch consolidation fails at 02:45 AM with:
IEC030I B37-04,IFG0554A,JOBEOM01,STEP040,SYSUT2,3420,VOL004,PROD.BILLING.MONTHLY.EXTRACT
IEF450I JOBEOM01 STEP040 - ABEND=SB37 U0000 REASON=00000004
Alternatively, variations such as D37-04 (No space available on current volume to satisfy secondary allocation request) or E37-04 (Dataset already allocated maximum allowable extents: 123 for non-extended sequential or 16 for standard PDS) bring the overnight batch processing pipeline to a dead halt.
2 Technical Root Cause & Architecture Mechanics
IBM DFSMS manages disk space allocations in primary and secondary extents:
- SB37: End of volume reached, and no secondary allocation quantity was specified in the JCL
SPACEparameter, or the system could not mount a new volume. - SD37: A secondary extent was requested, but the current DASD volume does not have a contiguous chunk of tracks/cylinders large enough to satisfy the minimum request, and no additional candidate volumes exist in the SMS Storage Group.
- SE37: The dataset reached the physical architectural limit of extents (16 extents on a single volume for basic PDS; 123 extents across all volumes for standard sequential datasets) or ran out of directory blocks (
D37on PDS directory).
3 Step-by-Step Diagnostic & Code Resolution
# 1. Optimize the JCL SPACE Allocation
Ensure secondary allocations and release unused space upon job completion:
//SYSUT2 DD DSN=PROD.BILLING.MONTHLY.EXTRACT,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(CYL,(150,50),RLSE),
// UNIT=SYSDA,
// DCB=(RECFM=FB,LRECL=250,BLKSIZE=27750)
- Primary:
150cylinders allocated immediately. - Secondary:
50cylinders allocated dynamically whenever the file expands. -
RLSE: Frees unwritten cylinders atCLOSE, preventing DASD wastage.
# 2. Bypass Extent Limits with SMS Extended Addressability (EA)
For multi-gigabyte or terabyte batch files, assign an SMS Data Class configured for Extended Format:
//SYSUT2 DD DSN=PROD.BILLING.MONTHLY.EXTRACT,
// DISP=(NEW,CATLG,DELETE),
// DATACLAS=DCEARGE,
// STORCLAS=SCBATCH,
// SPACE=(CYL,(500,100),RLSE)
Extended format datasets support up to 255 extents per volume and multi-volume spanning up to 59 volumes, completely eliminating the 123-extent barrier.
# 3. Recovering a PDS Out of Directory Blocks (SD37 / SE37)
If a partitioned dataset (PDS) fails due to exhausted directory blocks, expand it using IDCAMS:
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
ALTER PROD.COBOL.LOADLIB -
SPACE(50 20) -
DIRECTORY(150)
/*
Better yet, convert legacy PDS datasets to PDSE (DSNTYPE=LIBRARY), which features dynamic directory allocation and automatic member space reclamation without requiring periodic COMPRESS.
Diagnostic Reference Matrix
| Attribute | Specification |
|---|---|
| Target Subsystem | IBM z/OS 2.4 - 3.1 • ABENDS & Diagnostics |
| Error Signature | JCL, z/OS, DFSMS |
| Resolution SLA | < 15 Minutes via Verified StackMF Runbook |
| Technical Reviewer | Anshu, Chief Technology Architect • StackMF Architecture Pod |
Architectural Prevention & Performance Tuning Checklist
- Convert all legacy PDS libraries to PDSE (`DSNTYPE=LIBRARY`) to prevent directory block exhaustion and eliminate compress jobs.
- Establish SMS Storage Group monitoring thresholds at 80% DASD utilization to prevent volume full conditions.
- Always specify a realistic secondary allocation in batch JCL rather than relying solely on large primary extents.
- Utilize DFSMS Space Management automated pooling or third-party automated space recovery utilities.
? Frequently Asked Questions
What is the root cause of Mastering SB37, SD37, and SE37 Out-of-Space ABENDs in z/OS Sequential & PDS Datasets? ↓
How do you resolve Mastering SB37, SD37, and SE37 Out-of-Space ABENDs in z/OS Sequential & PDS Datasets in production? ↓
How can teams prevent Mastering SB37, SD37, and SE37 Out-of-Space ABENDs in z/OS Sequential & PDS Datasets 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
Diagnosing ABEND S0C1 (Operation Exception) in CICS & Batch Execution
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%.