AutoTMF Software User's Guide (Update 14)

NonStop AutoTMF Commands
HP NonStop AutoTMF Software User’s Guide—429952-016
6-41
ALTER GLOBAL
these cases, if the batch process is restarted after a failure, some completed
server requests may be aborted.
When the master process stops sending work to the server, there may be an
outstanding active transaction, plus record locks and uncommitted updates. A
commit timer will commit the active transactions after a specified idle period.
The master process may send a terminating request to the servers but should
not stop the server processes.
Automatic transactions are committed in any of the following instances:

the process terminates (but not if the process is stopped).

the server is waiting for a request and the time since the last request
exceeds the specified value.

the transaction reaches the limits set by the MAXTIME and MAXUPDATES
parameters.
Each transaction spans many server requests and updated records are kept
locked between server requests. If the batch process sends work to many
server processes, the servers processes must access different database
records or a deadlock may occur. The commit timer will not cause the current
transaction to be committed if the process is deadlocked.
ATMFTXTIMEOUT { value | NEVER | OFF }
sets the maximum duration of an automatic transaction, regardless of the TMF
AutoAbort setting. This feature requires TMF version 3.6 or later.

value: is n [ SEC[ONDS] | MIN[UTES] ], between 5 and 510 minutes.
value overrides the TMF AutoAbort timer setting. A value entered as
n SEConds is rounded up to minutes.

NEVER: the transactions is never aborted by TMF due to a timeout.

OFF: the default, specifies that the TMF AutoAbort is in effect.
If TXTIMEOUT is configured on a system that is not running TMF 3.6 or later, a
warning message is displayed, the configuration is updated and the transaction
timeout takes effect when TMF 3.6 is installed.
ATMFWARNLONGTX
sets the frequency of long transaction warning messages displayed in the EMS
log. By default, the warnings are generated every 5 minutes.
The AutoTMF runtime generates periodic EMS messages to alert the operator
of long running transactions, which are usually caused by a program holding
Note. The AutoTMF AutoCommit timer always applies, regardless of the configured
transaction timeout. If the desired transaction time out value exceeds the configured
AutoCommit timer value, the user should adjust the AutoCommit timer accordingly.
See AutoCommit attribute description above on page 6-7
for details.