Segmented entries on GTF

CICS trace entries can be split into several entries in the GTF data set, because there is a 256-byte restriction on GTF entry length. However, in a formatted GTF trace, CICS reconstructs the segmented entries to ensure that all the entries for any region are formatted completely and correctly. This makes the segmentation of the entries transparent.

In the GTF data set, the segmented entries might be interleaved in the following ways:
  • Header and continuation entries of different types of trace might be interleaved.
  • Records from different CICS regions that write to the same GTF data set might be interleaved.
To format a GTF trace, CICS uses 4 KB buffers to reconstruct the segmented entries. For each type of trace there can be up to five 4 KB buffers for reconstructing the entries. The reconstructed trace entries appear in order of completion, and so they might be out of time sequence.
GTF entries with the CICS format ID X'EF' are written from parts of CICS that run asynchronously with the mainline code, as well as from the trace domain itself. The source of the entry is identified by the type byte in TREN_TYPE in the entry header. See DFHTREN in Data areas for a full description of the trace entry header.
Type      Source of entry
 00         TR domain
 01         not used
 02         DFHMNSVC
 03         normal CICS z/OS Communications Server exit
 04         CICS z/OS Communications Server LERAD/SYNAD exit
 05         CICS z/OS Communications Server TPEND exit
 06         CICS z/OS Communications Server HPO exit
 07         CICS z/OS Communications Server HPO LERAD/SYNAD exit


dfhs3c001038.html | Timestamp icon Last updated: Monday, 5 June 2017