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
    - Duplicate fault 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

Duplicate fault processing

Fault Analyzer provides two different types of duplicate fault processing, "fast" and "normal", where "fast" implies pre-analysis detection and "normal" implies post-analysis detection.

The "fast" duplicate fault type is further divided into two different subtypes, one at a CICS® region level and one that encompasses an entire MVS™ image. The latter is applicable to IMS™ only.

A fault that is not deemed a "fast" duplicate is still subject to "normal" duplicate processing.

The different types of duplicate processing are controlled using the NoDup option (for details, see NoDup). While the NoDup option description provides a detailed explanation of each type, the following is provided as a general overview for easier comparison.

Table 1. Duplicate processing type comparison
Aspect of processing	ImageFast	CICSfast	Normal
Controlled using option	NoDup(ImageFast( IMS(...)))	NoDup(CICSfast(...))	NoDup(Normal(...))
Applicable to	All faults that use IMS™, except CICS® transaction faults	Only CICS® transaction faults	All faults
Order of processing	1	1	2
Improves performance by suppressing fault analysis (that is, no IDIDA TCB attach)	Yes	Yes	No
Saves disk space by suppressing history file fault entry	Yes	Yes	Yes
Requires IDIS subsystem started	Yes	No	No
Duplicate signature repository location	IDIS subsystem storage	CICS® region storage	History file index
Default setting	Enabled, 5 minutes	Enabled, 5 minutes	Enabled, 24 hours

The number of duplicate faults that have occurred against a given history file fault entry is shown in the Fault Entry List display DUPS column (for details, see The Fault Entry List display).

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.