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

Configuring Automatic Transaction Processing
HP NonStop AutoTMF Software User’s Guide—429952-016
4-10
Requiring Files to Be Audited
To prevent errors and deadlocks, AutoTMF automatically configures each file open for
read-through-locks mode. This mode has no effect on locking operations such as
READLOCK, only on non-locking access such as READ. You may disable this
configuration by altering the ATMFREADTHRULOCK global or by specifying NO
READTHRULOCK for a file set or program. If, however, a process attempts a READ or
READUPDATE on a file that has an active automatic transaction, READTHRULOCK
will always be set.
Requiring Files to Be Audited
AutoTMF manages access to audited files in a manner transparent to application
programs. If the audited attribute is removed from any of the audited files it is
managing, the application will continue to operate without any problem because
AutoTMF does not attempt to generate transactions for un-audited files.
In some environments, the accidental or deliberate disabling of audit on such files is
considered a critical event.
You can enforce the requirement that a file be audited:
1. First set the global parameter ATMFABENDNOAUDIT to ON.
2. Then, configure the files for which auditing is critical with one of the following
ATMFFILE options: COMMONTX, SEPARATETX, RECORDTX, or NOTX.
When a configured file is opened by a program, AutoTMF checks the audit flag. If the
file is not audited, the NonStop AutoTMF runtime abends the program and sends a
message to the EMS log, thus preventing any update to occur.
Handling TMF Environmental Errors
By default, if a program encounters a TMF environmental error, AutoTMF aborts the
program because the program cannot continue processing without compromising data
integrity. This has the side effect of producing large numbers of saveabend files at a
time when the system is under stress.
You can configure AutoTMF to stop, rather than abort, a program that encounters TMF
errors. This eliminates the proliferation of saveabend files caused by TMF problems.
If AutoTMF aborts or stops a program when a TMF error occurs, it sends a message to
the EMS log describing the failure and displaying the TMF error that was encountered.
STOPONTMFERR applies to the following TMF errors:
The TMF errors that are affected by this parameter are:

FETMFNOTRUNNING (82)

FETMFNOTCONFIGURED (84)

FEDEVICEDOWNFORTMF (85)