Managing the size of log streams

This section describes how to manage the size of logs.

System log

Normally, you should allow the CICS® log manager to manage the size of the system log. You should not need to take explicit action to delete redundant data, nor to retain data--all system log data required on a restart is presented, providing the necessary completed unit of work information. If you do need to retain system log data beyond the time it would normally be deleted by CICS, see the CICS Transaction Server for z/OS® Installation Guide for advice on how to define your system log.

General logs

Versions of MVS before OS/390 Release 3
OS/390 Release 3 and later
Note:
Support for the removal of the 168 data set limit, and for the AUTODELETE and RETPD parameters, requires the sysplex’s LOGR couple data set to have been formatted using OS/390® Release 3 or later. The removal of the 168 data set limit also requires the LOGR data set to have been formatted with DSEXTENT(nnnnn). If either has not been done, refer to the "Pre-OS/390 Release 3" box.

Related reference
Reading log streams using batch jobs (for example, DFHJUP)
SUBSYS=(LOGR,DFHLGCNV,...) keyword
Using DFHJUP to read log streams
DD statements for DFHJUP or your own batch job
Utility control statements for DFHJUP
DFHJUP return codes
Log data accessible to DFHJUP
Diagnostic information in DFHJUP output
Examples of using DFHJUP
[[ Contents Previous Page | Next Page Index ]]