TMF Operations and Recovery Guide (G06.24+)

Routine Maintenance
HP NonStop TMF Operations and Recovery Guide—522417-002
2-16
Displaying Transaction Activity
The same command issued on \SYS2 would show the following information:
Transaction Identifier Process State Parent Children
---------------------- ------- ----- ------ --------
\SYS1.0.40302 (3,54) active \SYS1
\SYS2 is unaware of the part of the transaction that affects \SYS3 and vice versa; only
\SYS1 knows about \SYS2 and \SYS3.
In the next example, \SYS2 accesses a server on a remote system, \SYS4. The
originating system is only aware of its immediate children; therefore, the STATUS
TRANSACTIONS command on \SYS1 still shows the following information:
Transaction Identifier Process State Parent Children
---------------------- ------- ----- ------ --------
\SYS1.0.40302 (3,54) active \SYS2
\SYS3
However, \SYS2 has knowledge that the transaction involves \SYS4. The STATUS
TRANSACTIONS command as viewed from \SYS2 would show the following
information:
Transaction Identifier Process State Parent Children
---------------------- ------- ----- ------ --------
\SYS1.0.40302 (0,54) active \SYS1 \SYS4
See the TMF Reference Manual for complete instructions on using the STATUS
TRANSACTIONS command.
Table 2-3 describes the information in the STATUS TRANSACTIONS display.
Table 2-3. Understanding the STATUS TRANSACTIONS Display
Heading Meaning
Transaction
Identifier
The transaction identifier, as described in the previous section, consisting of
the node name or number, CPU number, and sequence number. In addition,
if the tm-flags value used internally by TMF is not zero, this value appears
in parentheses following the node name or number. TMF uses one of the
flags in tm-flags to track the number of times TMF has been deleted and
subsequently re-initiated.
Process The CPU and process identification number (PIN) on the node that started
the transaction.