Using the DTC Transaction List and Transaction Properties Windows
Occasionally, if a communication line fails or a faulty distributed transaction application leaves unresolved transactions, you might need to view a transaction's properties in the DTC Transaction List window of the Component Services administrative tool. For example, a transaction might get stuck and remain present for long periods of time, or a transaction might time out and be forced to abort, or a system might fail and after recovery be unable to connect to an involved resource manager, leaving the transaction in an In Doubt or Failed to Notify state. In each case, you must view the transaction list before you can resolve the transaction states.
When you right-click an OLE transaction in the Transaction List window and point to properties, the Transaction Properties window opens, displaying a Parent/Subordinate column and an ID column. The Parent/Subordinate column displays the name of the parent transaction manager, if any, followed by the names of subordinate transaction managers and resource managers.
If the transaction originated on the local system, the local transaction manager is serving as the global commit coordinator and there is no parent. In this case, the first entry in the Parent/Subordinate column is <no superior>. If the transaction originated on another system, the name of that parent system is displayed in the Parent/Subordinate column.
In the Transaction Properties window, the names of the subordinate transaction managers and resource managers are listed following the parent transaction manager. For each subordinate OLE Transactions transaction manager, the Parent/Subordinate column contains the name of the subordinate transaction manager system. For each subordinate OLE Transaction resource manager, the Parent/Subordinate column contains the resource manager's displayable name if the resource manager supplied the name when it first connected to the DTC.
If the parent or subordinate is an OLE Transactions transaction manager or resource manager, the ID column of the Transaction Properties window is empty. If the parent or subordinate is an LU 6.2, TIP, or XA transaction manager, the ID column of the Transaction Properties window displays the transaction identifier of the transaction. For more information about LU 6.2, and TIP transactions, refer to the sections that follow.
For each IBM LU 6.2 transaction, the LU Pair is displayed in the Parent/Subordinate column of the Transaction Properties window and the Logical Unit of Work ID is displayed in the ID column.
The LU Pair consists of the fully qualified Microsoft SNA Server LU followed by the fully qualified IBM SNA LU. Each fully qualified LU consists of the network name followed by the LU name. Currently, the Microsoft system is always the transaction coordinator and the IBM system is always the subordinate.
The Logical Unit of Work ID consists of the fully qualified Microsoft SNA Server LU, followed by the Logical Unit of Work instance number and the Logical Unit of Work sequence number. The instance number and sequence number are displayed in hexadecimal form. You can correlate these values with the corresponding values on your IBM system.
For each TIP transaction, the TIP transaction manager's address is displayed in the Parent/Subordinate column of the Transaction Properties window and the TIP transaction ID is displayed in the ID.