TMF Operations and Recovery Guide (G06.26+)

Occasional Operations
HP NonStop TMF Operations and Recovery Guide—522417-003
3-17
Enabling New Transactions
To start transaction processing later, use the ENABLE BEGINTRANS command.
Enabling New Transactions
On most systems, transaction processing should run constantly, unless a maintenance
operation or system failure causes it to stop. This section describes the situations that
can prevent new transactions from starting, and contains suggestions for recovery.
Once you clear the condition that prevented new transactions, you can use the
ENABLE BEGINTRANS command to restart transaction processing.
Reason: The TMF subsystem is not running
Meaning. TMF is not in the started state, so it cannot accept new transactions.
Action. Check the STATUS TMF display to see the TMF state; if it is starting, no action
is necessary. Transactions will be enabled when the TMF state reaches started
(unless TMF has been started with the DISABLE BEGINTRANS option). If TMF is in
the stopping state, it has disabled the BEGINTRANSACTION procedure as part of its
shutdown process. If TMF is in the stopped state, it is completely shut down. To start
TMF with transaction processing enabled, use the START TMF command without
options.
Reason: A DISABLE BEGINTRANS command was issued
Meaning. The BEGINTRANSACTION procedure has been manually stopped by a
TMF operator. This action may be taken to perform maintenance that requires all TMF
volumes to be in a consistent state. New transactions cannot begin until an ENABLE
BEGINTRANS command is issued.
Action. Use the ENABLE BEGINTRANS command to start the BEGINTRANSACTION
procedure, thereby allowing new transactions to start.
Reason: An audit trail has reached its begin-transaction-
disable threshold
Meaning. New transactions cannot start because the audit trail is too full.
Action. Find out why there is no available space on the audit trail, and take the action
necessary to correct the situation. For more information, see Why Audit-Trail Files
Stay Pinned on a Volume on page 2-5 and Responding to Audit-Trail Overflow on
page 3-5.