Jump to main content

Product Documentation

Products
Support

IBM Fault Analyzer for z/OS User’s Guide and Reference V15.1.7

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

This version is no longer supported.

View the latest version.

A newer version of this product documentation is available.

View the latest version.

Home
Fault Analyzer installation and administration
Preparing to customize Fault Analyzer
Language Environment options required for invocation of Fault Analyzer
LE options required for CICS abends

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
  - Language Environment options required for invocation of Fault Analyzer
    - LE options required for non-CICS abends
    - LE options required for CICS abends
  - 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 Java 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

LE options required for CICS abends

There are no required LE options applicable to CICS® abends.

For CICS® trace considerations, see also Preventing LE from causing the CICS trace to wrap.

To add feedback about this topic, select the following checkbox:

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners Four, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site. Personal data should not be shared in this comment box. See our Privacy Statement to understand how personal data is used.

Generated by <oXygen/> XML WebHelp