TMF Reference Manual (G06.26+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-003
3-346
STOP TMF
To confirm that it accepts the STOP TMF command, TMFCOM displays the following
message:
STOP TMF operation [operation-number] begun.
The ABRUPT option terminates all TMF activities immediately, basically causing TMF
to crash. With this option, transactions in the brief, final commit stage are allowed to
finish, but all other in-progress transactions are aborted and no new transactions can
start. User applications receive an error code indicating whether their transactions
were committed or aborted. Aborted transactions are undone by the backout process
when TMF is started again.
If you issue a STOP TMF command without the ABRUPT option and then decide you
do not want to wait for unfinished work to complete, you can press the BREAK key and
issue another STOP TMF command with ABRUPT specified. TMFCOM accepts this
new command immediately, and the ABRUPT option takes effect at once.
If you issue the STOP TMF command with the NOWAIT option, you can verify later
that the shutdown was complete by entering the DISPLAY OPERATIONS command.
In the DISPLAY OPERATIONS command, use the operation number returned by the
STOP TMF command-acceptance message or the appropriate date-time specification.
The STOP TMF command fails if commit-hold is currently activated for an audit trail
and has not been suspended. In this case, if you wish to stop TMF, you must do one
of the following:
•
Wait until commit-hold is no longer activated. (This will occur when the problem
that activated the commit-hold is resolved, or when commit-hold is turned off or
suspended.) Then, enter the STOP TMF command.
•
Use the STOP TMF command with the ABRUPT option.
Output Displayed
As TMF shutdown progresses, TMFCOM displays EMS messages about various
events. The format and content of these messages varies. Many of these messages
show the status (stopping or stopped) of the primary and backup processes for the
individual TMP components; these messages can help in analyzing problems that
might occur during TMF shutdown.
Message examples appear along with the command-entry examples.
Caution. The STOP, ABRUPT command can disrupt customer applications. If the audit trails
are not disturbed while TMF is down, any transactions aborted when the STOP, ABRUPT
operation occurs should be properly backed out when TMF is restarted, and the database
should remain consistent. Nevertheless, it is always safest to use the ABRUPT option only at
times of low transaction activity.
Caution. If multiple users are managing your TMF system, be sure to communicate your
intentions to stop or restart TMF.