Using Fault Analyzer
- Introduction
- Real-time analysis
  - Dump suppression
  - Fault history file selection
  - Controlling the real-time analysis with options
  - JCL DD statements
  - The real-time analysis report
  - The SYSLOG summary
  - Using the program SNAP interface (IDISNAP)
    - IDISNAP invocation
  - Invoking Fault Analyzer from a Java try-catch block
    To capture the current Java™ state from a Java program, Fault Analyzer can be invoked to create a history file fault entry, along with an associated MVS™ SVC dump.
  - Invoking Fault Analyzer from Java dump events
  - Using the Fault Analyzer Java wrapper utility
    Fault Analyzer Java wrapper utility wraps a callable Java application in a try-catch block by using the FA Java class.
  - Using the Fault Analyzer JVMTI Agent
    Fault Analyzer provides a JVMTI (JVM Tool Interface) agent. The agent runs inside a Java™ Virtual Machine (JVM) and can inspect the state of the running Java application.
  - Dump registration processing
  - Real-time exclusion processing
  - Recovery fault recording
  - Using SLIP,COMP=0C4 with Fault Analyzer
  - Extended minidump data set (XDUMP)
  - Abend traps can prevent fault analysis
  - Capturing and displaying the abending job JCL
    When the JCLcapture option is in effect during real-time processing, Fault Analyzer attempts to obtain the JCL and save it in the fault entry. This feature is available with JES2 only.
- The Fault Analyzer ISPF interface
- Performing batch reanalysis
- Performing interactive reanalysis
- Performing CICS system abend dump analysis
- Formatting a CICS auxiliary trace data set
- Performing Java analysis
- The Fault Analyzer report
- Using non-ISPF interfaces to access Fault Analyzer history files

Using the program SNAP interface (IDISNAP)

A program SNAP interface is provided to assist users in debugging problems with applications that do not abend, or that for any other reason cannot be analyzed by Fault Analyzer using one of the normal abend invocation exits described in Exits for invoking Fault Analyzer. This interface permits a call to Fault Analyzer from anywhere within an application program to request an analysis of the current environment. For 24-bit and 31-bit programs, the program SNAP interface module name is IDISNAP. For 64-bit programs, the module name is IDISNAP6.

An example of where a call to IDISNAP might be used is in a DB2® application after execution of an SQL statement that results in a negative SQLCODE.

Apart from the way in which Fault Analyzer is invoked, there is no difference between this type of analysis and any other real-time analysis caused by an abend.

This exit can extract WTO console messages related to the current job from the master trace table and include these messages in the analysis report, except when running under CICS.

It is recommended that you invoke IDISNAP dynamically to ensure that you are always using the most current version:

If the invoking program is compiled with the DLL option, then invocations of IDISNAP need to be STATIC rather than DYNAMIC.
For programs written in C, IDISNAP can only be invoked dynamically.