At 04:02 PM 10/10/97 -0400, Gilles Schipper wrote:

>Exactly what kind of STORE syntax are people afraid of that would
>inadvertantly exclude some components of the database??

The only syntax that I can think of currently is ;transport which would
ignore the files in the posix space useless. So upon a subsequent restore
on another system the jumbo files (.001, etc) would not be included.

This will be even more of an issue when the new Btree capable version of
Image comes down the pipe. (The btree "info" is in a nmksam file with a
.idx extension and resides in the posix space)

The real problem as I see it is, if any portion of a database is attempted
to be stored then the entire database should be stored, that includes posix
files, dbe files the lot and preferably if restore attempts to restore a
dataset then the entire database should be restored???

This would save the lives and jobs of people like me from inadvertantly
restore an individual dataset from a week ago into a current database
"fileset". Luckily I had just backed up the entire database.

In fifteen years of working with the HP 3000, (I started when I was 17.:)
I have never lost a file or even a transaction that I couldn't recreate, but,
I do come across people who have ruined days and even weeks worth of work
because they restored a dataset over top of a currently active/production
database. This is one of the only weak points of "Image/sql" and really has
nothing to do with Image per se

Neil "how the heck did this reply get so long" Armstrong
P.S. I just would like to say that the main reason that I never lost any
data was because Gilles taught me everything I know about system management. :)
Lord knows what I would be like as a system manager ever since I moved to
the "dark side" :)