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.
- 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
  - COBOL Report Writer Precompiler
  - Required compiler options for HFZLANGX
  - Naming compiler listings or side files
    Store compiler listings or side files in sequential data sets, or as members of PDS or PDSE data sets.
  - Creating side files with the HFZLANGX utility
    The HFZLANGX utility program converts a compiler listing or SYSADATA file to a LANGX side file.
  - Formatting side files with the HFZLANGP utility
    The HFZLANGP utility can create a readable listing from a LANGX side file, from a SYSDEBUG side file, or from the DWARF debugging information in a program object. This utility can be useful if your installation conserves DASD space by keeping side files rather than compiler listings. The output from the utility resembles the original compiler listing.
  - Naming CSECTs for Z Abend Investigator
    To facilitate source code information, Z Abend Investigator must be able to match CSECT names with the compiler listings or side files provided.
  - Locating compiler listings or side files
  - Using the HFZXSFOR compiler listing/side file search and override exit
    If the HFZXSFOR exit is available, Z Abend Investigator invokes it to allow programmatic specification of the location of compiler listing or side file data.
  - Compiler listings and side file attributes
  - Using the HFZRLOAD DDname for CSECT mapping
  - HFZDATST side file availability test utility
  - ISPF-packed compiler listings
  - Providing Java source information to Z Abend Investigator
    There are two options for providing Java™ application source information to Z Abend Investigator.
    - Examples: Using HFZJAVA DD and HFZJAVA HFZOPTS
      This topic shows how to use HFZJAVA DD and HFZJAVA HFZOPTS to provide Java™ application source information to Z Abend Investigator in different scenarios.
    - Compiling Java for optimal debugging
      The type and amount of debug information included within a compiled .class file depends upon the defaults of the build tool and the explicitly specified debug options.
    - Generating debugging information with common Java build tools
      There are many approaches for building large Java™ applications. Each of the common build tools including Apache Ant, Maven, and Gradle have different ways that debug flags must be specified for debug information to be included.
- 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

Providing Java source information to Z Abend Investigator

There are two options for providing Java™ application source information to Z Abend Investigator.

The HFZJAVA option or DD concatenation
Specifying source jars on the Java™ classpath

Z Abend Investigator searches for matching source files in each path specified in the HFZJAVA option or HFZJAVA DD concatenation.

If HFZJAVA paths were not specified or source files were not found, Z Abend Investigator searches in each explicitly specified jar file and directory for source files that match the application events.

Optimizing Java source information

If Java source is never required or never available, specify the NOSOURCE option to tell Z Abend Investigator not to look for matching Java™ source files. If source jar files or Java™ source files are not on the application class path, specify the -dropcp- option to tell Z Abend Investigator to ignore the application classpath when locating source files. Instead, only paths specified using the HFZJAVA option will be considered when locating source information.