File status code 34 while reading a VSAM.

Virtual Storage Access method - ESDS, KSDS, RRDS & LDS. Basic direct access method, Basic sequential -, Queued sequential -, Basic partitioned -, Indexed sequential -, Object - access method.
Previous topicNext topic

Topic Author
Pragya
Registered Member
Posts: 28
Joined: Wed Jun 19, 2013 9:49 am
Zodiac: Sagittarius

File status code 34 while reading a VSAM.

Post by Pragya » Tue Oct 24, 2017 8:27 am

Hi,

While reading a VSAM file sequentially, I am getting a file ststus code 34. In this I need to read the file sequentially and
write records in an output sequential file.

As a remedy I have also increased the space for the output file but I stil get the abend, could please someone help.




nicc
Global Moderator
Global Moderator
Posts: 580
Joined: Wed Apr 23, 2014 8:45 pm

Re: File status code 34 while reading a VSAM.

Post by nicc » Tue Oct 24, 2017 3:40 pm

Why did you increase the space for the output data set (not "file")? Was that one of the recommendations from the manual? You did read the manual, didn't you? Probably not, so read up on what a status code of 34 is, and, being a VSAM data set, what the secondary status code is.


Regards
Nic

User avatar

Robert Sample
Global Moderator
Global Moderator
Posts: 1331
Joined: Fri Jun 28, 2013 1:22 am
Location: Dubuque Iowa
Zodiac: Virgo

Re: File status code 34 while reading a VSAM.

Post by Robert Sample » Tue Oct 24, 2017 5:17 pm

You left out a few CRITICAL pieces of information in your post:

Are you getting the file status 34 on the input VSAM data set or the output sequential data set?
How many records in the VSAM data set?
How many of those records are you wanting to copy to the output data set?
If the data set is being created by your job, what is the DD definition for the data set?
If the data set already exists, what are the attributes of the data set?
How many records do you process before getting the file status 34?



Previous topicNext topic

Return to “SMS & VSAM and BDAM, BSAM, QSAM, BPAM, ISAM, OAM.”