Running Fault Analyzer with similar third-party products
In general, Fault Analyzer works with other similar third-party products without problems, with the possible exception being Language Environment® batch jobs. Fault Analyzer uses the Language Environment® CEEEXTAN facility (IDIXCEE), as does potentially other similar third-party products. If more than one exit is specified in the CEEEXTAN list, then Fault Analyzer should be the first exit specified.
The analysis of LE jobs by Fault Analyzer can also be done using the IEAVTABX MVS™ change options/suppress dump exit (IDIXDCAP). Ensure that the LE options include the TERMTHDACT option, with the UATRACE, UADUMP, UAONLY, or UAIMM suboption, to make LE request an MVS™ dump for an abend. This way, the third-party product can use the CEEEXTAN exit while Fault Analyzer can run from the IEAVTABX MVS™ change options/suppress dump exit. The Fault Analyzer IDIXDCAP exit analyzes LE abends exactly the same way as the IDIXCEE exit. This similarity is because the exits do not actually do the analysis, they simply provide the method of invoking Fault Analyzer. It is the same Fault Analyzer analysis engine that runs for all Fault Analyzer exits, including CICS®.
For non-LE batch there are no known conflicts between Fault Analyzer and similar third-party products. However, it is recommended to specify the RETAINDUMP(ALL) option in the IDICNF00 parmlib member to ensure that similar third-party products that might rely on the MVS™ dump being taken for their invocation are not affected. Once Fault Analyzer is the only abend analysis product installed, then the RETAINDUMP(ALL) option can be removed.
The Fault Analyzer pre-abend (XPCABND) exit affects the CICS pre-transaction dump global user exit (XDUREQ). When invoked through the XPCABND exit, Fault Analyzer suppresses transaction dumps by default, and CICS does not invoke XDUREQ exit programs when transaction dumps are suppressed. If you require CICS to invoke the XDUREQ exit, use the Fault Analyzer RetainCICSdump(ALL) option.