Home
Z Abend Investigator installation and administration
Using the Z Abend Investigator HFZS subsystem
Z Abend Investigator uses a subsystem known as HFZS for services that can otherwise not be performed or which might cause incomplete analysis if not started.
Starting the HFZS subsystem
HFZS subsystem requirements for Java
Specifying an HFZJLIB DD statement

Z Abend Investigator installation and administration
- Preparing to customize Z Abend Investigator
- Customizing the operating environment for Z Abend Investigator
- Using the Z Abend Investigator HFZS subsystem
  Z Abend Investigator uses a subsystem known as HFZS for services that can otherwise not be performed or which might cause incomplete analysis if not started.
  - Sysplex-wide subsystem inter-communication
    Multiple HFZS subsystems in a sysplex interface with one another using the Cross-system Coupling Facility (XCF) to allow efficient sharing of subsystem-managed data, such as the caching of $$INDEX data.
  - Caching of history file $$INDEX data
  - Starting the HFZS subsystem
    - HFZS subsystem storage requirements
    - HFZS subsystem requirements for DB2
    - HFZS subsystem requirements for Java
      - Specifying an HFZJLIB DD statement
      - Specifying a default JVM for Java dump analysis
        Performing Java™ dump analysis requires a JVM that has a service level equal to, or greater than, the JVM that recorded the Java dump. Optional DD statements can specify default JVMs to use when the version of Java indicated by the dump JAVA_HOME path cannot be found on the system.
  - Stopping the HFZS subsystem
    The HFZS subsystem can be stopped and restarted at any time.
- Modifying your ISPF environment
- Customize Z Abend Investigator by using USERMODs
- Customize Z Abend Investigator by using an HFZOPTLM configuration-options module
- Setting up history files
  Z Abend Investigator requires at least one PDS or PDSE data set to be allocated as a fault history file.
- Setting and changing default options for the site
- Providing compiler listings or Z Abend Investigator side files
- Customizing the CICS environment
- Customizing the DB2 environment
- Customizing the IMS environment
- Customizing the Z Abend Investigator Japanese feature
- Verifying Z Abend Investigator customization
- Managing history files (HFZUTIL utility)
  The HFZUTIL batch utility can be used to perform history file management functions, such as listing and deleting history file fault entries.
- Providing application-specific explanations and descriptions
- Maintaining Z Abend Investigator
- Disabling Z Abend Investigator
- Customizing Z Abend Investigator by using user exits

Specifying an HFZJLIB DD statement

An optional HFZJLIB DD statement can be included in the HFZS subsystem JCL for Java™ as follows:


//HFZJLIB  DD   PATH='path'

The HFZJLIB JCL statement specifies a target directory for HFS executables. The HFZS subsystem writes a small number of program files to this directory as part of its execution, thus the HFZS subsystem must have authority to read, write, and execute files in the specified directory. Additionally, diagnostic information might also be written to this path. The path name is case sensitive and the path must exist. An example of a possible specification is PATH='/u/user-id/hfzj', where user-id is the user ID under which the HFZS subsystem is running.

If HFZJLIB is not provided, then the default path for the HFZS subsystem user ID is used. In this case, if the HFZS subsystem user ID does not have a valid default path, message HFZ0155W is issued.

For each image in a sysplex, Z Abend Investigator creates a subdirectory of the HFZJLIB path, using the &SYSCLONE name. This naming ensures that each image writes to a separate directory.