This document describes use of the trace function in batch, CICS with call interfaces, IMS and in CICS for the PL/I Wrapper.
To build a trace version for the scenarios
Batch and
CICS with Call Interfaces
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).
Compile and link the Trace Functions module (PLISRVT) to your
application.
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
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
Compile the Trace Functions module (PLISRVT).
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 Using the Generic RPC Services Module
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).
Link the Trace Functions module (PLISRVT) to the CICS Generic RPC
Services module (PLISRVIC).
