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.
Setting up views
Specifying a default column layout
A default column layout can be specified by using the -HistCols keyword in column 1 of any record in a view.

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
    When converting history files from PDS to PDSE data sets, or from PDSE to PDS data sets, set the minimum or maximum fault entries values. Failure to do this might cause unexpected results, including out-of-space conditions.
  - 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
    - Specifying a default column layout
      A default column layout can be specified by using the -HistCols keyword in column 1 of any record in a view.
    - Specifying initial fault entry selection criteria
      Initial fault entry selection criteria can be specified by using the -Match keyword in column 1 of any record in a view.
    - View considerations if not using XFACILIT resource class
  - 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
- 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
- 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

Specifying a default column layout

A default column layout can be specified by using the -HistCols keyword in column 1 of any record in a view.

Tip: Avoid specifying this on the first record if a view description is also required.

Following the -HistCols keyword, must be a list of Fault Entry List display columns enclosed in parenthesis. The syntax and format of the column name list is the same as for the FAISPFopts(HistCols(...)) option (see FAISPFopts). An easy way to obtain the column name list is to cut and paste from an actual Fault Entry List display where the columns have been configured as desired from the Fault Entry List Column Configuration display (see Fault entry list column configuration).

The complete -HistCols specification must fit on a single view member record. Continuation over multiple records is not supported.

No part of the -HistCols specification is case sensitive, including the keyword itself, and any number of blank characters, or none, can precede the open parenthesis following the keyword.

If multiple -HistCols specifications are found in a single view member, then only the last one takes effect.

Here is an example of a view data set member specifying a default column layout.

* All IMS history files
-HistCols(IMS_Pgm  Jobname  User_ID  System   Abend Date       Time    )
SYS1.IMS.HIST
SYS2.IMS.HIST