LOG filling faster that it can be archived

Products

• IDMS
• IDMS - Database

Issue/Introduction

This article describes the most likely scenario for why the dc-log appears to be filling faster than the ARCHIVE LOG job can empty it.

Environment

Release: All supported releases.

Cause

The most likely causes of the dc-log filling quickly is that task and/or system snaps are enabled, and several abends have happened in a relatively short space of time. Each abend will cause a snap to be written to the log. These snaps can be very large and it would not take many of them to make it appear that the log is not being emptied by the ARCHIVE LOG job.

 

Resolution

Issue the command DCMT D SNAP.
If task snaps are ENABLED, vary them off.

DCMT VARY SNAP TASK OFF
DCMT VARY SNAP TASK NOPHOTO

Issue the command LOOK OPTION FLAGS
If optional flag 176 is set, then system snaps may also be being written to the dc-log, so vary them off, too.

DCMT VARY SNAP SYSTEM OFF
DCMT VARY SNAP SYSTEM NOPHOTO

With snaps DISABLED, much less information will be written to the log.

Note: The effect of these DCMT VARY SNAP commands will last only until the next shutdown.
To make it permanent, the option must be changed in SYSGEN.

Note also that in the output of the DCMT D LOG command, the % USED figure may not be up-to-date.

 

Additional Information

DCMT DISPLAY SNAP
DCMT VARY SNAP
LOOK System Task