Standard File Status Codes

The Standard file status codes are listed here alphabetically, you may search for the one you want using your broswer, go down to the following selection list and click on the status code link to transfer directly to the message.

If a file status has multiple meanings depending on the compiler or subsystem which is setting the status, then multiple entries are listed. Entries which only apply to a particular subsystem are marked as such and the subsystem in highlighted. Some of the reasons for the file status are not those recorded in manuals but reasons which have been found from experience to cause that particular file status to be set.

CA YH 00 02 04 05 07 10 13 14 15 21 22 23 24 25 30 31 32 34 35 37 38 39 41 42 43 44 46 47 48 49 71 72 73 9A 9B 9C 9D 9I 9L 9S 90 91 92 93 94 95 96 97 98 99
YH
PDS011 Call refused, tells caller to handle the call.
00
Successful
02
A duplicate key exist for at least one alternate key for which duplicates are allowed.

The input-output statement was successfully executed, but a duplicate key was detected. For a READ statement the key value for the current key of reference was equal to the value of the same key in the next record within the current key of reference. for a REWRITE or WRITE statement, the record just written created a duplicate key value for at least one alternate record key for which duplicates are allowed

CICSIO DUPKEY

04
A READ statement was successfully executed, but the length of the record being processed did not conform to the fixed file attributes for that file.
05
An OPEN statement is successfully executed but the referenced optional file is not present at the time the OPEN statement is executed. The file has been created if the open mode is I-O or EXTEND. This does not apply to VSAM sequential files.
07
For a CLOSE statement with the NO REWIND, REEL/UNIT, or FOR REMOVAL phrase or for an OPEN statement with the NO REWIND phrase, the referenced file was on a non-reel/unit medium.
10
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 an optional input file that was not present.

CICSIO ENDFILE

13
VAXVMS No next logical record (at end).
14
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.
15
A sequential READ statement is attempted for the first time on an optional file that is not present. The new I-O status value of 15 distinguishes the absence of an optional file from other AT END conditions.
21
A sequence error exists for a sequentially accessed indexed file. The prime record key value has been changed by the program between the sucessful 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. That is,a sequence error occurred for sequentially accessed KSDS.
22
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.

CICSIO DUPREC

23
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.

CICSIO NOTFOUND

24
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.

Realia & Microsoft Disk full.

CICSIO NOSPACE

25
Indicates that a START statement or a random READ statement has been attempted on an OPTIONAL file that is not present.
30
An I-O error occured.

Microsoft File not found.

CICSIO IOERR See next two bytes in EIBRCODE for the VSAM return and error code.

31
PDS011 BLDL failed for a PDS member.
32
PDS011 STOW for a member failed.
34
A permanent error exists because of a boundary violation; an attempt was made to write beyound the externally-defined boundaries of a sequential file. Same as 24 only for ESDS.

Realia & Microsoft Disk full.

