As Dirty Harry said: "Go ahead punk, make my day!". And I extoll the value of going in the opposite direction: reserving SLOTs at the very top of the CP_OWNED list for more than enough SPOOL volumes. Reserved SLOTs are cheap: no software or hardware charges, and very little resource consumption. The alternative is that you place the SPOOL SLOTs somewhere else in the CP_OWNED list, and potentially change the SLOT number some day - thereafter losing all SPOOL files the next time you IPL VM.
Here's a cut/paste from my SHARE session: "z/VM Installation -- It?s Installed, NOW What? (Or: What we learned ?on the job?) ---<snip>--- SPOOL volumes in first Slots Any change in existing SPOOL volume SLOT order will result in a loss of all SPOOL files on that and trailing SPOOL volumes. You can always add more SPOOL slots lower down (that?s why it is good to have RESERVED slots up top specifically for future SPOOL volume use. Linux virtual machines will require more SPOOL due to DCSS usage ? plan for it. (DCSS? are stored in SPOOL) You can remove completely-empty SPOOL volumes (difficult to get completely empty), as long as they do not affect the SLOT NUMBER order of the remaining SPOOL volumes. When faced with a file similar to the following, what?s your first impulse? CP_Owned Slot 1 VMPP01 OWN CP_Owned Slot 2 VMR51A OWN CP_Owned Slot 3 VMPP08 OWN CP_Owned Slot 4 VMDUMP DUMP CP_Owned Slot 5 VMTD01 OWN CP_Owned Slot 6 VMPG05 OWN CP_Owned Slot 7 VMPG01 OWN CP_Owned Slot 8 VMPP06 OWN CP_Owned Slot 9 VMPG07 OWN CP_Owned Slot 10 VMPP07 OWN CP_Owned Slot 11 VMR51B OWN CP_Owned Slot 12 VMTD02 OWN CP_Owned Slot 13 VMSP01 OWN CP_Owned Slot 14 VMPG02 OWN CP_Owned Slot 15 VMPP04 OWN CP_Owned Slot 16 VMPP05 OWN CP_Owned Slot 17 VMSP02 OWN CP_Owned Slot 18 RESERVED CP_Owned Slot 19 RESERVED CP_Owned Slot 20 RESERVED Why? sort it by volser, of course! And then change the SLOT numbers back into a nice, neat serially sequential list starting at 1. BAD IDEA! At the next IPL you will lose all SPOOL files! Why? -- You changed the SLOT numbers of the SPOOL volumes (in this case fairly obvious VMSP01, VMSP02 ? but maybe not always so obvious). ---<snip>--- As Bill Cosby said: "Noah, how long can you tread water?" I figure you can tread water until one fateful day when you decide to "clean things up", making them all nice and neat. We sysprogs are after all rather A.R. At the next IPL you can no longer tread water, Dirty Harry (he *is* your manager, right?) has his day made for him. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "George Haddad" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> 04/30/2007 09:30 AM Please respond to "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Spool Area Full David Boyes wrote: > Couple of comments: > While no longer absolutely necessary, it's good habit to always allocate cyl 0 as PERM, and then do whatever else you need to do. The requirement to do this went away a while ago, but it's just good practice as it reinforces that cyl 0 is something that you don't wan't the system to clobber for any reason. Excellent advice as always from Dave. > > Make sure you add another open slot at the END of the CPOwned list when you use one of the slots. > > I'd go as far to suggest that a safe practice is to ALWAYS use slots at the END of the CPowned list when adding new SPOOL volumes. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
