This looks like a problem we had some time ago, although it was part of a much more complex outage.
The problem was a power failure (Murphy during actions on the power infra) in one site of the 2 site 9-LPAR sysplex. Several things like automatic recovery action (sysplex partitioning etc) were as expected, but one thing was unexplainable: We have 2 GDPS K systems in our 9-LPAR sysplex, and the surviving part of the sysplex was hung. We had message: .HASP292 MEMBER MVSS -- JES2 IS WAITING FOR RESPONSE TO WRITE TO CKPT1 SYS3.JES2.HASPCKPT ON SSYS39 This is a GDPS K-system, with a private single JES2, with its private DASD, with no other LPAR accessing it, so there should be no one accessing its CKPT. This system also reported that IXC431I GROUP SYSWLM MEMBER MVSS JOB WLM was stalled, but with no indication of the causer of the stall. Then another LPAR, which also hung, was partitioned out of the sysplex and the hang situation was solved. We cannot explain a) what was delaying JES2 on the K system b) why it was solved by partitioning another production LPAR out of the sysplex. Apparently there was some (JES2?) connection between these LPARs. I found XCF Group SYSJES, that was connected by all LPARs in the sysplex, in spite of the fact that the K-Systems run their own single JES2 and are not part of the JES2 MAS of the Production LPARs. There is very little information about this XCF Group. We are in the process of submitting all info to IBM to find the cause of this unexpected JES2 hang, which seems as unexplainable as yours. We run z/OS 2.2. Grtn, Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Salah Balboul > Sent: 19 April, 2018 22:37 > To: [email protected] > Subject: Re: SYSPLEX Hung > > nothing in the syslog prior to this indicates any issues. All running > fine. > > Yes we have an automation tool. > > Yes, I will place the CKPT1 on the CF. > > Thanks > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** 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
