I had the same problem (Recovery log filling up), and set up a
DBBackuptrigger.  You have to have your log in Rollforward mode for the trigger
to be enabled (q status will show you, on the last 2 lines, the status of these
things).  The only problem with Rollforward mode is that the log will not be
reduced EXCEPT by a database backup, where in Normal mode it will commit on its
own.

I did hit another problem when using this - my DSMSERV process would crash
because we were running too many database backups too quickly.  I would end up
running about 5 incremental backups durring a 9 hour period when the nodes were
backing up.  ADSM Support said that the fix will be out for that in PTF 16,
which is still not available.

Solution to this was to get more log space.  Fixed it right up.

Current enviorment is 2.1.15 on AIX.

Nick Cassimatis
Distributed Storage Management Team
RTP, NC
T/L 444-7302
919-254-7302

If you don't have the time to do it right the first time, where will you find
the time to do it again?



ADSM-L AT VM.MARIST DOT EDU on 01/13/98 04:44:21 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ internet
To: ADSM-L AT VM.MARIST DOT EDU @ internet
cc:
Subject: DBBackuptrigger


Until today my logs had been fine and I was running my DB backup on a scedule
once a day - full backup - no incremental.

After reading, I turned on the DBB trigger so that my log would empty out
when it was full -- my question is I'm not real clear on what I am gaining by
having the DB trigger on or not?  Also, What does IBM recommend -

Set LOGM - Rollforward or Normal?

Thanks, Gail