Fault reanalysis

The reanalysis process is essentially identical to the real-time analysis process, except for the following:
Figure 1 illustrates the reanalysis process.
Figure 1. Reanalysis
Diagram faoug002_HCL illustrates reanalysis: The user initiates reanalysis from either the ISPF interface or by submitting their own batch job. Z Abend Investigator either reads an existing fault entry from a history file or a SYSMDUMP data set, as well as possible compiler listings or side files for source level support, and generates an analysis report. The ISPF interface also allows the user to view the saved report in the fault entry.

If an MVS dump data set is associated with the fault entry, then the fault history entry holds the dump data set name in case it is required during reanalysis or user-selected display of storage locations that are not included in the minidump. If the dump data set is not available, then you can still perform reanalysis using the minidump which is included in the history file entry. If neither a minidump nor an associated MVS dump data set exists for a given fault, then you cannot initiate reanalysis, but you can still look at the real-time analysis report from the ISPF interface.

For the reanalysis, you can make a listing (or a side file) available, if one was not available when the real-time analysis was performed. Z Abend Investigator is now able to provide the source statement information relevant to the abend.

Fault reanalysis can be performed in two different ways: batch or interactive. Both methods can be initiated using the Z Abend Investigator ISPF interface.