Jump to main content
IBM Logo Product Documentation
  • Products
  • Support
IBM Fault Analyzer for z/OS User’s Guide and Reference V15.1.6
  • PDF documentation
  • About this document
  • Summary of changes
  • Using Fault Analyzer
  • Fault Analyzer installation and administration
  • Fault Analyzer reference information
  • Sample customized ISPF interface front-end
  • Java API to download Fault Analyzer report
  • Technical details for screen size adjustments
  • Support resources
  • Accessibility features for Fault Analyzer
  • Notices
  • Glossary
  1. Home
  2. Fault Analyzer installation and administration
  3. Preparing to customize Fault Analyzer
  4. Exits for invoking Fault Analyzer
  5. Invocation for non-CICS transaction abends
  6. Summary of exit usage
 Go to Feedback
  • Fault Analyzer installation and administration
    • Migrating from an earlier version of Fault Analyzer
    • Preparing to customize Fault Analyzer
      • Checklist for installing and customizing Fault Analyzer
      • Library names after you finish installing
      • Storage recommendations
      • Exits for invoking Fault Analyzer
        • Invocation for non-CICS transaction abends
          • Summary of exit usage
        • Invocation for CICS transaction abends
        • SVC dump registration
      • Language Environment options required for invocation of Fault Analyzer
      • Running Fault Analyzer with similar third-party products
      • MVS dump data set size
      • Application-handled error conditions
      • Setting Fault Analyzer SLIP traps

        As documentation for certain situations where Fault Analyzer issues an error message, an MVS™ dump is often required by IBM® Support.

    • 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
    • Customizing the CICS environment
    • Customizing the DB2 environment
    • Customizing the IMS environment
    • Customizing the Fault Analyzer Japanese 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

Summary of exit usage

Summary of Fault Analyzer non-CICS (batch) invocation exit usage shows the exit used to invoke Fault Analyzer, depending on execution environment and options in effect.
Figure 1. Summary of Fault Analyzer non-CICS (batch) invocation exit usage

Illustration of non-CICS (batch) invocation exit usage.

Generated by <oXygen/> XML WebHelp