This has been discussed before and is explained very well in this IBM techdoc:
https://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102081 Depending on if you need to be exactly on time after the leap second occurs, or can tolerate taking a while to 'smear' the time to the new value, STP gives you the choice of spinning whilst waiting for an extra leap second to be inserted (Category 1) or slowly steering the time (Category 2): STP will begin to slowly steer the mainframe time to the new value. It takes approximately 7 hours for STP to steer out a one second delta. Dana On Wed, 3 May 2017 10:25:36 -0600, Paul Gilmartin (π) <[email protected]> wrote: > >z/OS shuts down all applications for leap seconds. Would any >application have a problem with a 1-second outage? (Shutting >down to go forward would seem to aggravate any problem.) >Every leap second there are reports of network crashes. Amazon >and Google smear the leap second over a several-hour interval >to avoid transients. (Different durations; there is no standard.) >z/OS might do well to get on board with leap second smearing, but >that could be tricky with the TOD/STCK/CVTLSO design. > >-- gil > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
