GDDM V3R2 Diagnosis
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF | BOOK


Tracing output

GDDM V3R2 Diagnosis
SC33-0870-01



When a module is called, the entry and exit from the module always cause trace output if tracing is activated for that module. The return code is also output. A typical trace output looks like this:


       [01] (03) INTO GqfeInitFontFile
       [01] (04) EIFON:Font input name =
                     433A5C4F  53325C44  4C4C5C44  4953504C
                     41592E44  4C4C
       [01] (03) INTO GqfeGetPathNames
       [01] (04) Filename is:
                     433A5C43  4D4C4942  5C444C4C
       [01] (04) Filename is:
                     433A5C43  4D4C4942  5C
       [01] (03) LEAVING GqfeGetPathNames rc=00000000
       [01] (04) EIFON:Font base name =
                     433A5C43  4D4C4942  5C444C4C  5C475146
                     464F4E2E  444C4C
       [01] (04) EIFON:Font output name =
                     433A5C43  4D4C4942  5C475146  464F4E2E
                     464F4E
       [01] (15) INTO GqfzMakeFontFile
       [01] (15) ZMFON:Input file handle = 0000000D
       [01] (15) ZMFON:Input file date = 173C, time = 7397
       [01] (15) ZMFON:Input file size = 000454B0
       [01] (15) DosOpen C:\CMLIB\GQFFON.FON, rc=0
       [01] (15) ZMFON:Output file already exists
       [01] (15) ZMFON:Input file is unchanged, leaving
       [01] (15) LEAVING GqfzMakeFontFile rc=00000000
       [01] (03) LEAVING GqfeInitFontFile rc=00000000
       [01] (04) Saved GQF 3270 HostGraphics,GQF Common in OS2.INI
       [01] (03) LEAVING GqfeInitFontFile rc=00000000
       [01] (04) ECTL:Prime anchor 04E70008
       [01] (04) INTO GqfeGetTraceInfo
       [01] (04) EGTRC:Lancia Shared Seg addr = 1B170000
       [01] (04) EGTRC:trace flags addr=1B170553, setting=0
       [01] (04) EGTRC:comp name = HOSTGRAF
       [01] (04) LEAVING GqfeGetTraceInfo rc=00000000

The number in square brackets on the left-hand side, for example [01], shows the process to which the trace output belongs. This number also appears on the title bar of the corresponding trace options window. For example [01] appears on the title bar of Figure 6 in topic 7.4.3.2.

The indentation between INTO and LEAVING indicates the nesting level of the call. The number in parentheses on the left-hand side, for example (08), shows the trace point to which the trace output belongs.

Some modules also trace the value assigned to an important variable. Here is an example:


     [01] (15) ZMFON:Input file date = 173C, time = 7397

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

Go to the previous page Go to the next page



Copyright IBM Corporation 1990, 2012