Determining transaction states

A transaction can be in any one of a number of states.

The possible transaction states are:

LOCK: A transaction in LOCK state does not receive messages. Scheduled messages containing this transaction code are stopped.
Restriction: The /LOCK TRANSACTION command cannot be used with Fast Path-exclusive transactions, but it can be used with Fast Path-potential transactions.
MODSTOPPED: A transaction in MODSTOPPED state cannot receive input, because online change processing is in progress. A /MODIFY COMMIT command sets this status. A CPI Communications driven transaction cannot be marked MODSTOPPED.
PSTOP: A transaction in PSTOP state cannot be scheduled; however, the transaction continues to be processed until the limit count is reached. If the limit count is large, the processing interval is long. To ascertain the status of the transaction, use the /DISPLAY command; to alter the status of the transaction, use the /ASSIGN command.
PURGE: A transaction in a PURGE state has had its input messages stopped.
QSTOP: A transaction in QSTOP state cannot be entered during the time between the completion of a /MODIFY PREPARE command and the completion of the corresponding /MODIFY COMMIT or /MODIFY ABORT command. Transactions that are known to be affected by the content of an online change are rejected; that is, the transactions are to be changed or deleted, or they could access databases or programs that are to be changed or deleted. By using the /DISPLAY MODIFY command, you can cause a list of transactions that are affected by a current online change to be displayed. At the terminal, such a transaction is rejected with message DFS3470. If the transaction uses a Fast Path routing code that is changed or deleted, the rejection message is DFS3471. A CPI Communications driven transaction is never in a QSTOP state.
STOP: A transaction in STOP state is stopped. The queuing and scheduling of messages that are destined for a transaction or class of transactions are stopped. However, output can still be queued if it originates from an application program.
USTOPPED: USTOPPED is a status value that is set when an application program attempts to use an IMS DL/I database resource that is not available, and the program terminates abnormally with abend U3033. The USTOPPED condition is not set for a CPI Communications driven program. The CPI Communications driven application program is abnormally terminated with an abend U0125.