Format of journal record
Each CICS® journal record comprises a system header, system prefix, user prefix, and journaled data.


- JCRLL
- 2-byte length of record.
- X'0000'
- 2-bytes containing X'0000'.
- JCRSTRID
- 2-byte system-type identifier. For a user journal request, this is X'0000'. Otherwise, it consists of a 1-byte function ID followed by a 1-byte module ID.
- JCRUTRID
- 2-byte user-type identifier. For a CICS journal request, this is X'0000'. Otherwise, it contains the code specified by the JTYPEID keyword of the user request.
- JCRLRN
- 2-byte record number within the block.
The field JCRSTRID (the system-type ID) and the field JCRUTRID (the user-type ID) in the system header allow you to distinguish those journal records output by CICS (by such components as terminal control), from those issued by direct user requests.
For CICS journal requests, JCRUTRID contains binary zeros, and JCRSTRID contains a 1-byte function code followed by a 1-byte module code. The function code tells you which function was being journaled, and the module code shows which module caused the record to be written. Valid settings of these codes are contained in the member DFHFMIDS of the CICS assembler-language macro library. Figure 5 shows the valid function identifiers of those CICS components that issue journal requests. Figure 6 shows the valid module identifiers.
For user journal requests, JCRSTRID always contains binary zeros, and JCRUTRID contains the 2-byte hexadecimal code specified by the JTYPEID keyword of the WRITE JOURNALNAME request in the application program.

- JCSPLL
- 2-byte length of the system prefix.
- Reserved
- 2-byte reserved field.
- JCSPF1
- 1-byte flag field:
X'01' User prefix present X'02' Physical start-of-task, JCSPSOTK X'04' Logical start-of-task, JCSPLSTK - JCSPTASK
- 3-byte task number.
- JCSPTIME
- 4-byte time of request.
- JCSPTRAN
- 4-byte transaction identifier.
- JCSPTERM
- 4-byte terminal identifier.
For some CICS journal requests, additional data is included in the system prefix to identify more specifically the originator of the request. This extra data follows the common fields of the system prefix, and is usually variable in length; hence the need for the length field JCSPLL at the start of the system prefix. All the following have their own prefix layout, and these are described, for the purposes of diagnosis and recovery, in Data areas.

