Module

GDDM V3R2 Diagnosis

Module

GDDM V3R2 Diagnosis
SC33-0870-01

When a module is called, the entry to and exit from the module always causes a trace output if tracing is activated for that module. The trace output looks like this:

02 INTO GQDEDRV : 09 INTO GQDYLEV : 09 LEAVING GQDYLEV - RC=0000 : 02 LEAVING GQDEDRV - RC=0000

The indentation of INTO and LEAVING indicates the nesting level of the call. The number on the left-hand side shows to which trace point the trace output belongs.

Many modules give the requested function (why the module was called) and the return code:

02 INTO GQDEDRV 02 DRV - Init : 02 LEAVING GQDEDRV - RC=0000

In this example, module GQDEDRV was called for initialization (Init) and ended successfully (RC=0). To find out what module a trace output is from, use the trace point ID on the left-hand side (for example, 02 is GQDE component), and the last three letters of the module name shown (for example, DRV).

All the other module trace records depend on the module.

The return code from a DOS function call is often traced. Some modules trace the value assigned to an important variable with the variable name. Here is an example:


     03  PTF - DOSFIRST RC = 00
     03  PTF - file_count = 0008

A big module often traces the flow of process as follows:

07 STC - Initializing ODP 07 STC - Initializing PRT 07 STC - Setting Host Session Number 07 STC - Loading XHGI Driver 07 STC - Initializing GDP 07 STC - Initializing BPP

There are other types of trace output depending on the modules; they are mainly self-explanatory.

Notices | Terms of use | Support | Contact z/OS