Automatic transactions, Common transaction – HP Integrity NonStop J-Series User Manual

Page 52

Configuring Automatic Transaction Processing

HP NonStop AutoTMF Software User’s Guide—429952-016

4-4

Automatic Transactions

Automatic Transactions

AutoTMF generates TMF transactions when a program is not coded to provide
transactions. As needed, AutoTMF starts and commits automatic transactions. Non
transactional programs are unaware that automatic transactions are being created and
committed.

While automatic transactions are being created and committed, a process may have its
own transactions, through calls to BEGINTRANSACTION or by inheriting transactions
through messages on $RECEIVE. Such transactions are called process transactions.
The process can manage its own transactions, while its automatic transactions are
managed transparently by AutoTMF.

Automatic transactions are created on demand, that is, only when the process
accesses an audited file in a way that requires a transaction.

Automatic transactions are used only for database operations within a single process;
automatic transactions are never exported to server processes.

Automatic transactions are always committed; they are never aborted.

Common Transaction

The common transaction is the default type of automatic transaction. The common
transaction is used to access multiple audited files within the same transaction. At any
time, a process has at most one common transaction.

Non transactional applications do not require configuration of common transactions.
You may configure common transactions to force the use of automatic transactions for
specific files, even if processes have their own transactions. This capacity is useful

Unstructured
Access

Not Applicable

Large-
Transfer
Writing

Not Applicable

Transaction
File (TFILE)

ATMFMAXTX

Not Applicable

MAXTX

Handling TMF
Environmental
Errors

ATMFSTOPONTMFERR

Not Applicable

STOPONTMFERR