IBM Mainframe Forum Index
 
Register
 
IBM Mainframe Forum Index Mainframe: Search Log in to check your private messages Log in
 

OPEN VSAM in I-O mode, return code 35


 
IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
abby.qiong.zhang

New User


Joined: 07 Jun 2012
Posts: 26
Location: China

PostPosted: Sat Jun 08, 2013 12:26 pm
Reply with quote

The VSAM file is empty, i used I-O mode to open it, but received return code as 35. As I know, 35 means the file doesn't exist, but it does exist only empty, is any one have any idea?

Here's my two VSAM datasets
Code:

NA39660.PERM.B00502D.VSAM       
NA39660.PERM.B00502D.VSAM.DATA 
NA39660.PERM.B00502D.VSAM.INDEX
NA39660.PERM.B00503D.VSAM       
NA39660.PERM.B00503D.VSAM.DATA 
NA39660.PERM.B00503D.VSAM.INDEX
Back to top
View user's profile Send private message
abby.qiong.zhang

New User


Joined: 07 Jun 2012
Posts: 26
Location: China

PostPosted: Sat Jun 08, 2013 1:13 pm
Reply with quote

Issue has been fixed, need to initialize the files, put in some test data.
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1789
Location: Bloomington, IL

PostPosted: Sat Jun 08, 2013 6:33 pm
Reply with quote

Good to see that you have solved it. Remember that for VSAM data sets, there is a difference between an "empty" data set (that has ever held data) and one with no records in it.
Back to top
View user's profile Send private message
Pete Wilson

Active User


Joined: 31 Dec 2009
Posts: 488
Location: London

PostPosted: Mon Jun 10, 2013 4:03 pm
Reply with quote

Do a search for VSAMINIT on the internet and you'll find a program to download that does initialises of VSAM files in different ways. For example it can insert and then delete a record in what was an empty VSAM file and this 'initialises' it so CICS can open it OK.
Back to top
View user's profile Send private message
Pete Wilson

Active User


Joined: 31 Dec 2009
Posts: 488
Location: London

PostPosted: Mon Jun 10, 2013 4:46 pm
Reply with quote

VSAMINIT source:
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8568
Location: Dubuque, Iowa, USA

PostPosted: Mon Jun 10, 2013 6:02 pm
Reply with quote

The file status 35 does NOT mean "the file doesn't exist" -- from the Enterprise COBOL Language Reference manual:
Quote:
An OPEN statement with the INPUT, I-O, or EXTEND phrase was attempted on
a nonoptional file that was not present.
What the 35 tells you is that a required file does not have a DD statement present in the JCL. Possible reasons for this include:
1. file does not exist (although this usually generates a JCL error)
2. DD name in JCL is different from DD name in COBOL
3. opening a never-used VSAM file in INPUT or I-O mode
4. attempting to open a VSAM file defined with an alternate index specified with UPGRADE, but not having a DD statement for the alternate index path
5. DD name is missing in the JCL
etc
etc
etc
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic All times are GMT + 6 Hours
Forum Index -> JCL & VSAM
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Forum Replies
No new posts JCL for replacing code in Cobol JCL & VSAM 8
No new posts IGZ0035S THERE WAS AN UNSUCCESSFUL OP... COBOL Programming 3
No new posts Easytrieve EZABX007 with error code 0... CA Products 7
No new posts VSAM Alter Command - Cylinder Extent ... JCL & VSAM 3
No new posts RPLDDDD field for extended VSAM - ESDS JCL & VSAM 0

Back to Top