Checklist for installing and customizing Z Abend Investigator

In order to verify the installation of Z Abend Investigator, and to start using Z Abend Investigator at your site, you must perform the following tasks. Unless otherwise indicated, all tasks are mandatory.

Notes:
  • Copy all members of data set HFZ.SHFZSAM1 to another data set before proceeding, and make all changes to the copies only.
  • You can use the HFZCHKI utility to check the state of the Z Abend Investigator installation or to query service information. See Step 3: Verify the service level (optional).
  1. Make Z Abend Investigator modules available via LINKLIST and LPA

    For details, see Making Z Abend Investigator modules available.

  2. Allocate a history file

    Although multiple history files might eventually be used at your site, a single history file is sufficient to verify the installation of Z Abend Investigator.

    There are no restrictions on the name of the history file, but the default name searched for by Z Abend Investigator is HFZ.HIST. If a different name is used, then the HFZCNF00 parmlib member is used to provide the name through the DataSets option. You review the HFZCNF00 parmlib member, and the options it might contain, later in the installation process.

    A suggested size of the initial history file is 100 cylinders.

    General information about history files is provided in Setting up history files, along with considerations for choosing PDS or PDSE formats, and instructions for using the sample job provided for the data set allocation.

  3. Create the HFZCNF00 parmlib member

    For details, see Setting and changing default options for the site.

    Ensure that a 
    DataSets(HFZHIST(dsn))
    option is included if you allocated a history file with a name other than HFZ.HIST in step 2.

    Likewise, if Z Abend Investigator was installed using a high-level qualifier other than HFZ, use the DataSets option to provide the names of all required Z Abend Investigator data sets.

  4. Define and initialize the message and abend code explanation repository

    For details, see Setting up the message and abend code explanation repository.

  5. Install the MVS™ change options/suppress dump exit HFZXDCAP

    For details, see Installing the MVS change options/suppress dump exit HFZXDCAP.

    Information about the characteristics of this exit are provided in Exits for invoking Z Abend Investigator.

    At the completion of this step, Z Abend Investigator is effectively enabled at your site, and might start analyzing abends and creating entries in your history file.

  6. Enable the Language Environment® abnormal termination exit HFZXCEE

    For details, see Enabling the Language Environment abnormal termination exit (HFZXCEE or HFZXCE64).

    For information to help you determine the applicability of this exit at your site, see Exits for invoking Z Abend Investigator and Language Environment options required for invocation of Z Abend Investigator.

    If this exit is not installed, then abends in LE-enabled programs are only captured if the HFZXDCAP exit is installed, and the LE TERMTHDACT option with any of the UA* values (such as UATRACE or UADUMP) is in effect.

  7. Install the SVC dump registration exit HFZXTSEL

    For details, see Installing the MVS post-dump exit HFZXTSEL.

  8. Install USERMOD HFZTABD to eliminate the need for jobs to include an MVS™ dump DD statement

    For details, see Eliminating the need for a dump DD statement (++HFZTABD).

  9. Customize the CICS® environment

    This step is only applicable if you are using CICS®.

    For details, see Customizing the CICS environment.

  10. Customize the DB2® environment

    This step is only applicable if you are using DB2®.

    For details, see Customizing the DB2 environment.

    Create the DB2® table index discussed in Improving Z Abend Investigator DB2 performance; otherwise, severe Z Abend Investigator performance degradation might result when accessing DB2® catalog information.

  11. Customize the IMS™ environment

    This step is only applicable if you are using IMS™.

    For details, see Customizing the IMS environment.

  12. Customize for ISPF

    For details, see Modifying your ISPF environment.

  13. Start the Z Abend Investigator HFZS subsystem

    For details, see Using the Z Abend Investigator HFZS subsystem.

Optional installation steps

  1. Add BPX security server program control profile for Z Abend Investigator programs

    This step is only required if program control has been activated for your installation.

    For details, see Defining program control access to Z Abend Investigator programs.

  2. Install USERMOD HFZSPLI or HFZSPLIA to enable implicit Z Abend Investigator invocation from PL/I V2R3 applications

    For details, see Enabling implicit Z Abend Investigator invocation from PL/I V2R3 applications (++HFZSPLI/++HFZSPLIA).

  3. Change the default recovery fault recording IEATDUMP data set name using an HFZOPTLM configuration-options module (optional)

    For details, see Changing the default recovery fault recording IEATDUMP data set name (RFRDSN).

  4. Define XFACILIT resource classes to manage recovery fault recording data sets (optional)

    For details, see Managing recovery fault recording data set access.

  5. Provide XDUMP data set name and XFACILIT access (optional)

    This step is only required if your application is running AMODE 64 and you want to capture all of the programs' working storage, so that it is available during fault entry reanalysis. However, it also provides virtual storage constraint relief for reanalysis of fault entries with AMODE 24 or AMODE 31 programs.

    For details, see Extended minidump data set (XDUMP).

  6. Customize for Japanese language support

    This step is only required if the Japanese feature of Z Abend Investigator is installed.

    For details, see Customizing the Z Abend Investigator Japanese feature.

  7. Grant history file administrator authorization for change of settings via ISPF interface

    For details, see Restricting change of history file settings.

  8. Set SLIP traps to capture documentation for selected Z Abend Investigator error messages

    For details, see Setting Z Abend Investigator SLIP traps.

Additional customization can optionally be performed using user exits, as described in Customizing Z Abend Investigator by using user exits. However, no user exits are required for Z Abend Investigator to run.

Installation verification

  1. Perform assembler IVP

    For details, see Verifying the use of Z Abend Investigator with assembler.

  2. Perform COBOL IVP

    Only perform this step if COBOL is installed at your site.

    For details, see Verifying the use of Z Abend Investigator with COBOL.

  3. Perform PL/I IVP

    Only perform this step if PL/I is installed at your site.

    For details, see Verifying the use of Z Abend Investigator with PL/I.

  4. Perform HFZXCEE Language Environment® exit IVP

    For details, see Verifying the HFZXCEE Language Environment exit enablement.

  5. Perform HFZTABD USERMOD IVP

    For details, see Verifying the HFZTABD USERMOD installation.

  6. Perform CICS® IVP

    Only perform this step if CICS® is installed at your site.

    For details, see Verifying Z Abend Investigator customization under CICS.

  7. Perform DB2® IVP

    Only perform this step if DB2® is installed at your site.

    Both a C and a COBOL IVP is provided. For details, see Verifying the use of Z Abend Investigator with DB2.

  8. Perform ISPF IVP

    For details, see Verifying the use of Z Abend Investigator through ISPF.

  9. Verify Z Abend Investigator license status

    Inspect the SLCHK001 file in the output of the running job to verify that Z Abend Investigator is licensed to run.