This topic summarizes the requirements, and the steps that you need to follow, to set up the CICS® logging environment. Some of the steps listed have a pointer to sections that provide more detailed information. These steps cover both MVS™ and CICS system programmer tasks and some security administrator tasks, and close cooperation between all groups is needed:
See Coupling facility or DASD-only?, to help you decide on one of these or a combination of both.
As part of the planning phase:
DASD-only log streams can be shared only within the same MVS image.
For information about types of coupling facility, see the z/OS MVS Setting Up a Sysplex. Note that the minimum level of coupling facility supported by the MVS system logger is CFLEVEL=1, with the appropriate service level of the coupling facility control code that supports CFLEVEL=1.
See The log stream sizing utility, DFHLSCU for more information.
The removal of the 168 data set limit (described in General logs) also requires the LOGR data set to be formatted with DSEXTENT(nnnnn). This does not apply to LOGR couple data sets formatted for DASD-only logging.
See Defining coupling facility structures for details, including a sample job.
SUBSYS SUBNAME(LOGR) INITRTN(IXGSSINT)
Consider the following parameters:
In particular, consider the following when defining your log streams:
For user journals and the log of logs, specify LOWOFFLOAD as 0.
See Defining coupling facility log streams for some sample IXCMIAPU jobs, and see z/OS MVS Setting Up a Sysplex for general information about updating LOGR policies.
See the CICS Transaction Server for z/OS Migration from CICS TS Version 2.3 for CICS TS Version 1 Releases 1 and 2 for information about obsolete parameters and function relating to the old CICS journal control function and other migration information
This parameter now represents the number of write operations (log records) by CICS log manager to the log stream buffer before an activity keypoint is taken, whereas under the old journal control program it specifies the number of consecutive blocks written to the system log data set.
The parameter has a significant impact on the size of system logger primary (interim) storage, affecting the log tail management that takes place during activity keypoint (AKP) processing. The system logger:
The following topics provide more detailed information to help you with the above steps: