Thanks Mike. I knew most of the steps were the same as they were for adding the PAGE but I just wanted to make sure of any special issues with SPOOL!
Thanks again for the detail explanation. Terry -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Wednesday, November 19, 2008 6:09 PM To: [email protected] Subject: Re: Adding a spool volume Rhetorical question: When, oh when, will IBM document adding PAGE and SPOOL volumes dynamically in a clear, concise manner? This question is asked at least 3 or 4 times per year. And more often as we get more new z/VM sysprogs (WELCOME!). None of the lengthy calculations used to determine the initial PAGE and SPOOL volumes apply when someone wants to dynamically add a volume. The answer is always the same - and pretty simple (but scary to the uninitiated, and their managers). "Just DO IT"! :-) To answer your question: It is to adding a PAGE volume dynamically. One important caveat. -------------------------- When you add the SLOT to CP_OWNED in SYSTEM CONFIG, you don't ever get to change the SLOT number without first scheduling stand-alone time to use SPXTAPE to backup ALL your SPOOL files (including all SDF's -System Data Files, e.g CMS and many more). And I mean NEVER change a SPOOL volume SLOT number, not even "by accident" when you're doing regular "housekeeping" to neaten up the SYSTEM CONFIG file sometime in the future. That's why in my SHARE session "z/VM Installation - It's Installed, NOW What? (or: What we learned "on the Job")" (http://linuxvm.org/Present/SHARE111/S9120mw.pdf see slides 12-14) I recommend when installing z/VM to place the SPOOL volumes at the top of the CP_OWNED list -- and documenting why they should not be moved without understanding the implication of changing a SLOT number (loss of "*ALL* SPOOL files). So, to cut/paste from Scott Wandschneider's posts of just last week asking about a dynamic PAGE volume addition, adjusting for SPOOL: 1) CP ATTach rdev to MAINT. 2) CPFMTXA FORMAT 0-end on a new volume, with your chosen volser. 3) ALLOCATE 0-0 PERM and 1-END SPOL. additions... 4) Update SYSTEM CONFIG with new CP_OWNED SPOOL volume. Remember the SLOT number. (see comments above about never changing the SLOT number - maybe you want to slip it in right after an existing SPOOL SLOT if there's room available). 5) Run CPSYNTAX (on MAINT's 193 disk) against the updated SYSTEM CONFIG (as usual, after any change). 6) DETach rdev (from MAINT) 7) ATT rdev SYSTEM volser 8) CP DEFINE CPOWNED SLOT nnnn volser OWN (nnnn=SLOT number from SYSTEM CONFIG) 9) CP START DASD rdev SPOOL 10) CP Q ALLOC SPOOL (check that the new volume it looks right) Let me us know if I left anything out (detailed instructions were obviously not included for CPFMTXA, or updating SYSTEM CONFIG). Maybe IBM can use the results for a simple update to "CP Planning and Use". Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Martin, Terry R. (CMS/CTR) (CTR)" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <[email protected]> 11/19/2008 03:42 PM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Adding a spool volume Hi What are the steps to add a spool volume dynamically and what should I watch out for. Thank You, Terry Martin Lockheed Martin - Information Technology z/OS & z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 [EMAIL PROTECTED] 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. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
