Using Fault Analyzer
- Introduction
- Real-time analysis
  - Dump suppression
  - Fault history file selection
  - Controlling the real-time analysis with options
  - Pointing to listings with 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

Pointing to listings with JCL DD statements

No DD statements are required to run Fault Analyzer in either batch or real time. However, for versions of z/OS® prior to z/OS® 2.2, a SYSMDUMP, SYSUDUMP or SYSABEND DD statement is needed for normal MVS™ dump processing in real time when using the MVS™ IEAVTABX change options/suppress dump exit, IDIXDCAP, unless the IDITABD USERMOD is applied (see Eliminating the need for a dump DD statement (++IDITABD) for details about the effect of this USERMOD).

You can specify the following DD statements in the JCL if appropriate. If they are not specified, the definitions from the PARMLIB configuration member IDICNF00, the IDIOPTS user options file, or an Analysis Control user exit are used to identify these data sets:

IDILC: PDS or PDSE data set containing C compiler listings
IDILCOB: PDS or PDSE data set containing COBOL compiler listings (other than OS/VS COBOL)
IDILCOBO: PDS or PDSE data set containing OS/VS COBOL compiler listings
IDISYSDB: PDS or PDSE data set containing COBOL or Enterprise PL/I SYSDEBUG, or XL C/C++ MDBG side files.
IDILPLI: PDS or PDSE data set containing PL/I compiler listings (other than Enterprise PL/I)
IDILPLIE: PDS or PDSE data set containing Enterprise PL/I compiler listings
IDIADATA: PDS or PDSE data set containing SYSADATA from Assembler compilations
IDILANGX: PDS or PDSE data set containing LANGX side files for all languages

Do not specify a member name on any of the above DD statements. See Providing compiler listings or Fault Analyzer side files for further details on the use of these files.

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.