We have 10 zVM LPARS all of which simply run linux guests. We have no CMS/other applications running on any of these systems. We also don't care about spool files as they are primarily spooled console logs. Our maintenance methodology is a "rolling RES pack" paradigm, and we keep all of our third party products, linux guests, config files, etc. separate from the OS. We install the VM updates to a 2nd-level system and once we verify that all is well, we simply copy that RES vol around to the rest of our zVM LPARS. If any maintenance touches CMS, I also have to roll the spool volume around. By moving the NSS/DCSS segments to the RES vol, I am simply trying to avoid having to copy a spool volume around should any DCSS/NSS changes occur as everything will live on the one RES volume.
I am primarily concerned about any performance issues related to having everything on the RES vol. And yes, it would be nice if it was possible to redirect SPXTAPE output :-). -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Friday, July 20, 2007 3:29 PM To: [email protected] Subject: Re: NSS and DCSS on RES > >I just did a fresh install of zVM 5.3 using a MOD9 for the RES volume. > >The RES still has ~1500 cylinders free. Is it possible (or advisable) > >to format a few hundred of those cylinders as spool space and move all > >of the NSS/DCSS segments on to the RES? The zVM system does not have > >access to any tape drives so I cannot use SPXTAPE. Possible, but not a good idea -- it's taken years to convince IBM to get spool/page/etc OFF the RES volume; don't mess it up now. Leads to unexpected FORCE/COLD starts when you change RES vols with upgrades. Unless you have a desperate shortage of disk, it's a good idea to never have a release-dependent volume contain spool space in the CPOWN list. If you're in a 2nd level machine, better to add a few large minidisks on a different volume to the virtual machine definition, format/allocate them with DSF, and let the 2nd level CP treat them as separate packs. No chance of accidentally clobbering 1st level spool that way. PS - Wouldn't it be nice if SPXTAPE had a option to direct it's output to the input of a PIPE so we could redirect the output to where we needed it to go (so we wouldn't require a tape drive)? *sigh* Someday...
