This is why I like having my 2ndlvl maintenance system on real volumes wi th real volsers. I can and will use it as a recovery system. I have moved several entire MVS DASD farms from one subsystem to another because I had
this separate system to IPL. I choose to use IBM's volsers for my maintenance system and my own volsers for the production volumes. So I ha ve kept VMARES as my production sysres since VM/XA and still have multiple I BM systems to IPL (currently 4.4 is still on tape, 5.1 and 5.3 are on DASD). Because of our installation's decision to only have model 9 DASD, I do pu t both PAGE and SPOOL on the same volume. I know that everyone cries out against this, but it does work for the duration of my maintenance periods or recovery sessions. This is not the PRODUCTION configuration. It will even work for a DR scenario with PAGE, SPOOL, TDSK all on a single SYSRES. /Tom Kern /301-903-2211 (O) /301-905-6427 (M) On Wed, 17 Oct 2007 09:14:48 -0700, Austin, Alyce (CIV) <[EMAIL PROTECTED]> wrote: >I assume I could also bring my "new" system up lst level >rather than 2nd level since I have an additional LPAR available; or, do >I have to bring it up 2nd level first (with the new volumes attached) >and then bring it up lst level? > >Thanks again, >Alyce > > > > >-----Original Message----- >From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >Behalf Of David Boyes >Sent: Wednesday, October 17, 2007 8:19 AM >To: [email protected] >Subject: Re: 2nd Level IPL > >It's also useful to note that full packs are not required for page and >spool. Using minidisks on the 2nd level system and formatting them with >ICKDSF using the same labels as the real volumes gives you a disposable >page and spool area that you can cold-start at will w/o risking any real >data. My 2nd level test systems run with only about 200-400 cyls of each >defined. > >It'd be really helpful for that stream-oriented SPXTAPE to show up >someday... >======================== ========================= =======================
