We are having issues with the Compliance Event Manager Journal file filling up. Is there a way to dynamically clean that up or maybe make the info wrap?

Document ID : KB000013417
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

We are having issues with the Compliance Event Manager Journal file filling up. Is there a way to dynamically clean that up or maybe make the info wrap? 

Answer:

The Compliance Event Manager Monitor and Alert Component Journal Files are cleared each time the component tasks are started. The Journal files do not wrap. The Journal files can be set to SYSPRINT/SYSOUT.

The Compliance Event Manager Monitor and Alert Component Journal Files by default, are initially setup with an allocation of 10 tracks, with a secondary allocation of 10 tracks., If this allocation is not sufficient, you can estimate your storage needs by changing the Journal DD statement to output to SYSOUT. Doing so gives you a more accurate representation of the amount of output that the product writes to the file. You can then estimate the storage requirements for writing the journal information to a DASD data set, and you can reallocate the Journal data sets as needed. Using this method helps ensure that the data sets are large enough to record the amount of diagnostic information that your site requires. Doing so offers the following benefits:

- Lowers the chances of losing data if the data set becomes full
- Reduces the need for manual intervention to copy and reuse the data set.

To define the file to write its output to a JES SYSOUT file, use the following sample DD statement. 

Example: DD statement to route the Journal data set output to SYSOUT

JOURNAL DD SYSOUT=*

Note: When the ALERT or MONITOR Component Task is stop and re-started the Journal file is cleared.