Field JCSPUP is set in the system prefix area if a user prefix is present in a journal record.
JCRLL - (system header (10) bytes + JCSPLL + user prefix)
Not all journal records contain journaled data.
***********************************************************************
* * F U N C T I O N I D E N T I F I E R S * *
***********************************************************************
* *
* X'20' PLUS X'8-' ...USE FOR AUTOMATIC JOURNALING *
* X'40' PLUS X'8-' ...USE FOR AUTOMATIC LOGGING *
***********************************************************************
* * JOURNAL CONTROL * *
***********************************************************************
FIDJCLAB EQU X'80' ...JOURNAL CONTROL LABEL
* RECORD (DFHJCR) *
***********************************************************************
* * FILE CONTROL * *
***********************************************************************
FIDALOG EQU X'40' ...AUTOMATICALLY LOGGED
FIDAJRN EQU X'20' ...AUTOMATICALLY JOURNALED
FIDMASS EQU X'10' ...MASSINSERT REQ. (FIDFCWA ONLY)
* PLUS ONE OF... *
FIDFCRO EQU X'80' ...FILE CONTROL READ-ONLY
FIDFCRU EQU X'81' ...FILE CONTROL READ-UPDATE
FIDFCWU EQU X'82' ...FILE CONTROL WRITE-UPDATE
FIDFCWA EQU X'83' ...FILE CONTROL WRITE-ADD
FIDFCWAC EQU X'84' ...FILE CONTROL WRITE-ADD-COMPLETE
FIDFCWD EQU X'86' ...FILE CONTROL WRITE DELETE
FIDFCBOF EQU X'88' ...BACKOUT FAILED LOG RECORD
FIDFCDSN EQU X'8F' ...DSNAME RECORD
* *
* NOTE THAT FID* VALUES (AS ABOVE) ARE OFTEN USED BOTH TO *
* IDENTIFY THE FUNCTION OF THE DWE AND THE FUNCTION OF THE *
* LOG RECORD. IN THE CASE OF THE FIDFC* EQU'S ABOVE, THEY *
* ARE USED FOR LOG RECORDS ONLY. THOSE BELOW APPLY ONLY *
* TO DWE'S *
* *
FIDFCVWA EQU X'80' THIS DWE ADDRESSES A VSWA.
FIDFCRVY EQU X'40' THIS DWE IS ASSOCIATED WITH A *
RECOVERABLE CHANGE.
***********************************************************************
* TERMINAL CONTROL FUNCTION IDENTIFIERS *
* *
FIDTCML EQU X'F0' SYNCPOINT - LOG SEQUENCE
* NUMBERS *
* CAN BE OR'ED WITH ANY OF *
THE FOLLOWING THREE FIELDS:
FIDTCDWL EQU X'01' ...DEFERRED WRITE DATA
FIDTCFMH EQU X'02' ...+ FUNCTION MANAGEMENT
* HEADER
FIDTCDIP EQU X'04' ...+ DIP REQUEST
* *
* EQU X'08' ...DYNAMIC BACKOUT MASK *
RESERVED
FIDTCAL EQU X'40' AUTOMATIC LOGGING MASK...
FIDTCAJ EQU X'20' AUTOMATIC JOURNALING MASK..
* ...THE ABOVE 2 PLUS 1 OF FOLLOWING SET *
FIDTCTL EQU X'80' ...SEQUENCE NUMBER ONLY
* (LOG ONLY) *
FIDTCIM EQU X'81' ...INPUT MESSAGE (LOG AND
* JOURNAL) *
FIDTCOM EQU X'82' ...OUTPUT MESSAGE (JOURNAL
* ONLY) *
FIDTCWP EQU X'83' ...WRITE WAS PURGED (LOG
* ONLY) *
FIDTCPRR EQU X'84' ...POSITIVE RESPONSE
* RECEIVED (LOG ONLY) *
FIDTCIMF EQU X'85' ...INPUT MESSAGE (W/FMH,
* LOG AND JOURNAL) *
FIDTCOMN EQU X'86' ...OUTPUT MESSAGE, (W/O
* FMH, JOURNAL ONLY) *
FIDTCON EQU X'87' ...OUTPUT MESSAGE, FMH,
* CCOMPL=NO *
FIDTCONN EQU X'88' ...OUTPUT MESSAGE, W/O FMH,
...CCOMPL=NO
FIDTCUA EQU X'89' ...INITIAL TCT USER AREA
FIDTCEIB EQU X'8A' ...INITIAL EXEC COMM AREA
FIDTCIMN EQU X'8B' INPUT MSG, NO FMH, COMPLETE
FIDTCINN EQU X'8C' INPUT MSG, NO FMH, INCOMPLETE
***********************************************************************
* FRONT END PROGRAMMING INTERFACE IDENTIFIERS *
FIDFEPIN EQU X'F0' FEPI INBOUND DATA API <--- FEPI
FIDFEPOU EQU X'F1' FEPI OUTBOUND DATA API ---> FEPI
***********************************************************************
***********************************************************************
* * M O D U L E I D E N T I F I E R S * *
***********************************************************************
* *
MODIDTC EQU X'10' ...TERMINAL CONTROL
MODIDFC EQU X'11' ...FILE CONTROL
MODIDJC EQU X'45' ...JOURNAL CONTROL
MODIDFEP EQU X'50' ...FEPI
* *
***********************************************************************
- Records created by automatic journaling and automatic logging are identified by values of X'20' (FIDAJRN) and X'40' (FIDALOG) respectively, added to the "base" value of the function identifier.
- A File Control write-delete record created by the forward recovery process (where the write-delete is done) has a function identifier of X'86' (FIDFCWD). However, if the record is created by the autojournal process it has a function identifier of X'A2', made up of X'82' (write-update or FIDFCWU) plus X'20' (FIDAJRN).