COBOL asynchronous signal handling consistency during multi-threaded I/O

While COBOL-2002 provides the EXCEPTION clause for synchronous error handling, the language standard lacks a native mechanism for managing asynchronous timeouts or cancellations. In modern environments where COBOL programs run within multi-threaded containers, graceful cancellation typically relies on mapping OS-level signals like SIGTERM to specific routines.

A significant challenge arises when a cancellation signal is received while the program is engaged in a blocking I/O operation. Because the ON ERROR clause primarily targets statement-level runtime exceptions, it may not reliably trigger state cleanup or file de-allocation if the process is interrupted mid-transaction.

How do different modern COBOL implementations ensure thread-safety and state integrity when an asynchronous signal interrupts a blocking I/O call? Is there a standard-compliant approach to mapping external timer flags to COBOL-internal cleanup routines without risking file system corruption?