Maintaining Fault Analyzer

Fault Analyzer is maintained using the standard IBM® APAR/PTF service.
Note: For information about maintaining ADFzCC, see IBM Application Delivery Foundation for z/OS Common Components: Customization Guide and User Guide.

For the latest Fault Analyzer for z/OS service information, refer to

++APAR fixtests need never be restored, since they will either be superseded by a PTF, or a subsequent ++APAR fixtest will specify a later SMP/E REWORK date. However, it might be necessary to perform SMP/E restore and reapply of USERMODs if the maintenance causes a conflict.

Whenever maintenance has been applied to Fault Analyzer by means of SMP/E APPLY, or removed from Fault Analyzer by means of SMP/E RESTORE, perform the following steps:

Step 1: Remove libraries in LINKLIST from LLA and VLF control

If the following libraries are in LINKLIST, remove them from LLA and VLF control before performing the SMP/E APPLY:
  • Fault Analyzer SMP/E target libraries
  • Target libraries of any USERMODs provided by Fault Analyzer that update libraries in other products

Removing the libraries prevents errors that occur while loading the modules, when SMP/E has compressed or added extents to the libraries.

Step 2: IPL or update dynamically

IPL with CLPA. Alternatively, perform dynamic updates as follows:
  1. If the Fault Analyzer module IDIDA has been placed in LPA using the SETPROG command, as opposed to placing IDI.SIDILPA1 in LPA, then do the following:
    1. Issue the command:

      (For complete information on the use of the SETPROG command, refer to MVS System Commands.)

    2. Issue the command:
    Optionally, to add the module IDIDA to LPA again to regain the region size space advantage, issue the command:
  2. Otherwise, if IDI.SIDILPA1 is included in your LPALIST, issue this command:
  3. If using CICS®, refresh all installed CICS® exits. This refresh can be done by first uninstalling, and then reinstalling the exits, using the CFA transaction as described in Controlling CICS transaction abend analysis. There is no need to restart your CICS® region.
  4. Stop and restart the Fault Analyzer IDIS subsystem as described in Using the Fault Analyzer IDIS subsystem.
  5. Users of the Fault Analyzer ISPF interface should exit and re-enter ISPF for any updates to take effect.
  6. If you are using z/OS® V2.2 or later, refresh the IEAVTABX_EXIT by issuing the operator command:
    SET PROG=xx
    where xx matches the suffix of a PARMLIB PROGxx member that contains:

Step 3: Verify the service level (optional)

Information about Fault Analyzer installation status and applied maintenance is available through:
  • The Fault Analyzer ISPF interface Services->Service Information pull-down menu.
  • The IDICHKI utility, by submitting a job like this:
    //jobname JOB
The information provided by either method is similar, and includes:
IEAVTABX exit status
Tests the dynamic IEAVTABX exit, and reports an error on z/OS V2.2 if IDIXDCAP is statically defined to IEAVTABX. Displays no information for systems earlier than z/OS V2.2.
IEAVTSEL exit status
Reports if the Fault Analyzer post-dump exit is defined.
Fault Analyzer load modules
Presents the service information of important load modules.
CEEEXTAN and CEECXTAN exit information (Language Environment)
Checks whether various Fault Analyzer LE exits are defined.
IDIOPTLM information
Reports the contents of IDIOPTLM, if defined.