|
View previous topic :: View next topic
|
| Author |
Message |
abby.qiong.zhang
New User
Joined: 07 Jun 2012
Posts: 26
Location: China
|
|
|
|
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 |
|
 |
abby.qiong.zhang
New User
Joined: 07 Jun 2012
Posts: 26
Location: China
|
|
|
|
| Issue has been fixed, need to initialize the files, put in some test data. |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| 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 |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 580
Location: London
|
|
|
|
| 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 |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 580
Location: London
|
|
|
|
| VSAMINIT source: |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
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 |
|
|
|
|
