TMF Operations and Recovery Guide (G06.26+)

Routine Maintenance
HP NonStop TMF Operations and Recovery Guide—522417-003
2-15
Maintaining Transactions
Action. If the wrong volume is mounted, mount the correct one. If you want to use the
mounted volume, you must delete the volume and then re-add it to the TMF
configuration; to do this, thus omitting this volume from the volume recovery, use the
DISABLE DATAVOLS, DELETE DATAVOLS, and ADD DATAVOLS commands with
suitable options. For more details, see the descriptions of these commands in the TMF
Reference Manual.
Maintaining Transactions
Transactions are the foundation of a TMF system. It is vital to make sure that TMF can
process transactions when they are initiated by a system user. A transaction can affect
one file or many files on a data volume, and can span multiple systems. You monitor
the status of transactions to make sure that any long-running operations do not affect
system performance. You also monitor TMF to make sure that new transactions can
start.
If a transaction involves a requester, servers, and files that all reside on the same node
(NonStop server), the transaction is a local transaction. If a transaction involves
processes or files that reside on a remote node or are generated from a remote node,
the transaction is a homogeneous distributed transaction. If a transaction consists of
multiple portions that are processed by different transaction management systems
running under other operating systems as well as the NonStop OS, the transaction is a
heterogeneous distributed transaction.
This section explains how TMF identifies transactions and describes transaction states.
It also describes how to monitor the status displays for individual transactions and for
the part of the system that allows transactions to start, and explains what action may
be needed based on the information in the displays.
Understanding Transaction Identifiers.
Each transaction that TMF protects has a unique identifier. A transaction identifier has
the form:
node
specifies the name of the node (system) from which the transaction originates.
The default is the node on which the TMFSERVE process communicating with
your TMFCOM is running.
[node. ]
[node-number. ]
[node(tm-flags). ] cpu.seq-num
[node-number(tm-flags). ]
[(tm-flags). ]