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 file fault entry access

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.
  - 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
    - Using the XFACILIT resource class for history file fault entries
      If the required access to a history file fault entry is not already available via normal data set profiles, you can use the XFACILIT resource class to provide the access through Fault Analyzer.
- 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 file fault entry access

It is possible to manage access to history files using security server data set profiles only, for example if a given history file is only used within a single department where all users are equal with regards to access authority. In this case, all users typically have at least UPDATE access to the history file and are thus able to create new fault entries, as well as view, modify, or delete any existing fault entries, regardless of who created them.

If more control over access to individual fault entries is required, then Fault Analyzer supports the use of the XFACILIT resource class as described in the following.

Note: Because XFACILIT access is associated with some degree of processing overhead, you might want to use history files with normal data set profile access for performance critical applications, such as CICS® or IMS™.