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
  - 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.
    - Examples: Using IDIJAVA DD and IDIJAVA IDIOPTS
      This topic shows how to use IDIJAVA DD and IDIJAVA IDIOPTS to provide Java™ application source information to Fault Analyzer 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 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

Providing Java source information to Fault Analyzer

There are two options for providing Java™ application source information to Fault Analyzer.

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

Fault Analyzer searches for matching source files in each path specified in the IDIJAVA option or IDIJAVA DD concatenation.

If IDIJAVA paths were not specified or source files were not found, Fault Analyzer 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 Fault Analyzer 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 Fault Analyzer to ignore the application classpath when locating source files. Instead, only paths specified using the IDIJAVA option will be considered when locating source information.