TMF Operations and Recovery Guide (G06.26+)

Occasional Operations
HP NonStop TMF Operations and Recovery Guide—522417-003
3-18
Disabling New Transactions
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
data volume. This kind of maintenance should be performed when there is little or no
transaction activity.
When you need to disable new transactions, use the DISABLE BEGINTRANS
command. After you issue a DISABLE BEGINTRANS command, TMF continues to
process existing transactions, but prevents new transactions from beginning. You can
still use the TMFCOM commands for dumping files, adding tape volumes to the
catalog, recovering files, obtaining information about dumps and TMF status, and so
forth.
New transactions cannot begin until an ENABLE BEGINTRANS command is issued.
Caution. Disabling new transactions stops transaction processing on your system. This
action will probably cause your transaction processing applications to fail, so you should stop
your applications before disabling transactions. If you must disable new transactions, choose
a time when the interruption will affect system users the least.