The Fault Analyzer ISPF interface

At any time after an abend you can, as a TSO user, start the Fault Analyzer ISPF interface to review the fault. Using this interface you can:
  • View the stored real-time analysis report.
  • Start a batch reanalysis (for details, see Performing batch reanalysis).
  • Start an interactive reanalysis (for details, see Performing interactive reanalysis).
  • View information about the fault.
  • View details about any faults that might have occurred, that were deemed to be duplicates of the current fault.
  • Delete the fault entry.
The ISPF interface also permits you to:
Note: Whereas the information in this chapter assumes that the Fault Analyzer ISPF interface is invoked under ISPF, it is possible to instead invoke this interface under CICS®. When doing so, restrictions might apply. These restrictions are described in Performing interactive reanalysis under CICS.
Reanalysis: You can only perform reanalysis of a fault entry if it contains a minidump or is associated with an MVS dump data set.

Compiler listing or side file data sets that were allocated or specified via the DataSets option when the real-time analysis took place, are reused if performing reanalysis (if they are available in the reanalysis environment).

To make the reanalysis different from the initial real-time analysis, you must do one (or more) of the following:
  • Supply compiler listings (or side files) for the programs involved in the abend (if they were not available for the initial real-time analysis).
  • Change analysis options.
  • Use the interactive reanalysis to review dump storage.
The main differences between the batch and interactive reanalysis steps are:
  • Interactive reanalysis always provides full detail, and lets you look at storage locations that might not be included in the analysis report, whereas batch reanalysis provides the level of detail you ask for through the Detail option, and does not let you look at storage locations.
  • Interactive reanalysis ties up the use of an ISPF session, whereas once you submit batch reanalysis jobs you can get on with other things.

If you want to supply a listing or side file so that Fault Analyzer can provide source line information when it performs the fault reanalysis, you must compile the program and then store the compiler listing or side file. For more information on this process, see Providing compiler listings or Fault Analyzer side files.

If you have already created the listing or side file and are holding it in a non-standard storage location, you can use JCL DD statements to point to the location. Pointing to listings with JCL DD statements sets out possible values.