We have six volume sets and use the command
 
!   FILE FBKSV1;DEV=70
!   FILE FBKSV2;DEV=71
!   FILE FBKSV3;DEV=72
!   FILE FBKSV4;DEV=73
!   CONTINUE
!   STORE @[log in to unmask]@,@.@[log in to unmask]@,@.CURRENT.@,&
!   @[log in to unmask]@[log in to unmask]@DB.@[log in to unmask]@[log in to unmask]@[log in to unmask]@;;&
!   STORESET=(*FBKSV1),(*FBKSV2),(*FBKSV3),(*FBKSV4);&
!   PROGRESS=1;DIRECTORY;SHOW;INTER;MAXTAPEBUF;ONLINE;&
!   NOTIFY;ONVS=MPEXL_SYSTEM_VOLUME_SET
 
rsp. ....ONVS=UV_SET1 ... ONVS=UV_SET2 etc ...
 
To store the databases first is caused by ;ONLINE option (we keep the
system down for 2 hours anyway), and ;NOTIFY is used to build a trigger
file which are checked for existance (via MAESTRO) after 2 hours.
The ;DIRECTORY option of course is the most important one for Restores of
file structures you do not know in detail.
 
To restore out of an combined store all files only on one Vol_Set I guess
that restore ;VOLSET= ... and ;ONERROR=SKIP (without ;CREATE) should work
if the account structure is already there (all groups should have the
HOME VOL SET=name_of_volume). We didn't test this in the past by
splitting up the Sys_Vol into real Sys_Vol and Production_Vol_Set - we
successfully used the indirect file method you mentioned. On the other
hand, the BULDACCT program is very useful for this via the %ONVS etc.
options.
 
Hope this will give you some ideas as well.
Best regards, Andreas