Neither rhetorical nor humorous. How about hypothetical? We did not 'power down' an SE. It failed--as weenie-ware is wont to do. It got fixed within a reasonable period, so no harm, no foul. I was merely wondering WHAT-IF the second SE failed--as weenie-ware is wont to do--before the first one got repaired.
Rob Schramm's post comes at an interesting juncture. We happen to have had another SE failure. This one cannot simply be 'fixed'. It appears that a POR is required to resync the surviving SE with the CEC. Or vice versa. Looks like I have some meat for my SHARE Bit Bucket slot in Atlanta. ;-) . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Rob Schramm Sent: Tuesday, April 19, 2016 6:42 PM To: [email protected] Subject: (External):Re: What happens with no working SE? Ok.. So how many people leave their "l am down to one SE z machine" powered down for lengthy periods of time that is not a DR machine? Or is running production on a single SE machine for a long time using STP? I am hoping that my questions are somewhat rhetorical or humorous and completely lacking in the "Homer Simpson duooh!!" head slap. It would be like running an older multi-CEC sysplex with a single ETR expecting no single point of failure. Rob Schramm On Tue, Apr 19, 2016, 5:06 AM linda golding <[email protected]> wrote: > Am curious . This is what i could find looking at the enhancements . > Since you say STP doesn't steer the clock , i would like to know how > this works these days . > > *http://www-03.ibm.com/systems/z/advantages/pso/stp/ntp.html > <http://www-03.ibm.com/systems/z/advantages/pso/stp/ntp.html>* > > > *Service Element (SE) Time Accuracy* > As a continuation of the zEnterprise 196 (z196) timing accuracy > improvements for an STP-only CTN, namely, SE/CPC hourly clock steer > and synch, the zEnterprise EC12 and zEnterprise BC12 have expanded > these enhancements by allowing the SE to access an STP > panel-configured External Time Source (ETS), even when the CPC is powered off > or has not been IMLed. > The SE achieves this by invoking the ETS-configured NTP servers to > obtain the ETS-SE time difference and steers the SE clock towards the ETS > clock. > During IML, the more accurate SE clock time transfers to the CPC > clock, maximizing the CPC timing accuracy. > > This feature is available exclusively on zEnterprise EC12 and > zEnterprise BC12. > > Thanks , > > Linda > > > > > > > > On Tue, Apr 19, 2016 at 1:57 PM, R.S. <[email protected]> > wrote: > > > W dniu 2016-04-18 o 23:19, linda golding pisze: > > > >> One of two SE failed means you can peform everything you want, > >> including STP. Maybe STP setup would be impossible (I haven't > >> checked), but I'd > bet > >> it is also possible. > >> I've been working with single SE (primary failed) for some time. It > wasn't > >> my dream, but I could live with it. >>>> > >> > >> > >> I thought STP code runs on the support element . Access to the NTP > server > >> from the CTS is initiated and controlled by the Support Element. > >> > >> In that case , a sysplex would die when support element is not > available . > >> > > NTP is not STP. > > STP is managed from HMC/SE but it doesn't mean the SE is steering > > the clock. > > NTP can be used for "wall clock" time adjustment, but STP will work > > without NTP at all or with NTP failure. > > Last, but not least: multi-CPC STP configuration will survive any of > > the CPC failure. Not only SE, but whole CPC. > > > > -- > > Radoslaw Skorupka > > Lodz, Poland ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
