At 02:50 AM 1/22/99 +0000, Tom wrote:
>One thing to be *REALLY* careful about is with DB maintenance utilities
>such as DBGENERAL. If the group you're running in is on a different
>volume set than the group containing the dataset you're expanding, the
>dataset gets trashed.
>
>What happens is that the new datasets are built in the run-group. At the
>end of the rebuild, the old dataset is purged and the new set is RENAMED
>to the database's group - which FAILS across volume sets. It's recovery
>from this is to leave the root at the old capacity. So you've got an
>orphaned dataset on another volume set at the wrong capacity, but the
>root file is no longer in synch. Your database is effectively trashed.

As the North American support for Flexibase/Image, I saw this and wondered
whether we would be caught by the same thing.  I must admit that is a test
that I must add for future releases.

While Flexibase won't do the maintenance, it does tell you the reason why
it won't.


Brian Duncombe  [log in to unmask]  http://www.triolet.com
voice: 1-877-TRIOLET (874-6538) (905)632-2773 fax: (905) 632-8704
"Whether you think you can or think you can't, you are right."
          Henry Ford