Enabling interactive reanalysis under CICS

This feature is an optional feature. It allows the use of the Fault Analyzer ISPF interface to view history files and fault entries from a CICS® logon, without the need for a TSO logon.

Refer to Performing interactive reanalysis under CICS for information about using this interface.

Note: This feature requires the IBM Application Delivery Foundation for z/OS Common Components (which includes the required interactive panel viewer) to be installed.

It is recommended that a special CICS® region be set up for running Fault Analyzer in this mode to control the CPU and storage usage, without affecting other normal CICS® transactions. The reason is that in this mode, the Fault Analyzer analysis programs are running in attached subtasks in the CICS® region, and the JCL REGION= size needs to be large enough to accommodate the number of expected users concurrently logged on to run Fault Analyzer. The amount of storage needed varies depending on the size and complexity of the fault being analyzed, but a starting point of 32 megabytes per concurrent user is recommended. This storage is not CICS® DSA storage, and needs to be available to satisfy the MVS™ GETMAIN requests in the attached subtasks. That is, the estimated storage requirement (for example, 10x32M=320M) needs to be at least the difference between the REGION= size and the CICS® EDSALIM value.

The other setup requirements for a CICS® region to run Fault Analyzer as an interactive CICS® transaction are:

  1. Make the required CICS® resource definitions.
  2. Make the required CICS® JCL changes.

These requirements are described in the following sections. It is assumed that IDI is the data set name high-level qualifier that was used during Fault Analyzer installation.