TMF Operations and Recovery Guide (G06.26+)

Routine Maintenance
HP NonStop TMF Operations and Recovery Guide—522417-003
2-18
Understanding Transaction States
Understanding Transaction States
TMF transactions can be in various states of operation, which are shown in the
STATUS TRANSACTIONS command display. Table 2-4 describes transaction states.
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.
State The operational state of the transaction, as described in the following
section.
Parent The name of the system that sends a distributed transaction to another node
to perform work on it.
Children The names of any systems that receive and perform work on behalf of a
distributed transaction. During the course of a transaction, the child node
may send the transaction to yet another node. The original child node is now
also a parent node.
Starting MAT
Seq. No
Audit-trail file sequence number (for example, AA000001) of first audit-trail
file associated with this transaction.
Reason If the transaction is aborting or was aborted, brief message text explaining
the reason.
Backout
Assigned
If the transaction is aborting or was aborted, backout process assigned for
the transaction.
# Attempts
to Abort
If the transaction was subject to abort attempts, the number of those
attempts. (After 3 attempts, TMF places the transaction in the hung state.)
Start Time Age of the transaction on this node.
Table 2-4. Transaction States
State Meaning
Aborted The transaction has been backed out, either as a result of an ABORT
TRANSACTION command, or automatically by the TMF autoabort
function. (See Changing the Autoabort Configuration
on page 3-19 for
information on the autoabort function.) Locks held by the transaction are
being released. The transaction stays in this state until all nodes affected
by the transaction have been informed of the backout.
Aborting The transaction is being backed out.
Active The transaction is in progress.