Jump to main content

Product Documentation

Products
Support

IBM Fault Analyzer for z/OS User’s Guide and Reference V14.1.21

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

Home
Fault Analyzer installation and administration
Customizing the DB2 environment

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
- Customizing the CICS environment
- Customizing the DB2 environment
  - Binding DB2
    To run Fault Analyzer against abends occurring in applications that use DB2®, you must ensure that the DB2 Call Level Interface (CLI) is installed and the required setup has been performed to bind plan DSNACLI.
  - DB2 and Language Environment
  - Improving Fault Analyzer DB2 performance
- 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

Customizing the DB2 environment

This section contains information specific to Fault Analyzer in DB2® environments.

Binding DB2
To run Fault Analyzer against abends occurring in applications that use DB2®, you must ensure that the DB2® Call Level Interface (CLI) is installed and the required setup has been performed to bind plan DSNACLI.
DB2 and Language Environment
Improving Fault Analyzer DB2 performance

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Share: Email
Twitter

Disclaimer
Privacy
Terms of use
Cookie Preferences