Formato de prestamo de equipo

...

Fast I-O, sufficient memory for Fast I-O was not available.

“97” The input-output statement is successfully executed, but the

circumstances were not entirely as expected.

For an OPEN statement, either the referenced file has labels and

LABEL RECORDS OMITTED was specified, or it does not have

labels and LABEL RECORDS STANDARD was specified.

For a READ statement, the retrieved record is currently locked,

whether through some other file name of the run unit or by some

other process.

For a START statement, the start operation performed a read

operation to validate a position, and the record that was read was

locked.

Procedure Division

COBOL85 Manual–134543

8-33

I-O Status Code

Table 8-6. I-O Status Code Meanings: Unsuccessful Completion—

At-End Condition

I-O Status codes File Exception Condition

“10” A sequential READ statement is attempted and no next logical record

exists in the file because the logical end of the file has been reached.

“14” A sequential READ statement is attempted for a relative file, but the

relative record number cannot be assigned to the relative key data

item described for the file without a loss of significance.

Table 8-7. I-O Status Code Meanings: Unsuccessful Completion—

Invalid-Key Condition

I-O Status codes File Exception Condition

“21” 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 sequence

requirements for successive record key values are violated.

“22” An attempt has been made to write or rewrite a record that would

create a duplicate relative key, a duplicate prime record key, or a

duplicate alternate record key for which uniqueness is required.

“23” An attempt has been made to access a record identified by a key, and

that record does not exist in the file.

“24” An attempt has been made to write beyond the externally-defined

boundaries of a relative or indexed file, or a sequential WRITE

statement is attempted for a relative file but the relative record

number cannot be assigned to the relative key data item described for

the file without a loss of significance.

Procedure Division

COBOL85 Manual–134543

8-34

I-O Status Code

Table 8-8. I-O Status Code Meanings: Unsuccessful Completion—

Permanent Error Condition

I-O Status codes File Exception Condition

“30” A permanent error exists and no further information is available

concerning the input-output operation.

“34” A permanent error exists because of a boundary violation. This

condition indicates that an attempt has been made to write beyond the

externally-defined boundaries of a sequential file.

“35” A permanent error exists because an OPEN statement with the

INPUT, I-O, or EXTEND phrase is attempted on a required file that

is not present.

“37” A permanent error exists because an OPEN statement is attempted on

a file that is required to be a disk file but is supported on some other

medium.

“38” A permanent error exists because an OPEN statement is attempted on

a file previously closed with lock.

“39” The OPEN statement is unsuccessful because a conflict has been

detected between the fixed file attributes and the attributes specified

for that file in the program.

Table 8-9. I-O Status Code Meanings: Unsuccessful Completion—

Logic Error Condition (page 1 of 2)

I-O Status codes File Exception Condition

“41” An OPEN statement is attempted for a file already in the open mode,

or for one in a set of files that resides on a multiple file reel set when

some other file in that set is already in the open mode.

“42” A CLOSE, LOCKFILE, or UNLOCKFILE statement is attempted for

a