The question of whether or not to RESET a down system is a touchy one. I've
heard the mantra for years and could not begin to challenge it on technical
grounds.

<Sidebar>

Two hunters are out in the woods. One accidentally shoots the other. (Any
resemblance to U.S. politicians past or present is coincidental.) The
shooter calls Emergency in a panic.

"Help! I just shot my friend. I think he's dead. What should I do?"

"What you do next depends on whether he's really dead. Please make sure."

[Pause. BANG!]

"OK, I'm sure."

<End Sidebar>

The point: we've run one form of 'plex' or another for 15 years. We have
never required operators to RESET a down system once a wait state is
achieved after V XCF OFF. I can't deny the possibility of some comatose I/O
operation miraculously coming to life after seconds or minutes of WAIT
STATE. I can however attest to the inherent risk of an operator--or a
distracted sysprog--going to the trouble of unlocking an LPAR in order to
RESET...the wrong image. Until I have (sad) experience to the contrary, I'm
inclined to play the published odds: once dead, dead for good.

.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[email protected]


                                                                           
             Barbara Nitz                                                  
             <[email protected]                                             
             >                                                          To 
             Sent by: IBM              [email protected]                
             Mainframe                                                  cc 
             Discussion List                                               
             <[email protected]                                     Subject 
             .edu>                     Re: Sysplex timeout problems.       
                                                                           
                                                                           
             07/08/2009 10:07                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
               IBM Mainframe                                               
              Discussion List                                              
             <[email protected]                                             
                   .edu>                                                   
                                                                           
                                                                           




I was going to ask Mark how (and if) fencing works in a basic sysplex when
Skip (very oblingingly) provided the answer that it doesn't. :-(

So, in Kens case, he will always get IXC102A.

>A strong word of caution:
>DO NOT automatically reply DOWN.

Mark, does this apply to a basic sysplex, too? Or would Ken be safe having
automation reply to it?

<snip>

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

Reply via email to