Stopping transactions and PSBs because of unavailable data

In a DB/DC environment, IMS stops the transaction type if most messages being processed are failing because they are encountering unavailable data.

In a DB/DC environment, IMS stops the transaction type if most messages being processed are failing because they are encountering unavailable data. One abort is counted each time the program aborts due to abend U3303 and the message in process has not previously been placed on the suspend queue. Two aborts are subtracted each time a program goes through commit processing. However, if this results in a negative number, two aborts are not subtracted. If the total number of aborts exceeds 10, the transaction is stopped with a USTOPPED condition.

The transaction is stopped by USTOPPED if abend U3303 occurs while processing the message and SERIAL=YES is specified for the TRANSACT macro.

When the transaction is stopped by USTOPPED, messages from this queue are not scheduled for processing. Incoming messages continue to be queued on the normal queue.

In a DBCTL environment, after ten U3303 abends IMS stops the PSB instead of the transaction, preventing further rescheduling of the application program.