Defining CICS system logs
Each CICS® region requires its own system log. The system log is implemented as two MVS™ system logger log streams - a primary and a secondary - but, together, they form a single logical log stream.
About this task
The system log is used for recovery purposes - for example, during dynamic transaction backout, or during emergency restart, and is not meant to be used for any other purpose.
CICS connects to its system log automatically during initialization (unless you specify a journal model definition that defines the system log as type DUMMY).
You
must define a system log if you want to preserve data integrity in the event
of unit of work failures and CICS failures. CICS needs a system log in order
to perform:
- The backout of recoverable resources changed by failed units of work.
- Cold starts when CICS needs to recover conversation state data with remote partners.
- Warm restarts, when CICS needs to restore the region to its pre-shutdown state.
- Emergency restarts, when CICS needs to restore the region to its pre-shutdown state as well as recovering transactions to perform the backout of recoverable resources changed by units of work that were in-flight at the time of shutdown.
For information on how to define CICS system log streams, see Coupling facility log streams and DASD-only log streams.