> -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of David Kreuter > Sent: Monday, February 12, 2007 5:16 PM > To: [email protected] > Subject: Re: Renaming spool and page > > hmm...it is a minor miracle your production system didn't > crash, or corrupt spool files. At IPL time of the errant > LPAR, certainly 2 dump files were open, and some console logs > of early life virtual machines. So the spool volume was > touched. By copying the WARM cylinders and using the same > spool pack, pointers were intact from the moment of > "snapshot". Sort of. > > Sorry to suggest since given most shops production schedules, > but I would consider a reIPL of your production LPAR. Just to be sure.
Yeah. Already suggested it to my manager. Haven't heard back... > > What is your unbootable condition? Disabled Wait: -- The code is 0912. According to "System Messages and Codes" It is a volume not mounted. Did you run the SALIPL > utility to burn in the IPL info on your new "sysres"? no > Are you getting a disabled wait state? see above > When you relabelled did you re-allocate the page and spool volumes? no > David > Obviously this is much more complex than I thought. As it always seems to be. Thanks. > -----Original Message----- > From: The IBM z/VM Operating System on behalf of Little, Chris > Sent: Mon 2/12/2007 5:16 PM > To: [email protected] > Subject: [IBMVM] Renaming spool and page > > We're working on disaster recovery here...and just about created one. > Created a "recovery" of our primary z/VM lpar and IPLed it in > another, but with a potentially grand mistake. The > production spool and page volumes are at a lower address than > the DR spool and page volumes. And it did IPL with those. > "Q ALLOC SPOOL" and "PAGE" proved that. By some chance it > didn't crash production. > > So now we IPL second level before we IPL in an LPAR. > > After IPLing I tried changing the volume names of spool and > page and reflecting that in SYSTEM CONFIG, but it results in > an unbootable system. > > What else do I need to do? >
