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

Dump registration processing

Unlike the SYSABEND, SYSMDUMP, and SYSUDUMP processes, which run in the user address space, the SVC dump process in MVS™ runs from the DUMPSRV address space. This difference means that the MVS™ change options/suppress dump exit, which is one of the normal means of invoking Fault Analyzer, does not work for SVC dumps. For SVC dumps, Fault Analyzer provides the MVS™ post-dump exit IDIXTSEL. SVC dumps occur for system abends, and are also used by CICS® for its system dumps.

If you install the MVS™ post-dump exit IDIXTSEL, a "skeleton" fault entry is created whenever an SVC dump is written. For more information about installing the MVS™ post-dump exit IDIXTSEL, see Installing the MVS post-dump exit IDIXTSEL. This processing differs from normal real-time processing in that no analysis is performed, and therefore no report or minidump is produced. This Fault Analyzer process is known as "dump registration".

The dump registration processing permits the use of two user exits which effectively are the equivalent of the normal Analysis Control and Notification user exits. These are specified using the DumpRegistrationExits option (see DumpRegistrationExits).

The dump registration fault entry contains only limited information, such as the time of its creation, the system name, and the name of the job that caused the SVC dump to be written. If available, the abend code and abending program name is also provided. However, the first reanalysis of the dump registration fault entry refreshes the fault entry and save a report and minidump with it. For details, see Refresh processing.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the IBM Software Support site.