TREN - Trace entry

Applicable releases

6.2

     ==================================================================
      CONTROL BLOCK NAME = DFHTREN
      NAME OF MATCHING ASM CONTROL BLOCK = DFHTREN
      DESCRIPTIVE NAME = CICS trace entry
           PID 5655-YA1
           Copyright IBM Corp. 1986, 2023
      FUNCTION = Description of header of CICS trace entry.
      LIFETIME = Created by DFHTRPT in the internal trace table for
                 each TRACE_PUT. Destroyed when overwritten after
                 the next trace table wrap. Trace entries are also
                 held on auxiliary trace datasets and GTF datasets.
      STORAGE CLASS = Held in the internal trace table in MVS storage.
      LOCATION = Each trace table block contains a block header
                 followed by as many entries contiguously as will
                 fit in the rest of the block.
      INNER CONTROL BLOCKS = None
      NOTES :
         DEPENDENCIES = S/370
         RESTRICTIONS = None
         MODULE TYPE = Control block definition
     ------------------------------------------------------------------
      EXTERNAL REFERENCES = None
          DATA AREAS = None
          CONTROL BLOCKS = None
          GLOBAL VARIABLES (Macro pass) = None
     ------------------------------------------------------------------
           Change the following line for co-req dummy changes
           B3170 750 231102 HDPFRJM : Dummy change for co-req
     ==================================================================
Table 1.
Offset Hex Type Len Name (Dim) Description
(0) STRUCTURE * DFHTREN Trace entry
(0) CHARACTER 40 TREN_HEADER Standard header
(0) CHARACTER 2 TREN_MARKER Eyecatcher '<>'
(2) UNSIGNED 2 TREN_LEN Length of entry inc. header
(4) UNSIGNED 2 TREN_CALLER Domain id of trace caller
(6) UNSIGNED 2 TREN_POINTID ID of trace point in domain
(8) UNSIGNED 1 TREN_TYPE Entry type
(8) 1... ....   * The Top bits are used
(8) .1.. ....   * for the release of the
(8) ..1. ....   * trace.
(8) ...1 ....   *
(8) .... 1...   * The Bot Bits are used for
(8) .... .1..   * the type. The types are
(8) .... ..1.   * listed below.
(8) .... ...1   *
(9) BIT(24) 3 TREN_TASK Transaction manager task num
(C) UNSIGNED 2 TREN_KE_NUM Kernel task number
(E) UNSIGNED 2 TREN_OWNING_DOM Owning domain for system task
(10) UNSIGNED 2 TREN_HEADER_LENGTH Length of this header Offset of TREN_HEADER_LENGTH must not change. Add new header fields after this field
(12) CHARACTER 5 TREN_TCB_ID TCB ID
(17) UNSIGNED 1 TREN_CPU_TYPE CPU (CP, zAAP, zIIP)
(18) ADDRESS 4 TREN_TCBADDR TCB address
(1C) ADDRESS 4 TREN_RETADDR Addr of call to trace caller
(20) CHARACTER 8 TREN_TIME Time of entry - 8 byte STCK
(28) CHARACTER * TREN_DATA Trace data
(28) UNSIGNED 2 TREN_FIELD_LEN Length of data field
(2A) CHARACTER * TREN_FIELD_DATA Data field

Constants

Table 2.
Len Type Value Name Description
   ==================================================================
     Tren type constants.
     The Top Bits of TREN_TYPE will be used for the release.
             X'3?' equals R750
             X'2?' equals R740
             X'1?' equals R730
             X'0?' equals R720
             X'F?' equals R710
             X'E?' equals R700
             X'D?' equals R690
             X'C?' equals R680
             X'B?' equals R670
             X'A?' equals R660
             X'9?' equals R650
             X'8?' equals R640
             X'7?' equals R630
             X'6?' equals R620
             X'5?' equals R610
     These values are now being reused by the later releases and so
     are commented out below and are left here for future reference
             X'4?' equals R530
             X'3?' equals R520
             X'2?' equals R510
             X'1?' equals R410
             X'0?' equals R330 and below
     The Bottom Bits of TREN_TYPE will be used for the trace type.
     The types below will need to be updated for release.
     For example, the release after 5.1.0 will have the top bits
     set like this '2?'X.
     A new release field will also be added to the bottom.
     If a new TREN_TYPE is added, be sure to change GTF_TYPE_NUM
     in DFHTRFCA.
   ==================================================================
1 HEX 30 TREN_TYPE_NORMAL
1 HEX 3E TREN_TYPE_LE_PIPI_EXIT
1 HEX 3D TREN_TYPE_RRS_CALL
1 HEX 3C TREN_TYPE_RRMS_EXIT
1 HEX 3B TREN_TYPE_DB2_SUBTASK
1 HEX 3A TREN_TYPE_DBCTL_ RESUME_EXIT
1 HEX 39 TREN_TYPE_RLS_QUIESCE_ EXIT
1 HEX 38 TREN_TYPE_EXCI
1 HEX 37 TREN_TYPE_LERADSYNAD_ HPO
1 HEX 36 TREN_TYPE_VTAM_EXIT_ HPO
1 HEX 35 TREN_TYPE_TP_END
1 HEX 34 TREN_TYPE_LERAD_SYNAD
1 HEX 33 TREN_TYPE_VTAM_EXIT
1 HEX 32 TREN_TYPE_MONITORING
1 HEX 31 TREN_TYPE_SDUMP_EXIT
1 HEX 30 TREN_TYPE_R750
1 HEX 20 TREN_TYPE_R740
1 HEX 10 TREN_TYPE_R730
1 HEX 00 TREN_TYPE_R720
1 HEX F0 TREN_TYPE_R710
1 HEX E0 TREN_TYPE_R700
1 HEX D0 TREN_TYPE_R690
1 HEX C0 TREN_TYPE_R680
1 HEX B0 TREN_TYPE_R670
1 HEX A0 TREN_TYPE_R660
1 HEX 90 TREN_TYPE_R650
1 HEX 80 TREN_TYPE_R640
1 HEX 70 TREN_TYPE_R630
1 HEX 60 TREN_TYPE_R620
1 HEX 50 TREN_TYPE_R610 R133871C