It depends on how much a z/OS site needs, or doesn't need, precise timing. Server Timer Protocol can add a leap second at the appropriate time (goes into a wait for the second), or it can gradually 'steer' the time over seven hours, gradually correcting the system time.
Attached is nice document that explains STP's handling of leap seconds in fairly gentle terms. http://www-01.ibm.com/support/docview.wss?uid=tss1wp102081&aid=1 So the answer to both questions isn't necessarily "Yes", and that's not necessarily a bug. Ant. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Friday, 3 July 2015 11:27 AM To: [email protected] Subject: Re: Leap Second today! On Thu, 2 Jul 2015 13:36:26 -0400, Ed Finnell wrote: >Yikes. Too much hasenpfeffer... > >http://www.wired.com/2012/07/leap-second-glitch-explained/ > In my time zone, the leap second occurred at 17:59:60. So, I wonder about the z/OS STIMER macro: If, at 17:59:59 I had issued STIMER WAIT,LT=[18:000:01] would the wait have expired in 3 seconds? If, at 17:59:59 I had issued STIMER WAIT,BINTVL=[3 seconds] would the wait have expired at 18:00:01? Unless the answer to both questions is "Yes," there's a bug. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
