Defining system log streams

You must define a system log if you want to preserve data integrity in the event of unit of work failures and CICS® failures .

About this task

A system log is mandatory for the following processes:
  • The backout of recoverable resources changed by failed units of work
  • Cold starts, to enable CICS to restore units of work that were shunted at the time of the shutdown
  • Warm restarts, to enable CICS to restore the region to its state at the previous shutdown, including units of work that were shunted at the time of the shutdown
  • Emergency restarts, to enable CICS to:
    • Restore the region to its state at the previous shutdown, including units of work that were shunted at the time of the shutdown
    • Recover units of work that were in-flight at the time of the CICS failure, and perform backout of recoverable resources that were updated before the failure

CICS log manager connects to its log stream automatically during system initialization, unless it is defined as TYPE(DUMMY) in a CICS JOURNALMODEL resource definition.

Although the CICS system log is logically a single logical log stream, it is written to two physical log streams—a primary and a secondary. In general, it is not necessary to distinguish between these, and most references are to the system log stream. Using a primary and a secondary log stream for its single system log enables CICS to optimize its use of log stream storage through its process of moving long-running UOWs from the primary to secondary logstreams.



dfht21d.html | Timestamp icon Last updated: Sunday, 4 June 2017