Thanks Lizette. I couldn't see any DASD contention at all. The last message on the syslog (and OpsMVS log) is 10 seconds before the hardware log message. Nothing untoward there. There are no SVC dumps from around the time of the problem. I'll check SMF ...
Regards and thanks Paul -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Monday, March 23, 2015 2:03 PM 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 Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names used by the Atos group. The following trading entities are registered in England and Wales: Atos IT Services UK Limited (registered number 01245534), Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited (registered number 08514184) and Canopy The Open Cloud Company Limited (registration number 08011902). The registered office for each is at 4 Triton Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983. This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
