Home
Fault Analyzer installation and administration
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.
Starting the IDIS subsystem
IDIS subsystem requirements for Java
Specifying an IDIJLIB DD statement

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.
  - Sysplex-wide subsystem inter-communication
    Multiple IDIS subsystems in a sysplex interface with one another using the Cross-system Coupling Facility (XCF) to allow efficient sharing of subsystem-managed data, such as the caching of $$INDEX data.
  - Caching of history file $$INDEX data
  - Starting the IDIS subsystem
    - IDIS subsystem storage requirements
    - IDIS subsystem requirements for DB2
    - IDIS subsystem requirements for Java
      - Specifying an IDIJLIB DD statement
      - Specifying a default JVM for Java dump analysis
        Performing Java™ dump analysis requires a JVM that has a service level equal to, or greater than, the JVM that recorded the Java dump. Optional DD statements can specify default JVMs to use when the version of Java indicated by the dump JAVA_HOME path cannot be found on the system.
    - IDIS subsystem requirements for deletion of migrated tightly-coupled associated dump data sets
  - Stopping the IDIS subsystem
    The IDIS subsystem can be stopped and restarted at any time.
- 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 Java 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

Specifying an IDIJLIB DD statement

An optional IDIJLIB DD statement can be included in the IDIS subsystem JCL for Java™ as follows:


//IDIJLIB  DD   PATH='path'

The IDIJLIB JCL statement specifies a target directory for HFS executables. The IDIS subsystem writes a small number of program files to this directory as part of its execution, thus the IDIS subsystem must have authority to read, write, and execute files in the specified directory. Additionally, diagnostic information might also be written to this path. The path name is case sensitive and the path must exist. An example of a possible specification is PATH='/u/user-id/idij', where user-id is the user ID under which the IDIS subsystem is running.

Note:

If specified, the IDIJLIB path is also used for deletion of migrated tightly-coupled associated dump data sets. For details, see IDIS subsystem requirements for deletion of migrated tightly-coupled associated dump data sets.

If IDIJLIB is not provided, then the default path for the IDIS subsystem user ID is used. In this case, if the IDIS subsystem user ID does not have a valid default path, message IDI0155W is issued.

For each image in a sysplex, Fault Analyzer creates a subdirectory of the IDIJLIB path, using the &SYSCLONE name. This naming ensures that each image writes to a separate directory.