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

Cause
The HP COBOL Fast I-O routine initnewdatablock failed.
Effect
The READ statement is unsuccessful with I-O status code “30.”
Recovery
Report the error to your service provider.
232
An illegal operation was attempted on a fast i/o file
Cause
The program attempted to execute a READ REVERSED, REWRITE, or START statement to a file
that is using HP COBOL Fast I-O.
Effect
The REWRITE statement is unsuccessful with I-O status code “40.”
Recovery
Change the program so that it does not attempt to use HP COBOL Fast I-O. A program attempts
to use HP COBOL Fast I-O on a sequential file that meets these criteria:
• You are not creating an audited file (you can read an audited file, however).
• The file description includes a RESERVE clause with a number specifying the number of
blocks to buffer. number must be greater than 2.
• The file description does not include a LINAGE clause or a CODE-SET clause.
• The file was not opened with time limits (as with the TIME LIMITS phrase in the OPEN
statement).
• The program is not compiled with the NONSTOP directive.
• The specifications in the OPEN statement, or the attributes derived during the open operation
by some other means (such as from an applicable command interpreter ASSIGN command),
conform to:
◦ The open mode is INPUT or OUTPUT.
◦ The exclusion mode is EXCLUSIVE if OPEN OUTPUT is specified.
◦ The exclusion mode is PROTECTED if OPEN INPUT is specified.
233
OPEN OUTPUT SHARED specified for open disk file
Cause
OPEN OUTPUT file name SHARED was specified, and another process had the file open (in any
exclusion mode).
Effect
The OPEN statement is unsuccessful with I-O status error 30 and GUARDIAN-ERR 12.
Recovery
If you do not want to delete all of the information in the file, change the OPEN statement to
OPEN I-O file-name SHARED
and if necessary, specify OPTIONAL in the SELECT clause for the file.
1222 Run-Time Diagnostic Messages