Re: CNZ9003I Message



My instructions to operations (which has always worked and I have tested
many times) is to wait for this message prior to starting to IPL the next
LPAR when IPLing multiple LPARs in the sysplex"

ISG004I GRS COMPLEX JOINED BY SYSTEM sysname

This is right after all the couple data set processing.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark.zelden@xxxxxxxxxxxx
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html



On Wed, 31 Oct 2007 12:25:33 -0400, Chris Burgess
<burgess_christopher@xxxxxxx> wrote:

Thanks Gary that is excellent information. We are actually a test lab and
we are trying to IPL 15 LPARs at one shot. At this point we have not be able
to get them all up in a sysplex environment. I am trying to figure the best
way to tune the sysplex to make that happen.



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@xxxxxxxxxxx] On Behalf
Of Diehl, Gary (MVSSupport)
Sent: Wednesday, October 31, 2007 11:02 AM
To: IBM-MAIN@xxxxxxxxxxx
Subject: Re: CNZ9003I Message

Chris,

If you're actually getting these, it's an improvement over what used to
happen when you IPL'd systems too closely together chronologically.
They used to either wait state, or go out to "la la land" and never
report back, load an OS, or wait state (green on HMC, "operating", but
no OS ever shows up). Images/LPARs that are IPLd too close together
appear to be fighting over access to the CFs to check in to the PLEX,
and from what I've seen the CFs only seem to be able to check in one
system at a time in a very serial manner.

Wait until the LPAR joining the plex is responding to a routed D A,L
command and has at least one task started before performing the
load/activate on the next LPAR. (alternately, wait 2-3 minutes between
activations, that seems to work as well)

Hope this helps,

Gary Diehl

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.



Relevant Pages

  • Re: HMC Management Best Practices
    ... Major changes a Sysprog is on site to verify the changes were ... Sysprog handles all updates to the HMC (we don't use dynamic IPL parm ... As for IPLing the wrong LPAR, ...
    (bit.listserv.ibm-main)
  • Re: HMC Management Best Practices
    ... The only thing our operators ever do is IPL. ... lpar and IPL it. ... For IBM-MAIN subscribe / signoff / archive access instructions, ... send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO ...
    (bit.listserv.ibm-main)
  • Re: Question on 64 bit
    ... Can I setup the PROD LPAR so that when I'm ready ... to IPL it to 64 byte I just need to do the IPL and not a second POR? ... For IBM-MAIN subscribe / signoff / archive access instructions, ... send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO ...
    (bit.listserv.ibm-main)
  • Re: HMC Management Best Practices
    ... IPL an lpar with a specific load address/load parm. ... Change lpar settings, storage, cpu's, weights,... ... operator errors while performing HMC tasks? ...
    (bit.listserv.ibm-main)
  • Re: multiple z/OS sharing considerations.
    ... If you have one machine, and it crashes or loses power, then your whole sysplex crashes, and your outage is probably longer because you have to start 2 Lpars and connect them before starting your work back up. ... It didn't take much more to shut down batch and IPL, especially since we did backups right after the IPL, and didn't want anything running anyway. ... If you have 2 Lpars in a sysplex, and each Lpar runs say 10 CICSs, how do you prevent shutting down the 10 CICSs on the system you want to IPL? ...
    (bit.listserv.ibm-main)