Troubleshooting VSAM File Status 35: Dataset Not Found during Dynamic Allocation in Batch & CICS
Quick Diagnostic Summary: What Causes Troubleshooting VSAM File Status 35: Dataset Not Found during Dynamic Allocation in Batch & CICS?
VSAM File Status 35 indicates that an OPEN statement failed because the designated physical dataset does not exist or was not found in the master/user catalog. Learn how to verify catalog pointers, fix dynamic allocation parameters, and handle optional files.
1 Incident Symptoms: What Triggers Troubleshooting VSAM File Status 35: Dataset Not Found during Dynamic Allocation in Batch & CICS?
A daily batch reporting job abends on statement 102:
PROG01: OPEN ERROR FOR FILE 'CUSTVSAM'
FILE STATUS = 35
CEE3250C The system or user abend U4038 was issued.
The developer insists the DD card exists in the JCL, yet the job refuses to run.
2 Technical Root Cause & Architecture Mechanics
In COBOL execution:
- File Status 35 (File Not Found):
1. The dataset specified on the JCL DD card does not exist in the z/OS catalog.
2. The file is defined as SELECT ... ASSIGN TO CUSTDD but no //CUSTDD DD card was provided in the JCL step.
3. In CICS, the file is defined in the CSD with a DSNAME that was deleted or renamed.
3 Step-by-Step Diagnostic & Code Resolution
# 1. Verify Dataset Existence via IDCAMS LISTCAT
In ISPF or via batch JCL:
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
LISTCAT ENT('PROD.KSDS.CUSTOMER')
/*
If output returns IDC3012I ENTRY NOT FOUND, the dataset was purged or un-cataloged.
# 2. Handle Optional Datasets in COBOL Syntax
If a file may or may not exist on any given run, declare it as OPTIONAL:
SELECT OPTIONAL CUSTVSAM
ASSIGN TO CUSTDD
ORGANIZATION IS INDEXED
ACCESS MODE IS RANDOM
RECORD KEY IS CUST-KEY
FILE STATUS IS WS-CUST-STATUS.
When an OPTIONAL file does not exist:
-
OPEN INPUTsucceeds withFILE STATUS = '05'instead of crashing with35! - The first
READreturnsAT END(FILE STATUS = '10').
# 3. Verify CICS File Resource Definition
In CICS:
CEMT INQUIRE FILE(CUSTFIL)
If STATUS: UNENABLED, check DSNAME. Re-point to the correct physical dataset using CEDA ALTER FILE(CUSTFIL) DSNAME(...) and reinstall.
Diagnostic Reference Matrix
| Attribute | Specification |
|---|---|
| Target Subsystem | IBM z/OS 2.4 - 3.1 • CICS & VSAM Architecture |
| Error Signature | VSAM, File Status 35, COBOL |
| Resolution SLA | < 15 Minutes via Verified StackMF Runbook |
| Technical Reviewer | Anshu, Chief Technology Architect • StackMF Architecture Pod |
Architectural Prevention & Performance Tuning Checklist
- Use `SELECT OPTIONAL` for conditional batch reconciliation and delta files.
- Verify automated dataset creation steps execute prior to dependent consumer steps.
- Check user catalog aliases (`IDCAMS DEFINE ALIAS`) to ensure HLQs route to correct catalogs.
? Frequently Asked Questions
What is the root cause of Troubleshooting VSAM File Status 35: Dataset Not Found during Dynamic Allocation in Batch & CICS? ↓
How do you resolve Troubleshooting VSAM File Status 35: Dataset Not Found during Dynamic Allocation in Batch & CICS in production? ↓
How can teams prevent Troubleshooting VSAM File Status 35: Dataset Not Found during Dynamic Allocation in Batch & CICS in enterprise pipelines? ↓
Recommended Technical Runbooks
Diagnosing VSAM File Status 92 and 93: Enqueue Locks & Dynamic Allocation Contention
Eliminating Performance Degradation from VSAM KSDS CI/CA Splits: IDCAMS REORG Automation
Implementing VSAM Record-Level Sharing (RLS) for Concurrent Batch and CICS Access
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%.