Let me recap some points that have arisen over the past few days and try
to consolidate some things together - the general topic being moving
existing accounts and/or groups to a private volume set.

SYSTEM DIRECTORY/PRIVATE VOLUME DIRECTORY.  On non-classic 3000s,
directories are split between the system directory and private
volume(s).  To access a group/account, it must have a directory entry on
both the system volume and the target private volume.

The system directory entry holds almost all of the "attributes" of a
group or account (there are no private volume user directory entries).
The passwords, capabilities, access security matrix, and other items are
stored in the system directory entry.  The private volume entry serves
as little more than an HFS directory entry - it merely marks the
structure of the accounts/groups (FILES= might be stored there?  I don't
have a definitive answer).

The HOMEVS= value determines where a given group is to be found.  It is
possible to have the same group on multiple volume sets, but only the
one referenced in HOMEVS= is accessible.  (mpexl_system_volume_set can
come into play here as well).

I will omit discussion of building accounts/groups "twice" as in the
traditional :newacct foo and newacct foo;onvs=uservol, and the similar
group commands :newgroup bar;homevs=uservol - :newgroup bar;onvs=uservol
for brevity; this is the "traditional" way to create accts/groups.

A given, accessible group can only exist on one volumeset.  Different
groups within an account can reside on different volumesets (with the
requirement that the account exists on the volumesets as well).  This
makes things more complex, and BULDACCT doesn't handle it well, but it
is legal.

MOVING A GROUP/ACCOUNT.  There are three scenarios:
* Moving from system volumeset to private volumeset,
* Moving from private volumeset to system volumeset,
* Moving from one private volumeset to another.

All three can be handled by my "shortcut" method provided that the
volume sets already exist and will not change configuration.  However,
these cases are more trouble:

* Volumes are "taken away" from the system volumeset to create or append
to a private volume set.  You cannot remove a volume from the system
volumeset without an install/reload.

* Volumes are "taken away" from a private volumeset to create or append
to a private (or system) volumeset.  You must perform the :store
operation of the files to be moved first, then you must :store the
remaining files, volutil scratch the set and recreate with the remaining
volumes, and :restore the remaining files first.  You can then add the
"remaining" volume(s) to the new target volumeset prior to :restore.

THE SHORTCUT, AND HOW IT WORKS.  The basic idea is to save the files on
tape, clear the old private volumeset of directory entries, and restore
on the new volumeset LEAVING THE SYSTEM DIRECTORY INTACT.  If you purge
the system directory information all bets are off.  That is the point,
all the valuable directory information you want to preserve is already
there in the system directory.

** CAVEAT ** This works with HP Store and TurboStore, I have not
attempted this with 3rd party backup tools.

MOVE SYSTEM TO PRIVATE:
1) :store @[log in to unmask][or @.group.acct];*t;purge  (store it once before
   using ;purge unless you're really brave :-) )
2) Insure all files are gone (:report;onvs=mpexl_system_volume_set and
   check filespace)
3) :restore *t;@[log in to unmask][or @.group.acct];olddate;create;volset=newvolset
4) Verify that ;HOMEVS= was updated by LISTGROUP foo.acct
5) Empty groups won't be created - you may need to:
   :altgroup xyzzy;homevs=newvolset
   :newgroup xyzzy;onvs=newvolset

MOVE PRIVATE TO SYSTEM:
1) :store [files];*t;purge
2) :purge[acct|group] acct|group;onvs=oldvolset
3) :restore *t;[files];olddate;volset=mpexl_system_volume_set
4) Alter empty groups, if needed (:altgroup xyzzy;homevs=)

MOVE PRIVATE TO NEW PRIVATE:
1) :store [files];*t;purge
2) :purge [acct|group] acct|group;onvs=oldvolset
3) :restore *t;[files];olddate;volset=newvolset
4) Alter empty groups, if needed (:altgroup xyzzy;homevs=newvolset
                                  :newgroup xyzzy;homevs=newvolset)

CHECKING YOUR RESULTS:
Issuing :REPORT;ONVS=some_volume_set lists *only* those groups/accounts
which exist on the specified volume set.  The format is odd for the
system volume set (release-dependent); watch the disc usage column.

I *hope* this clarifies things.  If I've made any goofs above please
feel free to point them out, but the essentials should be correct.
I have been doing this for some time and shudder at the thought of
some of the time consuming suggestions I've read :-)

Jeff Kell <[log in to unmask]>