IBM Mainframe Forum

Hi,

I am getting below error message while opening VSAM file and the status code is 35.

DD=GLCONTF1 OPEN ERROR - FILE DEFINED BUT NOT LOADED

The file is there in the system. It ran fine when we restart the JOB.

Please advise.

Hi,

File Status : 35
Reason : Ateempting to open an empty file in INPUT or I/O mode. DD is missing or TEEMPTING TO OPEN AN EMPTY FILE IN INPUT OR I/O MODE. DD NAME is missing or wrongly given.
Desc: An OPEN statement with the INPUT, I-O, or EXTEND phrase was attempted on a non-optional file that was not present.

Thanks,
Chandu

VSAM distinguishes between an empty file (one that has been defined but never had a record in it) and a file with no records. An empty VSAM file cannot be opened for input or I-O in a COBOL program (nor anything else). Once the file has been opened for output, typically the file can be opened for input or I-O.

Hi,

The file used to delete and copy the content from the other file -- This process happening in program called X.

The ABEND JOB name is Y. We have not set the predecessor X for the JOB Y.

There is a possibility for the ABEND if both X and Y running at same time but this is also not happened. The JOB Y ran at 2100 hrs and JOB X ran at 2330hrs. so the file with content should be there for JOB Y.

That is why i posted the issue.

fornanthakumar wrote:The JOB Y ran at 2100 hrs and JOB X ran at 2330hrs. so the file with content should be there for JOB Y.

How do you get time to run in reverse in your shop?

So the file is defined, the job that loads data into the VSAM file ran 2 1/2 hours AFTER the job that got the file status 35, and you're questioning what happened? Let me rephrase my previous post so you can understand. At the time job Y runs, any VSAM data set being opened for INPUT or I-O in a COBOL program must have had data placed in it (whether or not that data was later deleted) -- otherwise you will get a 35 file status code. Based upon your post, what happened is both normal and expected behavior.