TMF Operations and Recovery Guide (H06.05+, J06.03+)

Routine Maintenance

HP NonStop TMF Operations and Recovery Guide—540137-002

2-19

Verifying that New Transactions Can Start

If there is a problem with transactions starting, you usually discover it by monitoring the

EMS log or the STATUS TMF display: that display provides a global view of TMF.

You can also use the STATUS BEGINTRANS command to make sure that transactions

are able to start on the system; this command displays the status of the

BEGINTRANSACTION object. Under normal operation, BEGINTRANSACTION is

enabled and new transactions are allowed to start. There are several reasons that

cause BEGINTRANSACTION to become disabled, however; under this condition, new

transactions are not allowed to start.

Any user allowed to use TMFCOM can issue this command while TMF is running.

Normally, the STATUS BEGINTRANS command displays the message:

BeginTrans Status: ENABLED

If transaction starts are disabled, you will see the message:

BeginTrans Status: DISABLED

The command also displays the reason why new transactions are disabled.

Reason: Audit Trail is above the BEGINTRANSDISABLE

threshold.

Meaning. The active-audit volume has filled to the level that causes TMF to disallow

new transactions. When the used capacity falls below this level, new transactions are

allowed to start.

Action. See Why Audit-Trail Files Stay Pinned on a Volume on page 2-5 and

Responding to Audit-Trail Overflow on page 3-5 for information on correcting the begin-

transaction-disable condition.

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.