Stopping the HFZS subsystem

The HFZS subsystem can be stopped and restarted at any time.

When the HFZS subsystem is inactive (stopped), only basic Z Abend Investigator processes continue to run, such as the creation of new fault IDs. SVC dump registration, Recovery Fault Recording (RFR), Java DTFJ processing, some DB2® catalog data access and deletion of migrated tightly-coupled dump data sets will not work. There is also an increase in CPU and I/O usage, compared to having the HFZS subsystem running with PARM='UPDINDEX'.

Attention:

Never use the CANCEL command to stop the HFZS subsystem.

To permit normal termination, use a MODIFY command to stop the HFZS subsystem by, for example: F name,STOP or P name

where name is the appropriate identifier for the MODIFY command, depending on how the HFZS subsystem was started.

If either the HFZS subsystem is not active, or if an incorrect identifier was used on the MODIFY command, MVS™ issues the message:

IEE341I XYZ               NOT ACTIVE

If the HFZS subsystem is already active when another attempt to start it is performed, the following message is issued to the operator console:

HFZSAMAN The Z Abend Investigator Subsystem is already active in jobname job-id

where jobname is the job or started task name of the currently executing HFZS subsystem and job-id is the JES job or started task ID.