COBOL Manual for TNS/E Programs (H06.08+, J06.03+)

Recovery
If you want the file to be created for EXTEND or I-O, put OPTIONAL in the SELECT clause;
otherwise, verify that the file exists when the program is run.
163
OPEN page eject failed with error nnn
Cause
The attempt to eject the first page during the processing of an OPEN statement referencing a
LINAGE file or during the process of COBOL_SPECIAL_OPEN_ failed with Guardian error nnn.
Effect
The OPEN statement or call to COBOL_SPECIAL_OPEN_ is unsuccessful with I-O status code
“30.”
Recovery
Type ERROR nnn to see the meaning of the Guardian error; it might indicate corrective action.
164
OPEN rewind failed with error nnn
Cause
The attempt to rewind the file during the processing of an OPEN statement failed with Guardian
error nnn.
Effect
The OPEN statement is unsuccessful with I-O status code “30.”
Recovery
Type ERROR nnn to see the meaning of the Guardian error; it might indicate corrective action.
165
OPEN requested for an unsupported device
Cause
The device assigned to the COBOL file is not a legal device for COBOL input or output.
Effect
The OPEN statement is unsuccessful with I-O status code “39.”
Recovery
Assign a file on a legal device.
166
OPEN requested for a locked file
Cause
The file referenced in an OPEN statement is locked (CLOSE LOCK was executed). CLOSE LOCK
is unrelated to LOCKFILE and UNLOCKFILE. A COBOL file name associated with a disk file can
become locked even if it is never opened. This message appears when the disk file is also
assigned to some other COBOL file name with the same ASSIGN name in the same run unit,
and a CLOSE LOCK is executed on that file name.
Effect
The OPEN statement is unsuccessful with I-O status code “38.”
Recovery
Either do not close the file with lock or correct the program.
1206 Run-Time Diagnostic Messages