TMF Operations and Recovery Guide (G06.26+)

Occasional Operations
HP NonStop TMF Operations and Recovery Guide—522417-003
3-2
Stopping TMF
If you issue a START TMF command immediately after a STOP TMF, ABRUPT
command, there is a momentary period when the new TMP attempts to create a new
backout process (as a result of START TMF) before the old TMF backout process
terminates (as a result of STOP TMF, ABRUPT). Very soon thereafter, the backout
process terminates but is not restarted by the new TMP. In this event, aborting
transactions are hung.
To recover from this situation, enter a TMFCOM ALTER TMF, SWITCHPROCESS
TMP command. In response, the TMP restarts a new TMF backout process, and
aborting transactions are then completed.
The ALTER TMF, SWITCHPROCESS TMP command is explained in the TMF
Reference Manual.
If TMF crashes while unresolved distributed transactions exist in the prepared state
and you subsequently enter a START TMF command, TMF detects those transactions
and the start operation waits until they are resolved. If the parent node is now
available, TMF automatically resolves those transactions and the start operation then
completes. But if the parent node is not available, you must use the RESOLVE
TRANSACTION command to resolve the transactions manually before the start
operation can conclude. For more information about the RESOLVE TRANSACTION
command, see Resolving Distributed Transactions on page 3-22.
Stopping TMF
It is normally not necessary or even advisable to stop your TMF system: you can
reconfigure most TMF components and perform most maintenance operations with
TMF running. The TMF operations that require TMF to be stopped are listed below.
•
Deleting a TMF configuration or adding a new one (requires the STOP TMF and
DELETE TMF operations, followed by TMF reconfiguration if adding a new
configuration, followed by a START TMF operation)
•
Changing the TMF configuration volume, changing the audit-trail format for the
TMF configuration, or changing the TRANSACTIONPROTOCOL performance-
tuning attribute (requires a STOP TMF operation and an ALTER TMF operation
with selected option, followed by a START TMF operation.)
•
Applying a Product Version Update (PVU) to the TMP or TMFMON (For the TMP,
requires the STOP TMF, ABRUPT and START TMF operations. For the TMFMON,
requires a cold-load.)
Caution. Stopping TMF stops transaction processing on your system. This action will
probably cause your transaction processing applications to fail, so you should stop your
applications before stopping TMF. If you must stop TMF, choose a time when the interruption
will affect system users the least.
If you are experiencing a problem with TMF, do not stop it; you might delete information
necessary for solving the problem. Refer to Section 7, Recovery Methods
, when experiencing
TMF problems.