The MaxMinidumpPages option specifies the maximum number of 4K pages that can be saved as a minidump in each history file fault entry.

Read syntax diagramSkip visual syntax diagram


If the use of an XDUMP data set has been enabled, some of the storage pages referenced during real-time analysis might be written to an associated XDUMP data set, while the rest are written to the fault entry minidump. If the use of an XDUMP data set has not been enabled, all referenced pages are written to the fault entry minidump.

A fault entry minidump is required to perform reanalysis of a fault entry created during real-time processing of Z Abend Investigator.

If the number of referenced pages destined for the minidump exceeds max_pages, then a fault entry with a saved report is still created, but it will not include a minidump, nor will it have an XDUMP data set associated with it.

Note: Additional minidump pages resulting from storage referenced during execution of a Formatting user exit are not included in the number of minidump pages tested against this option, nor are these included in the number of minidump pages provided as input to an End Processing user exit.

The MaxMinidumpPages option does not cause any preallocation of storage or DASD space. It is simply a cut-off mechanism to prevent minidumps above a specified size from being written with the history file fault entry. This option applies to real time processing or batch reanalysis of MVS dump data sets with option GenerateSavedReport in effect.

The section of the fault analysis report that shows options in effect includes this option and further indicate if the limit was exceeded, and if so, by how many pages. If it was exceeded, then message HFZ0052I is also issued.

The valid max_pages range is 0 - 524288.

Note: The use of an Analysis Control or End Processing user exit can effectively override the MaxMinidumpPages option in effect.