Home
Fault Analyzer installation and administration
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.
IDIUTIL control statements
SETFAULTPREFIX control statement
The SETFAULTPREFIX control statement specifies the PDS or PDSE history file data set name followed by the new prefix.

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
- 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.
  - IDIUTIL control statements
    - FILES control statement
      The FILES control statement specifies a list of PDS or PDSE history file data set names.
    - LISTHF control statement
      The LISTHF (LIST History File) control statement specifies a set of optional qualifiers to select which fault entries should be listed.
    - LISTHFDUP control statement
      The LISTHFDUP (list history file with duplicates) control statement can list all fault entries in a history file, as well as any duplicate occurrences of each fault.
    - DELETE control statement
      The DELETE control statement specifies qualifiers to select which fault entries should be deleted.
    - SETFAULTPREFIX control statement
      The SETFAULTPREFIX control statement specifies the PDS or PDSE history file data set name followed by the new prefix.
    - SETMAXFAULTENTRIES control statement
      The SetMaxFaultEntries control statement specifies a PDS history file data set name and the maximum number of fault entries to be set.
    - SETMINFAULTENTRIES control statement
      The SetMinFaultEntries control statement specifies a PDSE history file data set name and the minimum number of fault entries to be set.
    - IMPORT control statement
      The IMPORT control statement specifies the "to" PDS or PDSE history file data set name followed by the "from" data set name.
    - EXPORT control statement
      The EXPORT control statement can be used to create a portable copy of a fault entry, which includes both the fault entry itself and any associated dump data set.
    - EXITS control statement
      The EXITS control statement follows the same format as the Exits keyword for real-time analysis and reanalysis. The difference is that the exit points are for LISTHF, LISTHFDUP, DELETE, and IMPORT.
  - Examples
- 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

SETFAULTPREFIX control statement

The SETFAULTPREFIX control statement specifies the PDS or PDSE history file data set name followed by the new prefix.

Figure 1. Syntax

Description

data-set-name is the history file whose fault entry prefix characters are changed. prefix can be up to three characters. Only alphabetic prefix characters are permitted.

Prefixes for all existing fault IDs in the specified history file are changed to the specified prefix, and all fault IDs later created in this history file receive this prefix automatically.

Note: By default, this function is available to all users with UPDATE access to the history file. However, its usage can be restricted as explained in Restricting change of history file settings.

An example showing the use of the SETFAULTPREFIX control statement is provided in Example 5. Changing history file fault prefix characters.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.