Using CICS trace for problem determination

CICS® provides tracing that enables you to trace transactions through the CICS components and through your own programs. You can either define the tracing levels at system initialization or use a CICS-supplied transaction to define tracing when CICS is running.

About this task

To define tracing when CICS is running, use the CETR transaction.

Procedure

  1. Use the CETR transaction to run level 1 auxiliary tracing for the BTS domains. BTS consists of three CICS domains: the Business application manager domain, the Event manager domain, and the Scheduler services domain. You can trace what is happening in BTS using the component codes for these domains to specify the level of standard and special tracing for BTS. The component codes are as follows:
    Domain name CICS component code
    Business application manager BA
    Event manager EM
    Scheduler services SH
    This tracing provides you with information about the BTS processes and activities that are running in the CICS region.
  2. Use the CETR transaction to run level 1 auxiliary tracing for the following domains:
    • AP - application programming domain
    • PG - program manager domain
    This tracing provides you with information about the programs that are running and the contents of the BTS data-containers. CICS SFR also performs user tracing to trace the entry and exit of the modules that are called during request processing. See Trace points.
  3. If you are having problems with Web services in particular, use the CETR transaction to run level 1 auxiliary tracing for the PI domain. CETR traces what is happening in the pipeline when a service requester invokes a service flow from a Web service, or if a service flow makes an outbound Web service request.


btstrace.html | Timestamp icon Last updated: Sunday, 4 June 2017