Murphy's law dictates a small change in the order of things.
With the order you propose there is a time window where the SYSTEM CONFIG
does not know the new spool volume, but CP uses it for new spool files. If
CP goes down in that window, all spool files with some parts of the new
volume will be lost after the restart.
The good order to be 100% safe is:
1. Format & allocate (like you say)
2. Update SYSTEM CONFIG
3. DEFINE CPOWNED
4. ATTACH to SYSTEM
To find which spool files have parts on a given volume, get this tool
http://www.vm.ibm.com/download/packages/descript.cgi?SPOOLCHN
2007/4/30, James M <[EMAIL PROTECTED]>:
z/VM 5.2
I'm backing up the vm sys prog and sure enough - bing - a problem
immediately.
Problem solved but I have a couple of questions.
adding a new spool full volume steps - is this correct..
att cuu * as vdev
cpfmta vdev
label vmspxx
done...
format
done..
allocate
spol 0-end
done...
end
Once cpfmtxa ends - att cuu system vmspxx & update cpowned list in
config file.
...and I'm off and running.
Followup question - is there a convenient way to migrate spool files from
that volume without cold starting?
Another spool followup question.
If I query alloc and do the math on the spool numbers I get 80%
If I q alloc spool I get 53%
How come?
Any rexx exec's out there that can monitor spool and send me an email if >
x%?
Thanks
James
--
Kris Buelens,
IBM Belgium, VM customer support
