When IMS purges undeliverable commit-then-send output

If the purge function is specified, IMS purges commit-then-send (commit mode 0) output in certain circumstances only.

When the purge function is specified, IMS purges commit-then-send (commit mode 0) output when:
  • IMS Connect receives a NAK response from the client application
  • IMS Connect cannot deliver the output to the client application
  • OTMA cannot deliver the output to IMS Connect

When IMS Connect receives a NAK response from the client or cannot deliver the output to the client, IMS Connect notifies OTMA to discard the output message from the IOPCB queue. When OTMA cannot deliver the output to IMS Connect, OTMA discards the output without waiting for notification from IMS Connect.

If an IMS Connect STOPCLNT command is issued for a client ID that specifies the purge function, the reply message is purged.

IMS does not support the purge function for the following types of output:
  • IMS application output to ALTPCBs. Even if the purge function is specified for the IMS application CM0 output, the purge function does not apply to inserts to ALTPCBs.
  • CM1 output. Any output from a CM1 transaction that is undeliverable is already discarded and the transaction is backed out.
  • Output associated with a send-only transaction. Output for send-only transactions is routed directly to the asynchronous hold queue.
  • Output associated with a RESUME TPIPE call input message. A RESUME TPIPE call, by definition, requires and guarantees that the output is delivered.