Tom <[log in to unmask]> 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.


I cannot speak for other systems, but Adager, by design, has always built
its work files in the user's logon volume set, which MUST correspond to the
database's group and account.

In addition, Adager has supported volume classes on MPE/iX since they first
appeared on the scene (around 1992?).





 _______________
|               |
|               |
|            r  |  Alfredo                     mailto:[log in to unmask]
|          e    |                                  http://www.adager.com
|        g      |  F. Alfredo Rego                       +1 208 726-9100
|      a        |  Manager, R & D Labs               Fax +1 208 726-2822
|    d          |  Adager Corporation
|  A            |  Sun Valley, Idaho 83353-3000                   U.S.A.
|               |
|_______________|