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

Run-Time Diagnostic Messages
HP COBOL Manual for TNS/E Programs—520347-003
48-39
Message List
184
Cause. During the execution of an OPEN statement, the attempt to purge a file (the
purge is due to some attribute conflicts) 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. A value of “48,” for example, means that the program does
not have permission to purge an existing file that has an improper record size and
create a new one.
185
Cause. During the execution of an OPEN statement, the attempt to purge the data
from the file (the purge is due to an OPEN OUTPUT on a file that contains data) 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.
186
Cause. During the execution of a READ statement, the system read routine failed with
Guardian error nnn.
Effect. The READ 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.
187
Cause. A READ … LOCK statement was attempted on an OSS file or a file that is
reading ahead. This can happen if the file is opened for INPUT and the organization is
sequential. A READ operation that is executed as part of a transaction (delimited by
ENTER “BEGINTRANSACTION” and ENTER “ENDTRANSACTION” statements)
requires such locking.
Purge of file during OPEN failed with error nnn
Purge data from file during OPEN failed with error nnn
READ operation failed with error nnn
READ WITH LOCK on file with read ahead or an OSS file