AutoTMF Software User's Guide (Update 12)

NonStop AutoTMF Software Commands
HP NonStop AutoTMF Software User’s Guide—429952-014
6-16
ADD ATMFPROGRAMS
NOWAIT[TX]
returns control to the application without waiting for the transaction to be fully
committed. Automatic transactions generated by the programs are committed
in nowait mode. The status of a nowait transaction is checked by the runtime
when the next transaction for the file is started or when the process terminates.
NOWARNLONGTX
suppresses the warning message that is normally displayed in the EMS log
when an automatic transaction runs longer than 5 minutes. The warning is
repeated every 5 minutes until the transaction is committed.
Users should exercise caution when suppressing the long transaction warning
and do so only if the cause for the delayed commit is well understood.
To suppress the warning for all programs, set the global parameter
ATMFNOWARNLONGTX to ON.
OPTIMIZEUNL[OCKS]
specifies that UNLOCKFILE operations performed on audited files by the
program fileset are suppressed. NonStop AutoTMF software considers all locks
on the file released and attempts to commit the transaction, subject to the
usual protocol for committing automatic transactions.
This optimization only applies to files that are enabled for automatic
transactions.
UNLOCKFILE optimization can also be enabled for a program by specifying
the class map define =_ESCORT_OPTIMIZEUNLOCKS with a dummy file.
To enable the optimization for all programs, set the global parameter
ATMFOPTIMIZEUNL[OCKS] to ON.
READTHRULOCKS
instructs NonStop AutoTMF software to enable read-thru-lock mode on audited
files that use automatic transactions.
If READTHRULOCKS is specified, the program attribute overrides the global
ATMFREADTHRULOCK. setting
To set this option for a specific file set use the ADD ATMFFILESET
or ALTER
ATMFFILESET command.
RECORDTX
generates an automatic transaction for each locked record and commits the
transaction as soon as the record is unlocked.
RECORDTX is used when a file is accessed by programs in which record
locking sequences do not allow NonStop AutoTMF software to commit
automatic transactions (there is at least one lock held on a record in this file at
any given time).