Handling tmf environmental errors – HP Integrity NonStop H-Series User Manual
Page 55
![background image](/manuals/397556/55/background.png)
Configuring Automatic Transaction Processing
HP NonStop AutoTMF Software User’s Guide—429952-013
4-11
Handling TMF Environmental Errors
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 any of the configured files is opened by a program, NonStop AutoTMF software
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, NonStop AutoTMF
software 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 NonStop AutoTMF software to stop, rather than abort, a program
that encounters TMF errors. This eliminates the proliferation of saveabend files caused
by TMF problems.
If NonStop AutoTMF software 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)
•
FEBEGINTRDISABLED (86)
•
FETRANSABRTOWNERDIED (90)
•
FENODEVBUFSPACE (89)
•
FETRANSABRTOWNERDIED (90)
•
FETRANSABRTBADDBID (91)
•
FETRANSABRTNETDOWN (92)
•
FETRANSABRTAUDOVFL (93)
•
FETRANSABRTOPRCMD (94)
•
FETRANSABRTDISCTKOVR (95)