Before posting silly guesses - I should have read 1st the answers in:
IBM publication: Leap Seconds and Server Time Protocol (STP) - 11 February 2015 (pdf) Table on page 4: UTC=23:59:60 NTP/ETS=00:00:00 Leap second inserted. z/OS spins for 1 second. Time UTC=23:59:60 is never passed to any program issuing TIME macro/s and never reported by any application. If STCK instruction is used: "This returns the raw Time of Date (TOD) value. The application needs to convert it to UTC by subtracting the total leap second offset, or to LOCAL time by adding the local time of day offset and subtracting the leap second offset." -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jakubek, Jan Sent: Friday, July 03, 2015 6:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Leap Second today! Replying to myself...likely I'm wrong. I looked through my syslogs but could not find any entry with time stamp of 2015181 19:59:60.xx (June 30th). Did somebody see a syslog entry with date / time 2015181 19:59:60.xx ? -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jakubek, Jan Sent: Friday, July 03, 2015 4:06 PM To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU> Subject: Re: Leap Second today! I think leap second is "magical". All time measuring devices that respect it - stop for one second to observe it. Do I have it right? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu<mailto:lists...@listserv.ua.edu> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
