Kevin,


Moving back in time and then forward if the backward step is not stopped
already is not allowed. You'll get a message like "Their is a setclock
correction running". You'll have to wait or cancel the old correction first.

Problems will occur while running database actions with image logging, and you
use the now parameter as Manager.sys.

You'll get new log records with older date/time stamps. A rollback recovery may
go wrong (sorry I am not a image guru to be sure about this).


Regards,


Jan Gerrit Kootstra
"Newman, Kevin:" wrote:

> The problem might have been when moving the date back and then forward.
> When moving the time back, it slowly looses time, that way it doesn't
> overlap times that have already gone by.  If you move it forward while it is
> in the process of moving back....I'm not sure what will happen.  In your
> case of setting it forward, then back.  I don't see how anything could
> happen to mess that up.
>
> Kevin
>
> > > I may have had a bad dream one day awhile ago, but I was certain that I
> > read
> > > in this group a post about setting the HP3000 date forward and then
> > > returning it.
> >