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.
CA-IDMS, all supported releases.
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.