READ‑ERROR: Unhandled cancellation in COBOL READ

Direct Answer

There is no portable, standard-conforming way to cancel a blocking READ operation in COBOL. The ISO/IEC 1989:2014 standard defines READ-ERROR and WRITE-ERROR only for file-access failures, not for timeouts or external cancellation requests. Any mechanism to abort a blocking I/O call is a vendor-specific extension and is not portable across platforms.

Implementation Analysis

Confirmed Facts

• Standard Behavior: A READ statement blocks execution until a record is available, the AT END condition is met, or a hardware/filesystem error occurs.
• SIGINT Effects: Sending a SIGINT or equivalent interrupt during a networked READ (e.g., NFS or SMB) results in implementation-dependent behavior. The runtime may return a vendor-specific file-status code (typically in the 9x range), trigger a runtime crash, or leave the record buffer in a corrupted state if the interrupt occurred mid-transfer.
• Corruption Risks: While READ interruptions primarily risk indeterminate file positions, WRITE interruptions are critical. Interrupted writes to variable-length or indexed files can result in partial records and filesystem inconsistency.

Likely Explanation

Most COBOL runtimes map the READ statement to blocking OS system calls (such as read() on POSIX or ReadFile() on Windows). While the OS may interrupt these calls via signals, the COBOL runtime environment often lacks the necessary logic to cleanly unwind the File Control Block (FCB) or restore the record pointer, leading to the "unhandled" nature of the cancellation.

Recommended Coding Patterns

To implement graceful timeouts without risking data corruption, avoid blocking the main execution thread on I/O. Use the following patterns:

Portable Polling Pattern

1. Decouple I/O: Use a separate process or thread to perform READ NEXT operations.
2. Shared Queue: The reader process places records into a shared memory queue or a temporary staging file.
3. Main Loop: The main program polls the queue or checks a cancellation flag between processing records.
4. Graceful Exit: Upon a cancellation request, signal the reader process to stop at the next record boundary and flush the queue.

Vendor-Specific Features

Vendor/Platform	Mechanism	Scope
Micro Focus	EXTFH with TIMEOUT clause	Windows/UNIX specific; applies to supported I/O calls.
IBM z/OS	CICS Transaction Timeouts	Managed by CICS region (Runaway Task/Deadline).
GnuCOBOL	CALL 'CBL_SIGNAL_PROC'	Experimental; may not interrupt blocking system calls.

Verification and Safety

To verify behavior on your specific runtime, use a scoped test:

* Test: Read from a named pipe to simulate a blocking network call
READ FILE-INPUT
    AT END DISPLAY "End of File"
    NOT AT END DISPLAY "Record Received"
END-READ

While the program is blocked, send a SIGINT from a separate terminal and record the resulting file-status code. If the status is 9x, consult your vendor's manual for the specific meaning of that error code.

Missing Diagnostic Detail

Which COBOL compiler and runtime version are you using? Because there is no standard, the specific recommendation (e.g., EXTFH vs. CICS Task Deadlines) depends entirely on your environment.