Friday, January 29, 2010

Cobol File status codes

File Status

Result

Explanation

2

VALID DUPLICATE ALTERNATE KEY DETECTED.

N/A

5

ATTEMPT TO OPEN A FILE THAT IS NOT AVAILABLE.

N/A

7

INCONSISTENCY IN STORAGE DEVICE.

N/A

10

END OF FILE REACHED

A sequential READ statement was attempted and no next logical record existed in the file because the end of the file had been reached, or the first READ was attempted on an optional input file that was not present.

14

INVALID READ ATTEMPT ON RELATIVE FILE. THE GIVEN RRN NUMBER IS LARGER THAN THE RELATIVE KEY.

A sequential READ statement was attempted for a relative file and the number of significant digits in the relative record number was larger than the size of the relative key data item described for the file.

16

A READ WAS ATTEMPTED WHEN AT THE END CONDITION IS TRUE.

N/A

20

INVALID KEY.

N/A

21

RECORD OUT OF SEQUENCE

A sequence error exists for a sequentially accessed indexed file. The prime record key value has been changed by the program between the successful execution of a READ statement and the execution of the next REWRITE statement for that file, or the ascending requirements for successive record key values were violated.

22

DUPLICATE KEY

An attempt was made to write a record that would create a duplicate key in a relative file; or an attempt was made to write or rewrite a record that would create a duplicate prime record key or a duplicate alternate record key without the DUPLICATES phrase in an indexed file. This key value applies to an indexed file in which the alternate key has been declared 'UNIQUE'.

23

RECORD NOT FOUND

An attempt was made to randomly access a record that does not exist in the file, or a START or random READ statement was attempted on an optional input file that was not present.

24

NO MORE SPACE ALLOCATED TO FILE. WRITING BEYOND THE ALLOCATION OF THE FILE.

An attempt was made to write beyond the externally defined boundaries of a relative or indexed file. Or, a sequential WRITE statement was attempted for a relative file and the number of significant digits in the relative record number was larger than the size of the relative key data item described for the file.

30

UNCORRECTABLE I/O ERROR.

No further information

34

AN ATTEMPT WAS MADE TO WRITE BEYOND THE BOUNDARY OF THE FILE.

A permanent error exists because of a boundary violation; an attempt was made to write beyond the externally-defined boundaries of a sequential file.

35

ATEEMPTING TO OPEN AN EMPTY FILE IN INPUT OR I/O MODE. DD NAME IS MISSING OR WRONGLY GIVEN.

An OPEN statement with the INPUT, I-O, or EXTEND phrase was attempted on a non-optional file that was not present.

37

OPEN WAS ATTEMPTED ON A FILE THAT WILL NOT SUPPORT THE OPEN MODE SPECIFIED.

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.

37

ATTEMPT TO OPEN A FILE THAT HAS BEEN CLOSED WITH LOCK

An OPEN statement was attempted on a file previously closed with lock.

39

ERROR DURING OPENING.INCONSISTENCY BETWEEN FILE DESC AND ACTUAL FILE

The OPEN statement was unsuccessful because a conflict was detected between the fixed file attributes and the attributes specified for that file in the program. These attributes include the organization of the file (sequential, relative, or indexed), the prime record key, the alternate record keys, the code set, the maximum record size, and the record type (fixed or variable).

40

RECORD IS INCONSISTENT WITH THE DESCRIPTION OF THE RECORD THAT HAS BEEN READ

N/A

41

ATTEMPT TO OPEN A FILE WHICH IS ALREADY OPENED

An OPEN statement was attempted for a file in the open mode.

42

ATTEMPT TO CLOSE A FILE THAT IS NOT OPEN.

A CLOSE statement was attempted for a file not in the open mode.

43

A READ DID NOT PRECEDE EXECUTION OF CURRENT REWRITE COMMAND.

For a mass storage file in the sequential access mode, the last input-output statement executed for the associated file prior to the execution of a REWRITE statement was not a successfully executed READ statement. For relative and indexed files in the sequential access mode, the last input-output statement executed for the file prior to the execution of a DELETE or REWRITE statement was not a successfully executed READ statement.

44

A BOUNADRY VIOLATION DUE TO ATTEMPT TO WRITE A RECORD OF IMPROPER LENGTH.

A boundary violation exists because an attempt was made to rewrite a record to a file and the record was not the same size as the record being replaced, or an attempt was made to write or rewrite a record that was larger than the largest or smaller than the smallest record allowed by the RECORD IS VARYING clause of the associated file-name.

46

ATTEMPT TO READ THE NEXT NONEXISTENT RECORD.

A sequential READ statement was attempted on a file open in the input or I-O mode and no valid next record had been established because:
1. The preceding START statement was unsuccessful,
or 2.The preceding READ statement was unsuccessful but did not cause an at end condition,
or 3. The preceding READ statement caused an at end condition.

47

ATTEMPT TO READ FROM A FILE WHICH IS NOT OPEN IN INPUT OR I-O MODE.

The execution of a READ statement was attempted on a file not open in the input or I-O mode.

48

ATTEMPT TO WRITE ON A FILE NOT OPEN IN OUTPUT OR EXTEND MODE.

The execution of a WRITE statement was attempted on a file not open in the I-O, output, or extend mode.

49

ATTEMPT TO WRITE ON A FILE NOT OPEN IN I-O MODE.

The execution of a DELETE or REWRITE statement was attempted on a file not open in the I-O mode.

88

VSAM START FAILURE.

N/A

90

SOME TYPE OF VSAM LOGIC ERROR.

No further information.

91

PASSWORD FAILURE.

For VSAM only: Password failure.

92

DOING IN WRONG MODE.

Logic error.

93

NOT ENOUGH VIRTUAL STORAGE FOR VSAM TASK.

Resource not available.

94

NO CURRENT POINTER FOR SEQUENTIAL PROCESSING.

For VSAM with CMPR2 compiler-option only:No file position indicator for sequential request.

95

CONFLICTING ATTRIBUTES.

For VSAM only: Invalid or incomplete file information.

96

NO CORRESPONDING DD STATEMENT FOR THE FILE.

For VSAM only: No DD statement specified for this file.

97

FILE NOT CLOSED BY PREVIOUS JOB.

For VSAM only: OPEN statement execution successful: File integrity verified.

No comments: