7/29/2019 File Status

1/3

FILE STATUS CODES

FileStatus

Result Explanation

2

VALID DUPLICATE ALTERNATE KEY

DETECTED.

N/A

5

ATTEMPT TO OPEN A FILE THAT ISNOT AVAILABLE.

N/A

7

INCONSISTENCY IN STORAGEDEVICE.

N/A

10END OF FILE REACHED

A sequential READ statement was attempted andno next logical record existed in the file becausethe end of the file had been reached, or the firstREAD was attempted on an optional input file thatwas not present.

14

INVALID READ ATTEMPT ON

RELATIVE FILE. THE GIVEN RRNNUMBER IS LARGER THAN THERELATIVE KEY.

A sequential READ statement was attempted for a

relative file and the number of significant digits inthe relative record number was larger than thesize of the relative key data item described for thefile.

16

A READ WAS ATTEMPTED WHEN ATTHE END CONDITION IS TRUE.

N/A

20INVALID KEY. N/A

21

RECORD OUT OF SEQUENCE

A sequence error exists for a sequentiallyaccessed indexed file. The prime record key valuehas been changed by the program between thesuccessful execution of a READ statement and

the execution of the next REWRITE statement forthat file, or the ascending requirements forsuccessive record key values were violated.

22DUPLICATE KEY

An attempt was made to write a record that wouldcreate a duplicate key in a relative file; or anattempt was made to write or rewrite a record thatwould create a duplicate prime record key or aduplicate alternate record key without theDUPLICATES phrase in an indexed file. This keyvalue applies to an indexed file in which thealternate 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 STARTor random READ statement was attempted on anoptional input file that was not present.

24

NO MORE SPACE ALLOCATED TOFILE. WRITING BEYOND THE

ALLOCATION OF THE FILE.

An attempt was made to write beyond theexternally defined boundaries of a relative orindexed file. Or, a sequential WRITE statementwas attempted for a relative file and the number ofsignificant digits in the relative record number waslarger than the size of the relative key data item

7/29/2019 File Status

2/3

described for the file.

30UNCORRECTABLE I/O ERROR. No further information

34

AN ATTEMPT WAS MADE TO WRITEBEYOND THE BOUNDARY OF THEFILE.

A permanent error exists because of a boundaryviolation; an attempt was made to write beyond

the externally-defined boundaries of a sequentialfile.

35

ATEEMPTING TO OPEN AN EMPTYFILE IN INPUT OR I/O MODE. DDNAME IS MISSING OR WRONGLYGIVEN.

An OPEN statement with the INPUT, I-O, orEXTEND phrase was attempted on a non-optionalfile that was not present.

37

OPEN WAS ATTEMPTED ON A FILETHAT WILL NOT SUPPORT THEOPEN MODE SPECIFIED.

An OPEN statement was attempted on a file thatwould not support the open mode specified in theOPEN statement. Possible violations are:1. The EXTEND or OUTPUT phrase was specifiedbut the file would not support write operations.2. The I-O phrase was specified but the file wouldnot support the input and output operationspermitted.3. The INPUT phrase was specified but the filewould not support read operations.

37

ATTEMPT TO OPEN A FILE THATHAS BEEN CLOSED WITH LOCK

An OPEN statement was attempted on a filepreviously closed with lock.

39

ERROR DURINGOPENING.INCONSISTENCYBETWEEN FILE DESC AND ACTUALFILE

The OPEN statement was unsuccessful becausea conflict was detected between the fixed fileattributes and the attributes specified for that file inthe program. These attributes include theorganization of the file (sequential, relative, orindexed), the prime record key, the alternaterecord keys, the code set, the maximum record

size, and the record type (fixed or variable).

40

RECORD IS INCONSISTENT WITHTHE DESCRIPTION OF THERECORD THAT HAS BEEN READ

N/A

41

ATTEMPT TO OPEN A FILE WHICHIS ALREADY OPENED

An OPEN statement was attempted for a file in theopen mode.

42

ATTEMPT TO CLOSE A FILE THAT ISNOT OPEN.

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

43

A READ DID NOT PRECEDEEXECUTION OF CURRENTREWRITE COMMAND.

For a mass storage file in the sequential accessmode, the last input-output statement executed forthe associated file prior to the execution of a

REWRITE statement was not a successfullyexecuted READ statement. For relative andindexed files in the sequential access mode, thelast input-output statement executed for the fileprior to the execution of a DELETE or REWRITEstatement was not a successfully executed READstatement.

44

A BOUNADRY VIOLATION DUE TOATTEMPT TO WRITE A RECORD OF

A boundary violation exists because an attemptwas made to rewrite a record to a file and the

7/29/2019 File Status

3/3

IMPROPER LENGTH.

record was not the same size as the record beingreplaced, or an attempt was made to write orrewrite a record that was larger than the largest orsmaller than the smallest record allowed by theRECORD IS VARYING clause of the associatedfile-name.

46

ATTEMPT TO READ THE NEXTNONEXISTENT RECORD.

A sequential READ statement was attempted on afile open in the input or I-O mode and no valid nextrecord had been established because:1. The preceding START statement wasunsuccessful,or 2.The preceding READ statement wasunsuccessful but did not cause an at endcondition,or 3. The preceding READ statement caused an atend condition.

47

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

The execution of a READ statement wasattempted on a file not open in the input or I-Omode.

48

ATTEMPT TO WRITE ON A FILE NOTOPEN IN OUTPUT OR EXTENDMODE.

The execution of a WRITE statement wasattempted on a file not open in the I-O, output, orextend mode.

49

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

The execution of a DELETE or REWRITEstatement was attempted on a file not open in theI-O mode.

88VSAM START FAILURE. N/A

90

SOME TYPE OF VSAM LOGICERROR.

No further information.

91PASSWORD FAILURE. For VSAM only: Password failure.

92DOING IN WRONG MODE. Logic error.

93

NOT ENOUGH VIRTUAL STORAGEFOR VSAM TASK.

Resource not available.

94

NO CURRENT POINTER FORSEQUENTIAL PROCESSING.

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

95CONFLICTING ATTRIBUTES.

For VSAM only: Invalid or incomplete fileinformation.

96 NO CORRESPONDING DDSTATEMENT FOR THE FILE. For VSAM only: No DD statement specified for thisfile.

97

FILE NOT CLOSED BY PREVIOUSJOB.

For VSAM only: OPEN statement executionsuccessful: File integrity verified