Fault Analyzer installation and administration
- Migrating from an earlier version of Fault Analyzer
- Preparing to customize Fault Analyzer
- Customizing the operating environment for Fault Analyzer
- Using the Fault Analyzer IDIS subsystem
  Fault Analyzer uses a subsystem known as IDIS for services that can otherwise not be performed or which might cause incomplete analysis if not started.
- Modifying your ISPF environment
- Customize Fault Analyzer by using USERMODs
- Customize Fault Analyzer by using an IDIOPTLM configuration-options module
- Setting up history files
  Fault Analyzer 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 Fault Analyzer side files
  - COBOL Report Writer Precompiler
  - Required compiler options for IDILANGX
    - TEST option considerations
    - DEBUG option considerations
    - Limitations when using COBOL NOTEST(DWARF,SOURCE)
      If PTF UI60153 has not been installed and COBOL programs are compiled with NOTEST(DWARF,SOURCE), the compiler does not include cross-reference information in the DWARF.
    - Limitations when using PL/I TEST(NOSEPARATE NOSOURCE)
      When NOSOURCE is specified and program source is not available, source line numbers and storage areas are still reported.
  - 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.
  - Naming CSECTs for Fault Analyzer
    To facilitate source code information, Fault Analyzer must be able to match CSECT names with the compiler listings or side files provided.
  - Locating compiler listings or side files
  - Using the IDIXSFOR compiler listing/side file search and override exit
    If the IDIXSFOR exit is available, Fault Analyzer invokes it to allow programmatic specification of the location of compiler listing or side file data.
  - Compiler listings and side file attributes
  - Using the IDIRLOAD DDname for CSECT mapping
  - IDIDATST side file availability test utility
  - ISPF-packed compiler listings
  - Providing Java source information to Fault Analyzer
    There are two options for providing Java™ application source information to Fault Analyzer.
- Customizing the CICS environment
- Customizing the DB2 environment
- Customizing the IMS environment
- Customizing the Fault Analyzer Japanese feature
- Customizing the Fault Analyzer Korean feature
- Verifying Fault Analyzer customization
- Managing history files (IDIUTIL utility)
  The IDIUTIL 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 Fault Analyzer
- Disabling Fault Analyzer
- Customizing Fault Analyzer by using user exits
- Installing non-ISPF interfaces to access Fault Analyzer history files

Limitations when using PL/I TEST(NOSEPARATE NOSOURCE)

When NOSOURCE is specified and program source is not available, source line numbers and storage areas are still reported.

TEST(SEPARATE) and TEST(NOSEPARATE SOURCE) are equivalent, the former locates source in a separate SYSDEBUG side file, the latter in the program object.