FEPI journaling

This section describes the format of FEPI journal records, and how to print them. For background information about CICS® journaling, you should refer to the CICS Operations and Utilities Guide; for programming information, see the CICS Customization Guide.

FEPI journal operation

You can request FEPI to write inbound, outbound, or both inbound and outbound data to a specified CICS user journal; you cannot write to the system log. This is done using the MSGJRNL, FJOURNALNUM, and FJOURNALNAME options in your property set definitions.

Of the various reasons for using CICS journaling, the following are particularly relevant to FEPI processing:

Table 6 shows the types of FEPI data that can be journaled.

Table 6. FEPI journaled data
FEPI command Data flow Type
SEND Outbound Data stream
Formatted, screen image
Formatted, key stroke
RECEIVE Inbound Data stream
Formatted, screen image
CONVERSE Outbound Data stream
Formatted, screen image
Formatted, key stroke
CONVERSE Inbound Data stream
Formatted, screen image
EXTRACT FIELD Inbound Extract field data

The records journaled by FEPI are identified in the usual way by module and function identifiers. These are listed in Table 7.

Table 7. FEPI journal record identifiers
Identifier-type Name Value Type of data
Module identifier MODIDFEP X'5D' Identifies FEPI records in the journal
Function identifiers FIDFEPIN
FIDFEPOU
X'F0'
X'F1'
Identifies FEPI inbound data
Identifies FEPI outbound data

In order to identify the conversation for which the data was journaled, FEPI provides a prefix area in the journal record.

Printing FEPI journal records

You can select FEPI journal records in any of the ways described in the CICS Operations and Utilities Guide; programming information about this is in the CICS Customization Guide.

Each FEPI journal record contains a prefix area which contains FEPI-related information. See the CICS Customization Guide for details on the structure of journal records. The FEPI prefix area lies within the API user header, as shown in Figure 8.

Figure 8. Format of the API user header, showing the position of the prefix area
 The picture shows the format of the API user header, whose fields are listed below.

CL_UH_LENGTH
4-byte length of header
CL_UH_JOURNAL_TYPE
2-byte journal type
Reserved
2-byte reserved field
CL_UH_PREFIX_LENGTH
4-byte length of prefix
Prefix area
The variable length prefix
User data
Variable length user data

The exact format of this FEPI prefix area is shown in Figure 9.

Figure 9. Format of the FEPI prefix area
 The picture shows the format of the FEPI prefix area, whose fields are described below.
UP_MODFN
1-byte module function.
UP_SVMID
1-byte module identifier.
UP_FEPDF
1-byte data function.

Field UP_FEPDF can take any of the following values:

Table 8. Values of UP_FEPDF
Field name Value Meaning
UP_FEPDD 1 Datastream
UP_FEPDS 2 Formatted, screen image
UP_FEPDK 3 Formatted, keystroke
UP_FEPDE 4 Extract field data
UP_FEPES
1-byte escape character for keystroke.
Reserved
2-byte reserved field.
UP_FEPPL
8-byte pool name.
UP_FEPTG
8-byte target name.
UP_FEPCV
8-byte conversation identifier.
Reserved
4-byte reserved field.

See the CICS Operations and Utilities Guide for examples of ways in which you can use the CICS-supplied utility program, DFHJUP, to select FEPI records for printing.

[[ Contents Previous Page | Next Page Index ]]