file status 35 in COBOL

OS/VS COBOL, COBOL II, Enterprise COBOL for z/OS. OpenCOBOL and OOCobol.
Post Reply
Jagjeet Dayal
Registered Member
Posts: 20
Joined: Sun Feb 28, 2016 8:28 am
Afghanistan

file status 35 in COBOL

Post by Jagjeet Dayal »

Anyone has idea on file status 35. I checked ddname and filename it's correct.
User avatar
zum13
Registered Member
Posts: 85
Joined: Thu May 04, 2023 12:58 am

Re: file status 35 in COBOL

Post by zum13 »

For a VSAM file, this error can occur if the file is empty. If that's the case, then you need to load a dummy record into the file. This can be done programatically or you can use the REPRO statement under IDCAMS to get the record in there.
User avatar
ThorBap
New Member
Posts: 1
Joined: Fri Feb 23, 2024 4:55 pm

Re: file status 35 in COBOL

Post by ThorBap »

Have you considered the possibility that the file might be empty, especially if it's a VSAM file, and have you tried loading a dummy record into it?
:)
Post Reply

Create an account or sign in to join the discussion

You need to be a member in order to post a reply

Create an account

Not a member? register to join our community
Members can start their own topics & subscribe to topics
It’s free and only takes a minute

Register

Sign in

Return to “IBM COBOL, GnuCOBOL (OpenCOBOL), OOCobol.”