JOURNALMODEL resources

A JOURNALMODEL resource defines the connection between a CICS® journal name (or identifier) and the associated physical log streams managed by the MVS™ system logger, or between the journal name and the SMF log.

Although they are intended mainly for user journals, you can also define journal models for the system log and forward recovery logs (non-RLS only). However, for forward recovery logs, you are recommended to define all log stream names for forward recovery in the VSAM catalog. This is mandatory for VSAM files processed in RLS mode, but optional for non-RLS mode files.

Unlike the journal control table, you do not need to define a journal model for every journal that CICS uses. Instead, define some generic model definitions that describe the mapping to log stream names for the majority of your CICS journals. You may find that you can use the default models supplied by CICS and need not define any of your own. In addition to generic models, you can define the necessary specific models where special handling is required (for example, SMF logging, or merging with other log streams).

You can change JOURNALMODEL definitions at any time, but any journal entries that CICS has already created using model definition cannot reflect the change unless you first delete the existing entry using a DISCARD JOURNALNAME() command.

Compatibility note: For API compatibility with releases earlier than CICS Transaction Server for z/OS®, CICS continues to support numeric journal identifiers in the range 01 through 99, for the following purposes:
  • For file control autojournaling, as specified in FILE resources (or for BDAM files, on DFHFCT macro entries)
  • For terminal control autojournaling, as specified in PROFILE resource definitions
  • For forward recovery logging, as specified in FILE resources
  • For user journaling using API journal commands, such as the EXEC CICS WRITE JOURNALNUM command.