Trace

Trace entries are made on entry to and exit from DFHAPLI.

Point IDs AP 1940 to AP 1945, with a trace level of PC 1, correspond to these trace entries.

The function information is always interpreted.

For entry trace records, the program name and link level are also interpreted where applicable.

For exit trace records, the returned reason code is interpreted.

Also, all calls into and out of the language environments are traced at level 1. The point IDs are: AP1948 to AP 1952.

For more information about the trace points, see the CICS® Trace Entries. For more information about using traces in problem determination, see the CICS Problem Determination Guide.

(The CICS Trace Entries includes tables that show, for entry and exit trace records, the ERTLI function together with any other data items traced.)

The ERTLI function named in the DFHAPLI entry trace is the function requested on the call, while that named in the DFHAPLI exit trace is the ERTLI function most recently processed. There are some situations in which a trace record made on entry to DFHAPLI is not matched by a corresponding exit trace for the same ERTLI function. In particular, after making a call to Language Environment® for thread initialization, DFHAPLI does not return to the caller, but proceeds with "run-unit initialization" and "run-unit begin invocation" before finally returning. Another example is the successful execution of a "perform GOTO" function, which results in DFHAPLI not returning to the caller.

Note:
ERTLI refers to the Extended Run-Time Language Interface. This is an extension of the Run-Time Language Interface (RTLI) protocols that were defined to assist communication between CICS and both VS COBOL II and C/370. ERTLI includes communication between CICS and Language Environment.
[[ Contents Previous Page | Next Page Index ]]