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:
- Creating audit trails
- Monitoring performance
- Controlling message security.
Table 1 shows the types of FEPI data that can be journaled.
| 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 2.
| 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.