TMF Operations and Recovery Guide (G06.24+)

Occasional Operations
HP NonStop TMF Operations and Recovery Guide522417-002
3-17
Disabling New Transactions
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.
Reason: There are too many active transactions in progress
on the system
Meaning. The maximum number of transactions allowed to run concurrently, as
configured on your system, has been exceeded.
Action. After ruling out application errors by checking the system and application logs
for error messages, work with your system manager to alter the transaction count
threshold, as described in the TMF Planning and Configuration Guide.
Reason: The amount of available memory for TMF
processes is too low
Meaning. Your TMF system is configured to have a certain amount of memory
available for the TMP process and TMFLIB subroutines: one of these components is
running out of memory.
Action. After ruling out application errors by checking the system and application logs
for error messages, work with your system manager to alter the relevant memory
threshold, as described in the TMF Planning and Configuration Guide.
Disabling New Transactions
It is normally not necessary or even advisable to prevent new transactions from
starting while TMF is running. The only time you may need to take this action is to
perform maintenance that requires all TMF volumes to be in a consistent state: for
example, you may want to prevent new transactions from starting while you rename a