Starting the HFZS subsystem

To start the Z Abend Investigator HFZS subsystem, a simple job as shown below can be submitted:

//HFZSS    JOB  …
//* (Optional DD statements might follow, as described below)


Specifies the region size to be used for the HFZS subsystem.

In most cases, a region size of 100 megabytes should be adequate (REGION=100M). However, if a very large number of history files are being managed by the HFZS subsystem, or if the history file sizes are very large, then it might be necessary to specify an even larger region size. For information about how to estimate the required region size, see HFZS subsystem storage requirements.

Specifies special options that are only used by the HFZS subsystem to disable some subsystem functions. Further options processing in the subsystem occurs through the standard HFZCNFxx parmlib member and the HFZOPTS DD statement, as described in Options. The optional PARM field specification can contain one of the following values for options:
Specifies that the HFZS subsystem is to manage the $$INDEX member access of all PDSE history files used on the same MVS™ image as where the HFZS subsystem is running, and to which the HFZS subsystem has UPDATE access. For details, see Caching of history file $$INDEX data.

This value is the default.

Specifies that the abending job performs all history file updates.
Note: Specifying NOUPDINDEX will disable the Z Abend Investigator Recovery Fault Recording (RFR) feature.
Enables IMS fast duplicate fault suppression specified using the NoDup(ImageFast(minutes,IMS(…))) option. For details, see NoDup.

This value is the default.

Disables IMS fast duplicate fault suppression, regardless of NoDup(ImageFast(…)) settings.
Enables fast Exclude options processing. For details, see Fast Exclude options processing.

This value is the default.

Disables fast Exclude options processing to revert back to normal Exclude processing by the HFZDA task.
Provides control over the last character, c, of the HFZS subsystem XCF messaging group name, HFZSXCFc, in order to create an alternative XCF message group. This creation would normally only be done if there are MVS images in a sysplex which do not share DASD and history files with the main HFZSXCFM default group, and would be set for the images that do not share DASD and history files. Each messaging group shares updates to the history files by data set name using the XCF messaging group.
Use the default "M" suffix. This value is the default.
Enables Java™ analysis. See HFZS subsystem requirements for Java for more information.
Disables Java analysis. This value is the default.
Enables the capture of SLIP dumps.
Disables the capture of SLIP dumps. This value is the default.

Multiple PARM field options must be delimited by one or more blank characters.

Alternatively, the HFZS subsystem can be established using a started task. The HFZS subsystem dynamically allocates data sets to SYSOUT=*, so it must be run under the job entry subsystem (JES).

Note: Ensure that the TIME=NOLIMIT parameter is specified as shown in the example above to prevent HFZS subsystem abend S522.

The subsystem name that is used by Z Abend Investigator for this subsystem is HFZS. This name does not need to be defined in the IEFSSNxx parmlib member as it is dynamically defined by the HFZSAMAN program.

The //HFZDOC2 DD statement is used to allocate the HFZ.SHFZDOC2 SMP/E target data set, which might contain updates to the Z Abend Investigator VSAM KSDS message and abend code explanation repository. If updates are available, and either the //HFZDOC2 DD statement has not been specified, or the high-level qualifier of the HFZ.SHFZDOC2 data set is not the same as the high-level qualifier of the HFZ.SHFZDOC1 data set identified via the DataSets(HFZDOC(…)) option, then message HFZ0165A is issued. If this situation occurs, then add the //HFZDOC2 DD statement as shown above.

Do not change the LE HEAPZONES option setting to anything other than HEAPZONES(0,…) when the HFZS subsystem is active.