35
An OPEN statement with the INPUT, I-O, or EXTEND phrase was attempted on a non-optional file that was not present.
37
An OPEN statement was attempted on a file that would not support the open mode specified in the OPEN statement. Possible violations are:
  • The EXTEND or OUTPUT phrase was specified but the file would not support write operations.
  • The I-O phrase was specified but the file would support the input and output operations.
  • The INPUT phrase was specified but the file would not support read operations.
    • 38
    An OPEN statement was attempted on a file previously closed with lock.
    39
    The OPEN statement was unsuccesful 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, the record type (fixed or variable), and the blocking factor.
    41
    An OPEN statement was attempted for a file in the open mode.
    42
    A CLOSE statement was attempted for a file not in the open mode.
    43
    For a mass storage file in the sequential access mode, the last input-output statement executed for the asociated 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 boundary violation exists because an attempt was made to rewrite a record to a file and 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
    A sequential READ statement was attempted on a file open in the input or I-O mode and no valid next record has been established because:
  • The preceding READ statement was unsuccessful but did not cause an at end condition
  • The preceding READ statement caused an at end condition.
    • 47
    The execution of a READ or START statement was attempted on a file not open in the input or I-O mode.
    48
    The execution of a WRITE statement was attempted on a file not open in the I-O, output, or extend mode.
    49
    The execution of a DELETE or REWRITE statement was attempted on a file not open in the I-O Mode.
    71
    PDS011 Parameter list specified neither Input or Output.
    72
    PDS011 Blocksize was not positive after open.
    73
    PDS011 Record size too big to be handled.
    9A
    Realia Successful OPEN of a shared file. No logging will be done.

    Micro Focus Locked file - another program has already accessed the file to the exclusion of other programs.

    9B
    Realia Reserved. This file status value is returned upon successful completion of an OPEN of a file setup for file sharing (via a LOCK MODE clause in that file's SELECT statement). Programs requiring shared file access should insure that the expected 9x status occurs: a '00' status would indicate a successful open but that the file is not shareable. Plans for future improvements to the Realia file system include changes to log updates to allow for roll-forward/roll-backward recovery. File status '9B' and '9C' will be enabled in future versions when logging of updates is implemented.
    9C
    Realia Reserved. This file status value is returned upon successful completion of an OPEN of a file setup for file sharing (via a LOCK MODE clause in that file's SELECT statement). Programs requiring shared file access should insure that the expected 9x status occurs: a '00' status would indicate a successful open but that the file is not shareable. Plans for future improvements to the Realia file system include changes to log updates to allow for roll-forward/roll-backward recovery. File status '9B' and '9C' will be enabled in future versions when logging of updates is implemented.
    9D
    Micro Focus Locked record - another program has already accessed the record.
    9I
    Realia Improper operation on a logged file. Plans for future improvements to the Realia file system include changes to log updates to allow for roll-forward/roll-backward recovery. To assure that systems written today do not interfere with these intended features, version 4.00 of the file system does not allow operations against files whick look as if they are being logged. No Realia utilities currently mark any Realia file as being logged, so this status can only occur when accessing a file in byte-stream mode which happens to begin with the intended signature for logged files: an upper-case letter followed by an EOF mark (X'1A').
    9L
    Realia Returned when a user attempts to access a file locked by another user (does not allow multiple concurrent OPEN/CLOSE). DOS retries a locking attempt if it finds that another node is holding the lock. However after a fixed number of retry attempts, it abandons the effort and signals a lock failure. If the transactional file sharing system encounters such a failure, it fails the operation with a 9L file status. If a lock error happens under other circumstances (such as in a situation where there is very heavy network traffic), the apllication program can react to the 9L by abandoning the transaction or by retrying the attempt.
    9S
    Realia Error in first of multiple SORT output files.

    PDS011 Open failed.

    90
  • For multithreading only: A CLOSE of a VSAM or QSAM file was attempted on a thread that did not open the file.
  • Without multithreading: For VSAM only: See the information on VSAM return codes.
    • Note: Vsam return code information may be obtained by coding a second file status value in the select clause as below. 
    FILE STATUS IS FS-Code VSAM-Code.

01  FS-Code                           pic xx.
01  VSAM-Code.
  05  VSAM-R15-Return                 pic s9(4) comp-5.
  05  VSAM-Function                   pic s9(4) comp-5.
  05  VSAM-Feedback                   pic s9(4) comp-5.
    91
    Incorrect password.

    Realia The requested operation cannot be performed. For open output, the directory is full, or there is an existing read-only file of the same name.

    PDS011 Invalid function passed in parameter list.

    Microsoft File structure error. On a READ usually indicated the the record size in the file is larger than the size specified in the program.

    92
    Logic error, i.e. opening an open file.

    For newer filesystems there are File Status codes which are more descriptive of the exact cause and are now used instead of 92.

    Realia File not found.

    PDS011 Member already open.

    CICSIO File not found. DSIDERR

    93
    Resource not available. Insufficient storage, no more extents available, file already under exclusive control.

    PDS011 Member is not open.

    CICSIO File not available.

    94
    No current record pointer for a sequential READ statement.

    Realia Improper record format. The record format of the file does not support the requested operation. May also be returned if the file-name is illegal.

    PDS011 Another member is already open for output.

    Microsoft File locked. OPEN a file that is in the locked state because another process had selected it with the LOCKING EXCLUSIVE clause.

    CICSIO LENGERR Length Error

    95
    Invalid or incomplete file information. Possibilities: Open an ESDS as a KSDS or vice versa, Attempt to open a non-loaded file as INPUT or I-O, Attempt to open a loaded file as OUTPUT, Record key length or displacement does not match catalog.

    Realia Invalid operation. An incorrect sequence of operations has occurred. A READ or WRITE with no preceding OPEN. A sequential REWRITE not preceded by a READ. OPEN after a CLOSE with lock.

    PDS011 PDS is not open, therefore can not be closed.

    Microsoft Indexed file system not available. (ISAM not resident)

    CICSIO ILLOCIC Illogical operation. See the next two bytes in EIBRCODE for the VSAM return and error code. INVREQ Invalid Request. NOTOPEN File not opened by CICS.

    96
    For VSAM file: An OPEN statement with the OUTPUT phrase was attempted, or an OPEN statement with the I-O or EXTEND phrase was attempted for an optional file, but no DD statement was specified for the file.

    For QSAM file: An OPEN statement with the OUTPUT phrase was attempted, or an OPEN statement with the I-O or EXTEND phrase was attempted for an optional file, but no DD statement was specified for the file and CBLQDA(OFF) run-time option was specified.

    DOS/VSE Missing DLBL card.

    MVS Missing DD statement.

    Realia Out of memory.

    PDS011 Mis-match between Desparms and names in NOTE string on START.

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

    Realia DOS critical error.

    PDS011 DCB open wrong mode.

    98
    Open failed due to either the invalid contents of an environment variable specified in a SELECT ... ASSIGN clause, or failed dynamic allocation. For more information about the conditions under which this status can occur see the "ASSIGN clause".

    PDS011 Could not find DDNAME in TIOT.

    99
    Abnormal termination. (Subroutine error).

    PDS011 Not enough concatenated PDS's in TIOT.

    CICSIO SYSIDERR ISCINVREQ NOTAUTH Not authorized for access.

    If you experience a problem with this page, please send a message to JTate@JaTomes.Com including a description of the problem.

    Last modified: Monday Dec-18-2006.