What is the file reason for file status 39?

File status 39 means “A conflict has been detected between the fixed file attributes and the attributes specified for the file in the program. This is usually caused by a conflict with record-length, key-length, key-position or file organization.”

How do I fix an open VSAM file error?

VSAM OPEN Error Resolution and Check in the Program Attributes for file organization (sequential, relative, or indexed) Prime record key. Alternate record keys.

How do I check my VSAM file status?

VSAM file status code indicates the status of the operation….VSAM File Status.

What is file status 46 Cobol?

If a second sequential read is unsuccessful, a file status of 46 occurs and the AT END phrase is not executed.” When an AT END condition occurs, the READ is considered unsuccessful. This causes unpredictable results. The cause is the record contents returned to the program are UNDEFINED.

What is the use of file status in COBOL?

File status is a data item which you define in your program. Defining a file status data item is optional. If a file status data item is not declared and a file error occurs, the COBOL run-time system displays an error message and aborts your program.

What is file status code 46 in COBOL?

What does COBOL file status 49 indicate?

A WRITE operation has been tried on a file not opened in the OUTPUT, I-O, or EXTEND mode, or on a file open I-O in the sequential access mode. 49. A DELETE or REWRITE operation has been tried on a file that is not opened I-O. 91.

Is VSAM Status Code 39 on open compatible or incompatible?

> Sheldon. VSAM status code 39 on Open? incompatible. Some of the conflicts which return this status code are: opened as KSDS. description (FD) area do not match the actual file attributes.

What is the COBOL open file status code for 9?

Cobol Open File Status Code 39 If status-key-1 is equal to 9 then status-key-2 is a one byte, binary value as defined in the following table. Cobol Open File Status Code 35 END-RTN.

What does EOF 39 Mean in COBOL?

File Status 39 In Cobol Program A sequential READ statement was attempted and no next logical record existed in the file because the end of file (EOF) had been reached, or the first READ was attempted on RT017 Record error: probably zero length. Perhaps not even with READ or WRITE. PERFORM HEADING-RTN.

What is the meaning of a 39 error in a file?

File status 39 means “A conflict has been detected between the fixed file attributes and the attributes specified for the file in the program. This is usually caused by a conflict with record-length, key-length, key-position or file organization.” , IT Consultant, go player, family man, lover of life.