This document describes use of the trace function in batch, CICS with call interfaces, and IMS for the PL/I Wrapper.

• Using Trace in Batch, CICS with Call Interfaces, and IMS

• Using Trace in CICS

---

Using Trace in Batch, CICS with Call Interfaces, and IMS

To build a trace version for the scenarios Batch and CICS with Call Interfaces

1. Set the preprocessor switch ERXTRACE in file RPCPPS (PL/I Preprocessor Settings) to "YES" before you compile the generated interface objects and provided sources (see corresponding step in scenarios Batch and CICS with Call Interfaces).

2. Compile and link the Trace Functions module (PLISRVT) to your application.

Using Trace in CICS

For the scenario Using the PL/I Wrapper for CICS you can trace every interface object and the Generic RPC Services module individually. Interface objects with trace and without trace can coexist.

To trace generated interface objects

1. Set the preprocessor switch ERXTRACE in file RPCPPS (PL/I Preprocessor Settings) to "YES" before you translate and compile the following: (see corresponding step in scenario CICS)

   • the interface object you want to trace

   • the Specific RPC Functions module (PLISRVS) you link into the interface object you want to trace

2. Compile the Trace Functions module (PLISRVT).

3. Link the Trace Functions module (PLISRVT) to the interface object you want to trace.

Compile and link interface objects you do not want to trace with ERXTRACE set to "NO".

To trace the generic RPC services module

1. Set the preprocessor switch ERXTRACE in file RPCPPS (PL/I Preprocessor Settings) to "YES" before you translate and compile (see corresponding step in scenario CICS) the CICS Generic RPC Services module (PLISRVIC) and the Trace Functions module (PLISRVT).

2. Link the Trace Functions module (PLISRVT) to the CICS Generic RPC Services module (PLISRVIC).