Ken, wasn't that on the SIGIMAGE enhancement list (therefore
not yet implemented) that all aaociated files of a daabase
be  handled the same way the datasets are handled - as integral
parts of the data base?

Happy Easter!

Nick D.

> From: Sletten Kenneth W <[log in to unmask]>
>
> On a fairly recent release of MPE (don't recall which PP), I
> noticed a change on VSTORE output:  A feature was added
> where if the root file and all MPE-name-space dataset files
> for a TurboIMAGE database are not all present, VSTORE will
> complain with a prominent warning.  If the root file and all MPE
> -name-space datasets are in sync as far as VSTORE is
> concerned, you will get a count of the number of files in each
> database (and in each SQL DBE).  Nice feature....    BUT:
>
> I just happened to notice a few days ago that VSTORE does
> NOT notice if IMAGE B-Tree index files are missing, even if
> the database is properly ENABLEd for INDEXING.
>
> oops....
>
> SIDEBAR:  You may wonder:  How did we end up with the
> above situation....  well, confession:  We copy our production
> accounts to a backup volume set and then copy that to DDS.
> We haven't gotten around to changing our fairly complex, multi-
> stage backup jobs after we ENABLEd B-Trees.  Plus our
> production databases are all on mirrored discs...  plus we can
> re-INDEX our databases in about five minutes each...  so if our
> database B-Tree files don't get backed up, we can live with the
> low risk and short time to re-INDEX....   but it made me wonder:
>
> If VSTORE doesn't notice that B-Tree HFS files are not there,
> will it notice if JUMBO HFS detail dataset extensions are not
> there ??....  That would be a lot more serious....  And I would
> guess that we are not the only site that was using DSCOPY
> with FCODE= -400  and  FCODE= -401  to copy our root files
> and "standard" datasets;  that would miss both B-Trees and
> JUMBOs (our site is a long way from needing JUMBOs).
>
> Anyway, I put in a call to the HP RC.  Here's the story:
>
> GOOD NEWS:  TurboSTORE *does* know about JUMBO's,
> so VSTORE should notice if the HFS parts of JUMBO detail
> datasets are not there.
>
> BUT:  TurboSTORE does NOT know anything about B-Trees.
> So if however you specify your filesets for a STORE does not
> happen to take in the ".idx" HFS B-Tree files in your database,
> TurboSTORE will never notice they were omitted.. Of course if
> you know your databases very well you *might* notice that the
> "FILES VERIFIED" count is way low for all that are enabled for
> indexing...  and you can always re-index....  still.....:
>
> SR 5003-415-174  is being entered for me by the HP RC....
> I'll take their word for it;  won't even try and check the ESC
> for awhile....
>
> Ken Sletten