""??à?áá"" <[email protected]> wrote in message 
news:<[email protected]>...
> Hi lists,
> 
> 
> I established a base plex beyond VM.It consists of two zos guests connected 
> with each other by ESCON CTC.
> But...one of them fails every half day...what's a poor implemention!
> Every time it give a message like that when it died:
>  IXC402D XT1K LAST OPERATIVE AT 22:23:06. REPLY DOWN AFTER SYSTEM     
> RESET, OR INTERVAL=SSSSS TO SET A REPROMPT TIME.      
> and the vm console got this:
> 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
> from
> CPU 01.                                                                       
>  
> 00: HCPGIR450W CP entered; disabled wait PSW 00020000 80000000 00000000 
> 000200A2
> 01: HCPPCM6533A Following is a priority message received by the service 
> proces 
> sor - use the VINPUT command to respond:                                      
>  
> 01: *IXC220W XCF IS UNABLE TO CONTINUE: WAIT STATE CODE: 0A2 REASON CODE:     
>  
> 01:  020,                                                                     
>  
> 
> 01:  THIS SYSTEM RECOGNIZED THAT IT WAS REMOVED FROM THE SYSPLEX              
>    
> 
> 
> I tried several days to figure out what cause above,but i cann't .
> anyone could help me please?
> 
> 
> 
> 
> Thanks!
> 
> 
> 
> 
> Tiegox Zhang

Did you check the 0A2 waitstate? 
RC 020 gives the possible reasons:

        020      XCF removed the system from the sysplex.                       
              
                                                                             
      One of the following occurred:                                            
                                                                             
      ~   An I/O error was encountered by this system on either the primary    
 
          or the alternate couple data set after this system joined the         
     
          sysplex but before it could complete initialization of the couple     
 
          data sets.                                                            
                                                                             
      ~   An I/O error was encountered by another system in the sysplex on     
  
          either the primary or the alternate couple data set after this        
    
          system joined the sysplex but before it could complete                
    
          initialization of the couple data sets                                
    
                                                                             
      ~   The operator on another system in the sysplex initiated a data       
    
          set transition by making a new alternate available via the SETXCF     
 
          COUPLE,ACOUPLE command or by replacing the primary couple data        
    
          set with the alternate couple data set via the SETXCF                 
     
          COUPLE,PSWITCH command. This action was taken after the time that     
 
          this system joined the sysplex but before it could complete          
          initialization of the couple data sets.                               
   
                                                                             
      ~   The operator replied DOWN to message IXC402D to specify that XCF     
  
          was to remove the system from the sysplex.                            
                                                                             

Kees.

********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************
                        

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to