Implicit enqueuing on logically recoverable TD destinations
CICS® provides an enqueuing protection facility for logically recoverable (as distinct from physically recoverable) transient data destinations in a similar way to that for recoverable files.
There is one minor difference, however: CICS regards each recoverable destination as two separate recoverable resources—one for writing and one for reading.
Transient
data control commands that invoke implicit enqueuing are:
- WRITEQ TD
- READQ TD
- DELETEQ TD
Thus, for example:
- If a task issues a WRITEQ TD command to a particular destination,
the
task is enqueued upon that write destination until the end of the task
(or
unit of work). While the task is thus enqueued:
- Another task attempting to write to the same destination is suspended.
- Another task attempting to read from the same destination is allowed to read only committed data (not data being written in a currently incomplete unit of work).
- If a task issues a READQ TD command to a particular destination,
the task
is enqueued upon that read destination until the end of task (or
unit of work).
While the task is thus enqueued:
- Another task attempting to read from the same destination is suspended.
- Another task attempting to write to the same destination is allowed to do so and will itself enqueue on that write destination until end of task (or unit of work).
- If a task issues a DELETEQ TD request, the task is enqueued upon both the read and the write destinations. While the task is thus enqueued, no other task can read from, or write to, the queue.