As Paul said, you've most likely got a long running session or process that
has a transaction pinning the log.  I've got a cron'd script that runs every
10 minutes that logs to an alog.  This is a cirular log that won't grow out
of control even if you never check it.  This helps me figure out what's
causing my pinned recovery log on the rare occassion it happens.  A simple
example is included below.

Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail


!#/usr/bin/ksh

{
   echo "q sess"
   echo "q pr"
   echo "q log"
} | dsmadmc -id=id -pa=password | alog -q -f /path/logname -s 200000