TMF Management Programming Manual (G06.24+)

Commands and Responses
HP NonStop TMF Management Programming Manual—522420-002
5-187
STATUS TRANSACTION
ZTMF-MAP-STATUS-TRANSACTION
is an extensible structured token specifying attributes that are used to select the
transaction for which information is to be returned. This token is optional; only one
occurrence is allowed. If multiple attributes are specified, information is returned
only for transactions that meet all the selection criteria (that is, the values are
logically “and-ed”). This token contains the following fields:
ZSTATE
specifies that information should be returned only for unresolved transactions
in the selected state. The following values are valid:
ZTMF-VAL-ACTIVE
specifies transactions in the active state. A transaction enters this state
when it comes into being. A local transaction comes into being when an
application calls the BEGINTRANSACTION procedure. A remote
transaction comes into being when an application accesses a file or server
on a remote node on behalf of a locally originated transaction.
ZTMF-VAL-ABORTING
specifies 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.
ZTMF-VAL-ABORTED
specifies transactions that have been aborted. A transaction enters this
state when all of its effects are undone and the ABORTTRANSACTION
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.
ZTMF-VAL-COMMITTED
specifies transactions in the committed state. A transaction enters this
state when the ENDTRANSACTION 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.