dspmqtrn (display incomplete transactions)
Display in-doubt and heuristically completed transactions.
Use the dspmqtrn command to display details of transactions. This command includes transactions coordinated by IBM MQ and by an external transaction manager.
- Requests details of externally coordinated, in-doubt XA transactions. Such transactions are those for which the queue manager (RM) has been asked to prepare to commit, but has not yet been informed by the TM of the transaction outcome (commit or rollback).
- Requests details of externally coordinated transactions that were resolved by the rsvmqtrn command, and the external transaction coordinator has yet to acknowledge with an xa-forget command. This transaction state is termed heuristically completed by X/Open. Note: If we do not specify -e, -h, or -i, details of both internally and externally coordinated in-doubt transactions are displayed, but details of externally coordinated, heuristically completed transactions are not displayed.
- Requests details of internally coordinated, in-doubt XA transactions. Such transactions are those for which the queue manager (TM) has asked each resource manager (RM) to prepare to commit, but an error was reported by one of the resource managers (for example, a network connection broke). In this state, the queue manager (TM) has yet to inform all resource managers of the transaction outcome (commit or rollback), but stands ready to do so. For more information, see Display outstanding units of work with the dspmqtrn command.
- Information about the state of the transaction in each of its participating resource managers is displayed. This information can help you assess the affects of failure in a particular resource manager. Note: If we do not specify -e or -i, details of both internally and externally coordinated in-doubt transactions are displayed.
- Requests a list of all transactions known to the queue manager . The returned data includes transaction details for all transactions known to the queue manager. If a transaction is currently associated with an IBM MQ application connection, information related to that IBM MQ application connection is also returned. The data returned by this command might typically be correlated with the output of a runmqsc DISPLAY CONN command, and the output fields have the same meaning as in that command.
- Not all of the fields are appropriate for all transactions. When the fields are not meaningful, they are displayed as blank. For example: The UOWLOG value when the command is issued against a circular logging queue manager.
- Specify this parameter on its own is the same as specifying -a -q.
- Displays all the data from the -a parameter and a list of up to 100 unique objects updated within the transaction. If more than 100 objects are updated in the same transaction, only the first 100 distinct objects are listed for each transaction.
- -m QMgrName
- The name of the queue manager for which to display transactions. If we omit the name, the transaction of the default queue manager are displayed.
|26||Queue manager running as a standby instance.|
|36||Invalid arguments supplied|
|40||Queue manager not available|
|49||Queue manager stopping|
|58||Inconsistent use of installations detected|
|69||Storage not available|
|72||Queue manager name error|
|102||No transactions found|