TMF Reference Manual (G06.26+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-003
3-336
STATUS TRANSACTIONS
transaction comes into being when an application accesses a file or server on
a remote node on behalf of a locally originated transaction.
ABORTING
displays only transactions in the aborting state. A transaction enters this state
when an application calls the ABORTTRANSACTION procedure or the system
aborts the transaction. The transaction remains in this state until all of its
effects have been completely undone on this node.
ABORTED
displays only transactions that have been aborted. A transaction enters this
state when all of its effects are undone and its transaction state (aborted)
record is written to the audit trail. A transaction normally stays in this state only
briefly. But, in the case of a distributed transaction on a remote node, if the
remote node (the child node, in this case) unilaterally aborts a transaction, that
transaction remains in the aborted state until the parent node is informed of the
outcome. Only transactions in that situation are displayed by the STATUS
TRANSACTIONS, STATE ABORTED command.
COMMITTED
displays only transactions in the committed state. A transaction enters this
state after its transaction state (committed) record is written to the audit trail. A
transaction normally stays in this state only briefly. However, in a distributed
transaction, a parent node cannot remove a committed transaction until all
child nodes have been informed of the commitment. The STATUS
TRANSACTIONS, STATE COMMITTED command identifies such
transactions.
ENDING
displays only transactions in the ending state. In this state, which lasts only
very briefly, a transaction is waiting for locks to be released. This is the final
state through which a transaction progresses to conclude its life.
HUNG
displays only transactions hung during backout. A transaction enters this state
if the backout process attempts, but fails, to abort it.
PREPARED
displays only distributed transactions in the prepared state. A distributed
transaction enters this state after it completes phase 1 of its commitment and
its transaction state (prepared) record is written to the audit trail. The
transaction remains in this state until the remote node is informed by its parent
of the transaction’s outcome.