COBOL File Status Code - 39

jz1b0c · Posted: Sat Aug 25, 2007 2:19 am

In the JCL I have LRECL=360. and in the program I have 01 FD-outrec pic x(360)

this program gives an error while opening the file.

File status 39.

IGZ0201W A file attribute mismatch was detected. File XXXXFILE in program XXXXX01 had a record length of 361 and the file specified in the ASSIGN clause had a record length of 360.

Where is that 361 coming from?

Here is the program:

SELECT XXXXFILE ASSIGN TO DD2
ORGANIZATION IS SEQUENTIAL
FILE STATUS IS WS-OUTPUT-STAT.

FD XXXXFILE.
01 FD-OUTREC PIC X(360).

JCL:

//*
//DD2 DD DSN=PX01211.XXXXFILE.OUTPUT,
// DISP=(NEW,CATLG,DELETE),
// DCB=(SRCDSCB,RECFM=FB,LRECL=360),
// SPACE=(360,(100,80),RLSE),AVGREC=K
//*

CICS Guy · Posted: Sat Aug 25, 2007 3:13 am

FBA?
Ignore the JCL, look at the actual file...
Or what do your writes look like?

dbzTHEdinosauer · Posted: Sat Aug 25, 2007 4:27 am

CICS Guy,
I don't think he can tell you what his writes look like. He never gets it open.

but, the ops-sys is interpreting his dd statement as an allocation for a 361 byte lrecl. so, it is either SRCDSCB - overrides any lrecl? or AVGREC=K

sachin_star3 · New User Joined: 30 Sep 2006 Posts: 78 Location: pune

The reason of this error genrerally when record legnth of logical records
and file is mismatch

In your case as per my assumption

you try to write the record in the opt file having record length

is 360 so there are following p0ssibilities to arise the 39 file-status:

1.you try ro write the input record having legnth (either <360 or >360)
different from output record first see the input or what are try to write check this
first

2.you check the file legth and there record structure you trying to write

---sachin borase

CICS Guy · Posted: Sat Aug 25, 2007 3:15 pm

shankar.v · Posted: Sat Aug 25, 2007 4:16 pm

jz1b0c,

Are you using WRITE ... AFTER/BEFORE ADVANCING PAGE/nLINES in program. If yes, then the compiler may add one byte to length of the field description. In your case 360+1=361.

dbzTHEdinosauer · Posted: Sat Aug 25, 2007 5:52 pm

shankar.v,

excellent point. I have misinterpreted the error message. After looking it up I image your suggestion may be accurate, since it does not seem to be a variable length record.

so, the dd statement should be RECFM=FBA,LRECL=361 ?

dbzTHEdinosauer · Posted: Sat Aug 25, 2007 5:54 pm

CICS Guy,

my appologies, you were also on the right track.

CICS Guy · Posted: Sat Aug 25, 2007 6:12 pm

Dick,

I was thinking that but I just couldn't see why anybody would specify carriage control on a 360 byte line.....

Bill

dbzTHEdinosauer · Posted: Sat Aug 25, 2007 6:49 pm

People use commands like WRITE AFTER without looking up what it means.

CICS Guy · Posted: Sat Aug 25, 2007 7:00 pm

Just what I was thinking.....

jz1b0c · Posted: Mon Aug 27, 2007 7:46 pm

shankar.v

you are right. There was after advance in that program.
Thanks everyone..

sgaid21 · New User Joined: 12 Sep 2006 Posts: 16 Location: Canada

If you still get the mismatch record length, then try to add "Record contains 360 characters" that should solve it.