Home
Fault Analyzer installation and administration
Setting up history files
Fault Analyzer requires at least one PDS or PDSE data set to be allocated as a fault history file.
Managing history files across MVS systems without shared DASD
Views can be used for easy access to fault entries in more than one history file. However, this easy access is only possible when all history files in a view are accessible from the same MVS™ system.

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.
  - Determining what size history files to allocate
  - Allocating a PDS or PDSE for a history file
    To allocate one or more history files, edit and submit the sample job IDISHIST.
  - Allocating secondary space for history files
    For PDSE history files in particular, it is important to allocate the data set with secondary space. Failure to do so might result in out-of-space conditions with subsequent loss of data.
  - Converting history files between PDS and PDSE
  - AUTO-managed PDSE history files
    By default, a newly created PDSE history file is AUTO-managed.
  - Changing the size of a PDSE history file
    You can change the allocated size of a PDSE history file.
  - Providing the name of a history file to Fault Analyzer
  - Setting up views
  - Managing history files across MVS systems without shared DASD
    Views can be used for easy access to fault entries in more than one history file. However, this easy access is only possible when all history files in a view are accessible from the same MVS™ system.
    - Automated implementation
      Given two MVS™ systems, A and B, which do not share DASD, fault entries that are created on system A can be copied automatically to system B for viewing or reanalysis by using the Fault Analyzer ISPF interface.
    - On-demand implementation
      You can use a Formatting user exit to transmit fault entries that match certain criteria to another system for analysis. This process is initiated as required from within the interactive reanalysis report.
  - Sharing of history files across a sysplex
    Fault Analyzer uses XCF messaging from IDIS subsystems to efficiently share PDSE history files across all MVS™ images in a sysplex.
  - Managing history file fault entry access
- 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

Managing history files across MVS systems without shared DASD

Views can be used for easy access to fault entries in more than one history file. However, this easy access is only possible when all history files in a view are accessible from the same MVS™ system.

If the systems share DASD, they can simply use a common history file. Two other solutions are provided for sending fault entries from the system on which the fault occurred to another system for analysis:

The first solution uses the Notification user exit and requires no manual intervention. See Automated implementation.
The second solution uses the Formatting user exit to transmit fault entries "on demand" during interactive reanalysis. See On-demand implementation.