Thanks Andy! That was my problem.  (Something I would only see in this test
environment since normally our logmode is set to rollforward from the
start!)

-----Original Message-----
From: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
Sent: March 6, 2003 2:30 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Logmode RollForward on 5.1.6.2

OK Tim, I think I see the problem. The recovery log doesn't go into
roll-forward mode until the next full database backup, which is necessary
in order to have a baseline from which the log can be used to recover a
database.

When you defined the dbbackuptrigger, it automatically did the full backup
for you... that's why you see the roll forward mode working.

If you had run a full db backup after you set the mode to rollforward, the
recovery log would have started to operate in roll-forward mode.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.