User journals and automatic journaling
User journals and autojournals are written to a general log stream defined to the MVS™ system logger.
- User journaling is entirely under your application programs' control. You write records for your own purpose using EXEC CICS® WRITE JOURNALNAME commands. See Flushing journal buffers for information about CICS shutdown considerations.
- Automatic journaling
means that CICS automatically
writes records to a log stream, referenced by the journal name specified
in a journal model definition, as a result of:
- Records read from or written to files. These records represent
data that has been read, or data that has been read for update, or
data that has been written, or records to indicate the completion
of a write, and so on, depending on what types of request you selected
for autojournaling.
You specify that you want autojournaling for VSAM files using the autojournaling options on the file resource definition in the CSD. For BDAM files, you specify the options on a file entry in the file control table.
- Input or output messages from terminals accessed through the z/OS® Communications Server.
You specify that you want terminal control autojournaling on the JOURNAL option of the profile resource definition referenced by your transaction definitions. These messages could be used to create audit trails.
Automatic journaling is used for user-defined purposes; for example, for an audit trail. Automatic journaling is not used for CICS recovery purposes.
- Records read from or written to files. These records represent
data that has been read, or data that has been read for update, or
data that has been written, or records to indicate the completion
of a write, and so on, depending on what types of request you selected
for autojournaling.