TMF Operations and Recovery Guide (G06.26+)

Routine Maintenance
HP NonStop TMF Operations and Recovery Guide—522417-003
2-20
Verifying that New Transactions Can Start
Reason: The TRANSCOUNTTHRESH was exceeded.
Meaning. The number of current transactions in the system is at or above the
configured maximum, which causes TMF to disallow new transactions. New
transactions can start when the transaction count decreases to an allowable number
(see Tabl e 1-4 on page 1-7 for more information).
Action. To solve this problem, consider the following:
•
If a new or changed application has been recently installed, it might be looping on
BEGINTRANSACTION. In this case, use the STATUS TRANSACTIONS
command to identify and stop the process.
•
If a bottleneck in either the system or the application is slowing down transaction
throughput so that transactions are not completing as quickly as new ones are
starting, performance tuning is needed.
•
If the TRANSCOUNTTRHESH value is inadequate for your system, work with the
system manager to adjust it.
Reason: The DISABLE BEGINTRANS command was issued.
Meaning. The DISABLE BEGINTRANS command has disabled new transactions.
Action. Issue the ENABLE BEGINTRANS command to reenable new transactions,
unless there is a reason not to do so.
Reason: TMF is stopped, is stopping and has already
disabled BEGINTRANSACTION, or is starting and has not
yet enabled BEGINTRANSACTION.
Meaning. This is a transitional state while TMF is stopping or starting.
Action. No action is needed.
Reason: The available TMFLIB memory in CPU number is
running low.
Meaning. The percentage of extended segment memory allocated by TMFLIB is at or
above the level that causes TMF to disallow new transactions. New transactions can
start when the memory used decreases to an allowable percentage (see Table 1-4 on
page 1-7 for more information).
Action. Work with the system manager to adjust the TMFLIBMEMTHRESH value for
your system, or change the extended segment size for TMFLIB.