Larry after Don:

>> ..... what constitutes an Image database beyond the root file,
>> datasets (including jumbo), TPI files, and B-tree files?
> >>
> >> Is a copy of the schema required?
>
> If you're using IMAGE/SQL, you will have other files associated
> with the SQL portion of the database.

-431, -491, -493, - 497 for the standard DBE files (at
least that is the set I am aware of).

>> I would like to determine a minimum set of files that must be
>> backed up and restored in order to recover a database in the
>> event of some catastrophic system failure.

> This is a more complicated question.

> ......  "it depends".

....  and coming up with a "standard list" that would reliably
apply to all sites is tough....  And if you extend the question
from "what files are required to do a formal DBRECOV" to
"what files are required and/or really handy to have to restore
and synchronize a local database environment", then YMMV
applies.

This issue is one of many things the "IMAGE ENCHILADA
Project" is intended to address, by making it relatively easy
to implement an enhancement that has been on the
SIGIMAGE Ballot for a number of years now:

Item # 27. Allow tracking files to be associated with a database:

If the ENCHILADA is implemented as envisioned, it would
allow each site to define their own list of "associated files", that
backup products would then (hopefully) all use to determine
what files should be included with each database.

If you want to put in your detailed $0.02 on the optimum recipe
for cooking the IMAGE ENCHILADA, best way is to attend the
all-day IMAGE Users meeting on Wednesday 17 Feb across
the street from the HP Mothership, and the SIGIMAGE meeting
at IPROF on Friday 19 Feb at 09:15.   See:

http://www.allegro.com/SIGIMAGE/index.html           and
http://www.interex.org/conference/iprof99/schedule.html

Ken Sletten
SIGIMAGE Chair