We had a problem where the Recovery log was not being reset by the Database
backup.
IBM believe that the problem was due to a hung client session which had not
released a thread on the recovery log.
The solution was to upgrade the MVS Server to 3.1.2.15 with fixtest pq21945.
Since applying this fix the problem has not reoccurred.

Nathan

        -----Original Message-----
        From:   Richard Sims [SMTP:rbs AT BU DOT EDU]
        Sent:   Monday, March 22, 1999 9:10 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: Excessive amount of database backups triggered

        >Time after time, a database backup was triggered almost immediately
after
        >the last one completed. This happened 12 times before the system
(probably)
        >ran out of scratch tapes:
        >Why does this happen?

        The Recovery Log having reached the DBBackuptrigger value,
especially
        repeatedly, is obviously a symptom of a LOT of activity.  What
sessions
        were active?  What was going on?  Look at your Activity Log and
        accounting records for client activity.
            Richard Sims, BU