GenerateSavedReport

Figure 1. Syntax

1! NOGENERATESAVEDREPORT
1  GenerateSavedReport?  (
2.1 Override
2.1 NoOverride
1 )
1 NOGenerateSavedReport

The GenerateSavedReport option can be used to create or replace a saved report in a fault entry during reanalysis.

If the Override suboption is used, then a new saved report is generated, regardless of whether one already exists or not.

If the NoOverride suboption is used, then a saved report is generated only if one does not already exist. This value is the default if the GenerateSavedReport option is specified without a suboption.

If the GenerateSavedReport option is in effect, then source information data sets (compiler listings or side files) used during real-time processing are automatically included during the reanalysis.

A practical application of this option might be to use it with automated batch reanalysis of newly created fault entries, which due to the DeferredReport option having been in effect during real-time processing for performance reasons, do not already include a saved report. By, for example, submitting such a batch reanalysis job from a Notification user exit, a saved report can be made to exist prior to users issuing the 'V' or 'S' line command from the Fault Entry List display. A sample Notification user exit which can be used for this purpose has been provided in Example 4.

If the GenerateSavedReport option is used with batch analysis of an MVS™ dump data set specified using the DumpDSN option, then this option causes a fault entry to be created in the current history file, subject to the user's access authorization. If the fault entry is to be created in a history file, other than the default history file, then the history file can be designated using any of the normal methods, such as specifying an HFZHIST DD statement or using the DataSets(HFZHIST(dsn)) option. If a fault entry is successfully created, then message HFZ0164I is issued.