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)
  - 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

Fault history file selection

When a fault is being analyzed in real time by Fault Analyzer, a history file must be available in which details of the analysis can be recorded.

There are a number of ways in which the name of the history file can be provided to Fault Analyzer. The following is a list of these in the order of their override significance (each entry in the list overrides all previous entries):

The product default name, IDI.HIST.
The IDIHIST suboption of a DataSets option that is specified in the parmlib config member, IDICNF00. This information includes either the logical parmlib concatenation or the installation-wide alternate parmlib data set name provided via the IDIOPTLM configuration-options module IDICNF setting. For details, see Customize Fault Analyzer by using an IDIOPTLM configuration-options module.
The IDIHIST suboption of a DataSets option that is specified in a config member identified via the IDICNFUM user options module.
Note: If a user options module is used, it replaces the default IDICNF00 parmlib config member. Thus, even if the user options module designated config member did not include an IDIHIST suboption of a DataSets option, any specification of IDIHIST in the default IDICNF00 parmlib config member would not be recognized.
The IDIHIST suboption of a DataSets option provided via the IDIOPTS DDname in the abending job step.
An explicitly coded IDIHIST DD statement in the abending job step.
The data set name provided by an Analysis Control or End Processing user exit in the ENV data area IDIHIST field.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.