> >> So it actually waits for 4 seconds rather than the 3 requested. > > > >The problem is that at 17:59:59 when the STIMER is processed we > >don't know that a leap second will occur at 18:00. > > > Actually, you could have known that for 4 months, ever since the > IERS announced the leap second. (Less the time it takes for a > PTF to be created, distributed, and installed.) I don't believe > (but I've already been wrong once) that a programmer can request > a GMT or LT more than 4 months in the future.
Leap seconds are scheduled via STP or the sysplex timer. z/OS can only know about a leap second when it gets the Time Control Parameter Change event external interrupt for STP or the ETR Alert event external interrupt for ETR. George Kozakos z/OS Software Service, Level 2 Supervisor ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
