Checklist for installing and customizing Fault Analyzer

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

1. Make Fault Analyzer modules available via LINKLIST and LPA

   For details, see Making Fault Analyzer 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 Fault Analyzer.

   There are no restrictions on the name of the history file, but the default name searched for by Fault Analyzer is IDI.HIST. If a different name is used, then the IDICNF00 parmlib member is used to provide the name through the DataSets option. You review the IDICNF00 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 IDICNF00 parmlib member

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

   Ensure that a

   DataSets(IDIHIST(dsn))

   option is included if you allocated a history file with a name other than IDI.HIST in step 2.

   Likewise, if Fault Analyzer was installed using a high-level qualifier other than IDI, use the DataSets option to provide the names of all required Fault Analyzer 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 IDIXDCAP

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

   Information about the characteristics of this exit are provided in Exits for invoking Fault Analyzer.

   At the completion of this step, Fault Analyzer 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 IDIXCEE

   For details, see Enabling the Language Environment abnormal termination exit (IDIXCEE or IDIXCE64).

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

   If this exit is not installed, then abends in LE-enabled programs are only captured if the IDIXDCAP 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 IDIXTSEL

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

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

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

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 Fault Analyzer DB2 performance; otherwise, severe Fault Analyzer 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 Fault Analyzer IDIS subsystem

    For details, see Using the Fault Analyzer IDIS subsystem.

14. Add entry in IFAPRDxx parmlib member

    For details, see Registering Fault Analyzer in the IFAPRDxx parmlib member.

Optional installation steps

1. Add BPX security server program control profile for Fault Analyzer programs

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

   For details, see Defining program control access to Fault Analyzer programs.

2. Specify the name of the LE runtime library using an IDIOPTLM configuration-options module (optional)

   For details, see Identifying the LE runtime library (LEDSN).

3. Install USERMOD IDISPLI or IDISPLIA to enable implicit Fault Analyzer invocation from PL/I V2R3 applications (optional)

   For details, see Enabling implicit Fault Analyzer invocation from PL/I V2R3 applications (++IDISPLI/++IDISPLIA).

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

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

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

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

6. 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).

7. Customize for Japanese language support

   This step is only required if the Japanese feature of Fault Analyzer is installed.

   For details, see Customizing the Fault Analyzer Japanese feature.

8. Customize for Korean language support

   This step is only required if the Korean feature of Fault Analyzer is installed.

   For details, see Customizing the Fault Analyzer Korean feature.

9. Install optional non-ISPF interfaces to access Fault Analyzer history files

   For details, see Installing non-ISPF interfaces to access Fault Analyzer history files.

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

    For details, see Restricting change of history file settings.

11. Review the chapter "Quick start guide for compiling and assembling programs for use with the ADFz family of products" in IBM Application Delivery Foundation for z/OS Common Components: Customization Guide and User Guide for information about steps required to prepare your programs for use with ADFz family of products.
12. Set SLIP traps to capture documentation for selected Fault Analyzer error messages

    For details, see Setting Fault Analyzer SLIP traps.

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

Installation verification

1. Perform assembler IVP

   For details, see Verifying the use of Fault Analyzer with assembler.

2. Perform COBOL IVP

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

   For details, see Verifying the use of Fault Analyzer 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 Fault Analyzer with PL/I.

4. Perform IDIXCEE Language Environment® exit IVP

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

5. Perform IDITABD USERMOD IVP

   For details, see Verifying the IDITABD USERMOD installation.

6. Perform CICS® IVP

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

   For details, see Verifying Fault Analyzer 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 Fault Analyzer with DB2.

8. Perform ISPF IVP

   For details, see Verifying the use of Fault Analyzer through ISPF.