File open error 37 for a KSDS VSAM file in OUTPUT mode

karthick Raja · New User Joined: 10 Aug 2006 Posts: 8

Hi,

When i tried to open a KSDS VSAM file in OUTPUT mode i am getting file open error of 37. the DISP i gave in JCL is OLD and even tried with SHR.
I have given the access mode as DYNAMIC.

This is the piece of code i used for SELECT
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
RECORD KEY IS OUT-ID
----------
----------
PROCEDURE DIVISION.
START-PARA.
DISPLAY 'STARTED'.
OPEN OUTPUT OUTPUT-FILE.

This open statement is causing the error. I have tried with both empty file & with some data. Can any one help me on this.

Thanks in Advance.

cobolunni · Posted: Thu Dec 07, 2006 5:49 pm

file status 37 occurs because of

An OPEN statement was attempted on a file that would not support the open mode specified in the OPEN statement. Possible violations are:
1. The EXTEND or OUTPUT phrase was specified but the file would not support write operations.
2. The I-O phrase was specified but the file would not support the input and output operations permitted.
3. The INPUT phrase was specified but the file would not support read operations.
4. Under VSE, the EXTEND phrase was specified for a SAM file.

note: taken from www.simotime.com/vsmfsk01.htm

karthick Raja · New User Joined: 10 Aug 2006 Posts: 8

Hi,

Thanks for the reply. But i dont know the reason why i am getting that return code. I suppose the code has work fine.
I didnt find any error in the code.
please correct me if i am wrong.

muthuvel · Posted: Thu Dec 07, 2006 7:22 pm

karthick,
If my guess is correct,you might have created the VSAM file and initialized it previously before the program..
Hence if you want to write data into it ,then you should open the file in
I-O mode..

Regards,
Muhuvel.

karthick Raja · New User Joined: 10 Aug 2006 Posts: 8

Hi Muthuvel,

i dont get your explanation. Can you breif me on that please. What do you mean by the file is initialised?
But you are correct. The things are fine when it is opened in I-O mode.
i have checked it previously.
Thanks for your reply.

Arun Raj · Posted: Fri Dec 08, 2006 11:50 am

Hi Karthick

Try dropping and recreating the VSAM file.It will be of more help if you can provide us with your VSAM file definition.

Thanks
Arun

hiravibk · Active User Joined: 14 Dec 2008 Posts: 107 Location: India

dick scherrer · Posted: Fri Nov 27, 2009 10:48 am

Hello,

Please note that you have posted a reply that has been inactive for almost 3 years. . .

Dropping and re-creating the file can remove any internal inconsistency or corruption. Dropping and re-creating the file also removes any chance of determining what was currently wrong with the file.

Anuj Dhawan · Posted: Fri Nov 27, 2009 4:28 pm

Pardon my ignorance (if it is) but does "dropping" really a correct term here in relation with VSAMs? VSAMs are used with DELETE/DEFINEd... one can DROP a table not file...

dbzTHEdinosauer · Posted: Fri Nov 27, 2009 6:39 pm

Anuj,

being a little picky aren't you?

people say
JCL when they should say JOB or STEP.
PROC when they should say REXX Script.
DROP when they should say delete.

this is more of a chat room than a technical forum.
my guess that a lot of people post here, because their technical co-workers
have had enough of the illiteracy.

Anuj Dhawan · Posted: Fri Nov 27, 2009 8:27 pm

Dick,

Yes actually...

First, I started my response with "Being little picky" instead of