Welcome
Z Abend Investigator installation and administration
Setting up history files
Z Abend Investigator requires at least one PDS or PDSE data set to be allocated as a fault history file.
Managing history file fault entry access
Using the XFACILIT resource class for history file fault entries
If the required access to a history file fault entry is not already available via normal data set profiles, you can use the XFACILIT resource class to provide the access through Z Abend Investigator.
Using the HFZXFXIT user exit
Example (C)

PDF documentation
About this document
Summary of changes
Using Z Abend Investigator
Z Abend Investigator installation and administration
- Migrating from an earlier version of Z Abend Investigator
- 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.
  - Determining what size history files to allocate
  - Allocating a PDS or PDSE for a history file
    To allocate one or more history files, edit and submit the sample job HFZSHIST.
  - Allocating secondary space for history files
    For PDSE history files in particular, it is important to allocate the data set with secondary space. Failure to do so might result in out-of-space conditions with subsequent loss of data.
  - Converting history files between PDS and PDSE
    When converting history files from PDS to PDSE data sets, or from PDSE to PDS data sets, set the minimum or maximum fault entries values. Failure to do this might cause unexpected results, including out-of-space conditions.
  - AUTO-managed PDSE history files
    By default, a newly created PDSE history file is AUTO-managed.
  - Changing the size of a PDSE history file
    You can change the allocated size of a PDSE history file.
  - Providing the name of a history file to Z Abend Investigator
  - Setting up views
  - Managing history files across MVS systems without shared DASD
    Views can be used for easy access to fault entries in more than one history file. However, this easy access is only possible when all history files in a view are accessible from the same MVS™ system.
  - Sharing of history files across a sysplex
    Z Abend Investigator uses XCF messaging from HFZS subsystems to efficiently share PDSE history files across all MVS™ images in a sysplex.
  - Managing history file fault entry access
    - Using the XFACILIT resource class for history file fault entries
      If the required access to a history file fault entry is not already available via normal data set profiles, you can use the XFACILIT resource class to provide the access through Z Abend Investigator.
- 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 Java 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
- Z Abend Investigator on VS Code
  HCL Z Abend Investigator is a host component and supports a client that supports various interfaces such as Microsoft Visual Studio Code IDEs.
Z Abend Investigator reference information
Sample customized ISPF interface front-end
Technical details for screen size adjustments
Notices
Glossary

Example (C)

The following is an example of an HFZXFXIT exit that is written in C.


#include "HFZSXPLC"
int HFZXFXIT(char *action, char *userid, char *group, char *jobnm,
             char *histDSN, DDIR_DATA_HD *pHD) {
  if (strcmp("MY.HIST", histDSN) == 0) return 2;  /* Update access ok */
  else return 0 ;                                 /* No access */
}