Assuming that you have available DASD, not only should you add a whole volume as SPOOL, but you might even consider adding a whole volume as DUMP space (there is an allocation type of DUMP, just as there is for SPOL). Even though we have not had a CP outage resulting in a dump since December 5, 1997 (GREAT work IBM!! What else runs without an ABEND for so long!?), missing the opportunity to capture a dump is just begging for it to happen again. By dedicating a DASD to DUMP, you are pretty sure to always have plenty of room to capture the next dump (if an ABEND ever happens again). DASD is cheap nowadays. System outages are NOT cheap, and are getting more expensive every day - don't expose yourself to the same problem more than once just because you are trying to save a little DASD space!
You can add SPOOL space (allocated as "SPOL") and DUMP space (by some odd quirk of fate and design, allocated as "DUMP") without an IPL. Since these are areas dedicated to CP usage, all the allocated cylinders MUST ALL BE FORMATTED by the CPFMTXA EXEC (which calls ICKDSF under the covers). For performance reasons you do not want to place any moderate or high use data on the same DASD as SPOL (or PAGE) cylinders. Doing so causes an interrupt in the "seldom-ending channel program" that provides such good SPOOL (and page) performance. Again, DASD space is cheap nowadays, while people are not -- "waste" whole DASD volumes for SPOL and PAGE space -- allocating them as PAGE or SPOL from CYL 1 to the end (saving cylinder 0 as PERM, even though it *could* be used as PAGE or SPOL). Again PAGE and SPOL space is not hard to do in the fly. Just read the "CP Planning and Administration" manual carefully before starting. Remember that whatever you add dynamically, should be added to the 'SYSTEM CONFIG' file so it's there at the next IPL, too. Welcome to VM. If you decide to add more SPOL cylinders, and if you are worried about doing it alone, pretty much everyone on the list would be happy to review your planned set of commands and actions to guide you. Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "Alan Altmark" <[EMAIL PROTECTED]> Sent by: "VM/ESA and z/VM Discussions" <[email protected]> 11/07/2005 10:37 AM Please respond to "VM/ESA and z/VM Discussions" <[email protected]> To [email protected] cc Subject Re: Q alloc SPool Help BINGO!!!!!!! - now we are on to something! On Monday, 11/07/2005 at 08:19 PST, Randy Dray <[EMAIL PROTECTED]> wrote: [without dump] > USABLE 32040 7993 24% [with dump] > USABLE 32040 23129 72% Randy, let me emphasize the suggestions that you need to add more spool space to your system. The initial configuration delivered by IBM in z/VM 4.4 was not intended for production, but only to allow the system to come up. Without a dump, the IBM Support Center will not be able to diagnose any problem you might encounter, or you will be forced to take stand-alone dumps, a pain in the ... neck. And with your current configuration, you are running too close to the edge. If the system does abend and dump, then when the system comes back up, there will not be sufficient space to hold a second dump. Add another volume of spool space so you can quit worrying about it! :-) Alan Altmark z/VM Development IBM Endicott 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.
