AutoTMF Software User's Guide (Update 14)

Configuring Automatic Transaction Processing
HP NonStop AutoTMF Software User’s Guide—429952-016
4-11
Suppressing Inherited Transactions

FEBEGINTRDISABLED (86)

FENODEVBUFSPACE (89)

FETRANSABRTOWNERDIED (90)

FETRANSABRTBADDBID (91)

FETRANSABRTNETDOWN (92)

FETRANSABRTAUDOVFL (93)

FETRANSABRTOPRCMD (94)

FETRANSABRTDISCTKOVR (95)

FETRANSABRTTIMEOUT (96)

FEABORTEDTRANSID (97)

FENOMORETCBS (98)
Suppressing Inherited Transactions
A non TMF-aware server may inherit a transaction from a TMF-aware requester when
reading $RECEIVE. The transaction has no effect on the program. However, if
AutoTMF is configured, the inherited transaction becomes visible to the program.
When AutoTMF detects an inherited transaction, AutoTMF assumes that the process
will use that transaction to access audited files.
Suppressing inherited transactions insures that AutoTMF generates automatic
transactions for all audited file accesses, emulating the behavior of a non TMF-aware
process.
UNLOCKFILE Optimization
Non TMF-aware programs sometimes issue a blanket call to UNLOCKFILE to release
all locks rather than managing locks individually. In high-volume environments, the cost
of UNLOCKFILE can be noticeable. When files are audited, the transaction commit
unlocks records that participate in the transaction, making the UNLOCKFILE
redundant.
AutoTMF can be configured to eliminate the call to UNLOCKFILE. Since the program
has released all locks on the file by issuing the UNLOCKFILE, AutoTMF attempts to
commit the transaction, following the usual rules for committing an automatic
transaction. If a lock is held on another file participating in the transaction, the commit
will occur when this lock is released by the program.
Note that this optimization can only be enabled for files that are also enabled for
automatic transactions.