<----- snip -----> We have 2 LPARs in a sysplex, running on 2 different machines in 2 different sites. What happened was we lost connectivity between our 2 sites for a few seconds. As a result, MVSB (running in site B) lost its connectivity to the primary SYSPELX couple data set residing on dasd in site A, and issued the following message:
IXC253I PRIMARY COUPLE DATA SET 953 XCF.COUPLE01 FOR SYSPLEX IS BEING REMOVED BECAUSE OF AN I/O ERROR DETECTED BY SYSTEM MVSB ERROR CASE: PERMANENT ERROR The above message was then issued by MVSA as well. Sadly enough, our alternate SYSPLEX couple data set resides on dasd in site B. So MVSA had no connectivity to it, which led to a Disabled Wait 0A2 RC 20 in MVSA. <----- snip -----> Did you lose the XCF signalling connectivity at all? If you have got the above message on the MVSA as well, the connection was still there at the time. <----- snip -----> After that, MVSB issued the following message: IXC256A REMOVAL OF PRIMARY COUPLE DATA SET 463 XCF.COUPLE01 FOR SYSPLEX CANNOT COMPLETE UNTIL THE FOLLOWING SYSTEM(S) ACKNOWLEDGE THE REMOVAL: MVSA Of course, MVSA could never acknowledge since it was in a disabled wait. <----- snip -----> Your automation tool could vary offline system(s) that are already in disabled wait in the case of IXC256A. Zaromil ---------------------------------------------------------------------- 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
