HP Integrity NonStop J-Series - Manual (Page 69)

HP NonStop AutoTMF Software User’s Guide—429952-017
5-1
5
Usage Guidelines
This section describes typical uses and limitations of AutoTMF, drawn from the
experiences of customers.
Auditing Files
Auditing Unstructured Files
Preparing HP Utilities
Preparing Third-party Applications
Auditing Enscribe Queue Files
NonStop AutoTMF and Process Pairs
Auditing Files
Once NonStop AutoTMF software is installed, the programs are prepared, and after
NonStop AutoTMF configuration attributes have been specified, you can enable
auditing of files. Enabling auditing can be performed by using the standard system
utilities FUP and SQLCI, but the AutoTMF command interpreter can also audit entire
file sets with a single ALTER command.
The audit attribute may not be changed when a file is open, so you will need to stop
applications that are using the file in order to change the audit attribute.
Non TMF-aware applications
Non TMF-aware applications do not access any audited file. By default:

Auditing a file will cause AutoTMF to generate automatic transactions to manage
access to the file because there is no active transaction.

Access to all audited files occurs under the common transaction.
However you can configure some files to be managed as a separate transaction.
TMF-aware applications
TMF-aware applications access audited files under their own transactions. These
transactions are begun and ended or aborted by the application, not by AutoTMF. The
non-audited files that these applications also access can now be audited and managed
by automatic transactions generated by AutoTMF.
AutoTMF does not start an automatic transaction if a process transaction is active. To
generate automatic transactions to access newly audited files, explicitly configure
these files by specifying the AutoTMF file attribute COMMONTX or SEPARATETX.
In a mixed AutoTMF and application controlled transaction environment, you must
specify to AutoTMF which files are managed by AutoTMF and which files are managed