The caller data

Caller data follows the record header. The format of the caller data part of a general log journal record differs according to the CICS® component writing the record, and the function being journaled.

Journal records can be written by any of the following CICS components: the logger, journal control (in the case of a request issued by a user), file control, the front end programming interface (FEPI), and terminal control. The field GLRH_REC_COMPID in the record header tells you which component has written the record: LG, UJ, FC, SZ, or TC respectively.

File control adds information to the start of the actual journaled data, and this is described in Caller data written by file control. The other components (journal control, FEPI, and terminal control) do not add any further information to the journaled data.

The API user header

If the record has been written by the CICS API, the caller data section starts with an API user header, the format of which is shown in Figure 1.
Figure 1. Format of the API user header
This fields in this picture are described in the list that follows.
CL_UH_LENGTH
4-byte header length.
CL_UH_JOURNAL_TYPE
2-byte journal type.
Reserved
2-byte reserved field.
CL_UH_PREFIX_LENGTH
4-byte prefix length.
Prefix
Variable-length prefix area.
User data
Variable-length user data.