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
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.
XFACILIT implementation example 3: Using ACF2

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
  - 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
- 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

XFACILIT implementation example 3: Using ACF2

OEM security servers need the commands converted to the specific product, such as the following ACF2 commands. The requirement is that the SAF RACROUTE requests give the equivalent return information for the OEM product, as would happen with RACF®. The following is an example for ACF2.

$KEY(TEST)
 ZZ.HISTORY.- UID(<string for MVS support>) READ(A) WRITE(A) ALLOC(A) EXEC(A)
 ZZ.HISTORY.- UID(*)

Here, the TEST.ZZ.HISTORY.* history files can only be directly accessed by the users in the <string for MVS™ support> list.

$KEY(IDIHIST_USERID_DSN) TYPE(XFC) or $KEY(IDIHIST_GROUP_DSN) TYPE(XFC)
 -.TEST.ZZ.HISTORY.- UID((<string for MVS support>) ALLOW
 -.TEST.ZZ.HISTORY.- UID(*) SERVICE(READ,UPDATE) ALLOW

TYPE(XFC) is the default for XFACILIT class. This setup only allows general users READ and UPDATE access, only MVS™ support can do explicit delete of fault entries. Automatic deletion is still done by Fault Analyzer according to the SetMaxFaultEntries/SetMinFaultEntries setting of each history file.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

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 immixGroup, 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 IBM Software Support site.