Enabling  MUSTRECOVER allows only read (open modes 5-8) access to the
database after a system failure until the database is recovered. It is part
of the rollback recovery process.

In the event of a system abort, hang, or power fail overage you may not want
to restart user logging
before running DBRECOV. Log records may have been lost! If user logging is
resumed without an intervening recovery, the resulting broken log file may
invalidate any subsequent recoveries.

These same issues are also relevant to the various forms shadowing.

This leads to the next question: Are Turbo Image log files attached to
transaction management?

Mike Hornsby
[log in to unmask]

-----Original Message-----
From: Tony Furnivall <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Tuesday, November 17, 1998 12:07 PM
Subject: Image MustRecover flag


>Hi there, Image gurus
>
>Can anybody tell me more about the MustRecover flag in DBUTIL? There is
only
>the sketchiest documentatin in the Image manuals that I have, and this
looks
>like it might be a useful tool for my situation (several K databases on the
>network, several hundred on some machines), and could be a real time-saver
>(as well as a real-time saver!) after a system failure.
>
>Tony