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

Extended minidump data set (XDUMP)

You can enable Fault Analyzer to allocate an extended minidump (XDUMP) data set and associate it with a history file fault-entry. An XDUMP data set is designed to contain:

64-bit storage pages
Application storage that is not directly involved with essential aspects of the analysis, such as program linkage or the point of failure

Fault Analyzer requires an XDUMP data set to save 64-bit storage pages and associate them with a fault entry. 64-bit storage pages are not included in a minidump.

For 24-bit and 31-bit applications, an XDUMP data set can provide relief from re-analysis storage constraints and reduce the likelihood of minidump suppression when the MaxMinidumpPages value is exceeded. (See MaxMinidumpPages.)

To enable Fault Analyzer to allocate an XDUMP data set, specify a valid data set name pattern in the XDUMPDSN setting of the IDIOPTLM configuration-options module. See Specifying the extended minidump data set name pattern (XDUMPDSN). Fault Analyzer allocates the data set with RECFM=FBS LRECL=4096 and uses the access authorization mechanism described in Managing XDUMP data set access. If XDUMP data set allocation fails, Fault Analyzer issues message IDI0184W.

An XDUMP data set is automatically deleted when its associated fault entry is deleted.

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.