Taking and interpreting trace entries

FEPI supports only one level of tracing. At CICS initialization, you can specify the default levels of standard and special tracing using the STNTR, SPCTR, STNTRSZ, and SPCTRSZ system initialization parameters.

1. You can start tracing using either of these methods:
   • Use the CETR transaction. The FEPI component code on the CETR “Component Trace Options” panel is ‘SZ’. Specify ‘SZ 1’ to turn on FEPI tracing.

     You can use the selection features of the CETR transaction to limit tracing to specific transactions rather than using the SZ component. If you do this, you can control the tracing of application programs. The FEPI Resource Manager, running as the CSZI transaction, is unaffected, because trace selection is applied only at transaction start.

   • Use the following command: SET TRACETYPE SZ.
2. Check if there are any exception trace entries.
   Their presence indicates that a problem has been detected. Exception trace entries are either initialization errors or storage management errors.
   1. Initialization errors result from checks made when CSZI starts, to prevent a second instance of the FEPI Resource Manager.
   2. Storage errors result from GETMAIN or FREEMAIN errors, and are usually caused by a lack of CICS storage.
3. Other trace entries are the usual module entry and exit traces, together with a few points indicating that important processing events have occurred (such as the FEPI Resource Manager becoming idle).