Or if the automation tool does regularly re-IPL systems, it could have decided to do so at that moment for an unknown reason.
Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: 23 March, 2015 15:03 To: [email protected] Subject: Re: Unscheduled automatic reIPL on z10 Did you seen any device contentions? Sometimes if a DASD has a reserves and it is a critical volume, like a Jes CKPT dataset, then the system only allows so many seconds to get at it. If it does not, the system could be considered non responsive. Any SVC Dumps during that time? How intact is your syslog? If syslog stopped minutes before the event, then you might not see the details. Check SMF Data as well for PDS/E, zFS or other statistics. If you have OPS/MVS or other automation tool, it might have captured messages you could review. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Beesley, Paul > Sent: Monday, March 23, 2015 6:44 AM > To: [email protected] > Subject: Unscheduled automatic reIPL on z10 > > An hour or so ago, one of our z/OS systems decided it had enough of life and > re-IPLed itself. > > In the HMC hardware log we see this: > A logically partitioned mode event occurred. Select details for information. > Selecting Details gives: > A program directed re-IPL has been initiated for partition XXXX. > > First thought was that someone had done a V XCF,SYSNAME=XXXX,REIPL but > that would have generated a wait state record in the hardware log, And in > any case I have checked all of the other 13 systems in the sysplex, and there > is no evidence of this happening (and in fact, a CMDEXIT would have > prevented this from another system) > > There are no clues in this system’s syslog as to what triggered this. Nothing > in > LOGREC either. > On the other systems we can see the usual messages indicating a system has > left (ISG378I, MIM saying a system may be inoperative, etc.) but nothing else > useful. > > Has anybody else experienced this? > This is a z/10 (2098-Z03) - I don’t know what level of microcode. All 14 > sysplex > members being at z/OS 1.13, mostly RSU1308 or higher. > > > Regards and thanks > Paul > ---------------------------------------------------------------------- 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
