I still only have one Volume (on a small machine) but I have been doing this
for a couple of years on it):
 
I made sure all my nightly batch print runs have UNIQUE spool file names.
 
I hold off printing until all the night jobs have been SPSAVED (with :SPOOLF
@;SPSAVE) or I make sure the file equation has SPSAVE in it.
 
I then copy them (using MPEX) daily to seven groupings in the production
account daily called MON,TUE, WED, THU, FRI, SAT, & SUN after purging all
files in the group that are a week old.
 
The copied files retain their Spool File-ness attributes.  In other words, a
user can
 
SPOOLF filename.MON;PRINT;DEV=devclass/ldev
 
any time during the week, "as if" the "filename" were a Onnnn.OUT.HPSPOOL
file.
 
Even though I don't use Private Volumes, I suggest this would work for you
since the groups are in their respective production accounts.  Or even if
you don't wish to convert the spool file name to a regular file name, you
can just copy them to the same "Onnnn" number in the new groups.
 ----------
From: owner-hp3000-l
To: Multiple recipients of list HP3000-L
Subject: Spoolfiles on private volumes?
Date: Monday, September 09, 1996 10:43PM
 
I know this may be asking for more flexibility than one can reasonably
expect
from MPE private volumes, but has anyone successfully moved the spool
account(HPSPOOL) to a private volume? Or do spool-files have to reside on
a system volume?
 
I've tried following the steps outlined in the volume management manual to
move the relevant spooling account structure. Everything appears OK until
I start spooling or re-boot the system at which time the system dies with
a System abort 614 Subsys 143(file system, secondary=-33,518) - undocumented
of course.
 
Thanks for any advice, pointers, or personal experiences.
 
Regards,
 
Lee Courtney
Monterey Software Group Inc.
 
 Voice: 408-253-1778
   Fax: 408-253-1815
E-Mail: [log in to unmask]