Re: Leap seconds and the Server Timer Protocol

2012-03-13 Thread John Gilmore
Radoslaw has made the essential point. Times like hh.mm.60 are rejected as syntactically illicit by time-vetting routines, conversion routines, and the like. Glonass, RS's example, did hang for just this reason. There is a strong consensus among the members of the several international committ

Re: Leap seconds and the Server Timer Protocol

2012-03-13 Thread R.S.
W dniu 2012-03-13 22:28, Paul Gilmartin pisze: On Tue, 13 Mar 2012 16:12:07 -0500, John Gilmore wrote: The sequence 2012 June 30, 23h 59m 59s 2012 June 30, 23h 59m 60s 2012 July 1, 0h 0m 0s will certain

Re: Leap seconds and the Server Timer Protocol

2012-03-13 Thread Paul Gilmartin
On Tue, 13 Mar 2012 16:12:07 -0500, John Gilmore wrote: > >The sequence > > 2012 June 30, 23h 59m 59s > 2012 June 30, 23h 59m 60s > 2012 July 1, 0h 0m 0s > >will certainly appear in the transmitted sequence, but

Re: Leap seconds and the Server Timer Protocol

2012-03-13 Thread John Gilmore
Paul, The sequence 2012 June 30, 23h 59m 59s 2012 June 30, 23h 59m 60s 2012 July 1, 0h 0m 0s will certainly appear in the transmitted sequence, but its middling term was chosen to call attention to itself

Re: Leap seconds and the Server Timer Protocol

2012-03-13 Thread Paul Gilmartin
On Tue, 13 Mar 2012 16:45:35 -0400, Robert A. Rosenberg wrote: >At 14:41 -0500 on 03/13/2012, John Gilmore wrote about Leap seconds >and the Server Timer Protocol: > >>This is the title of a new this month IBM Techdocs White Paper, >>WP101091, by Gregory Hutchison,

Re: Leap seconds and the Server Timer Protocol

2012-03-13 Thread Robert A. Rosenberg
At 14:41 -0500 on 03/13/2012, John Gilmore wrote about Leap seconds and the Server Timer Protocol: This is the title of a new this month IBM Techdocs White Paper, WP101091, by Gregory Hutchison, a PDF of which can be downloaded from the IBM Techdocs website. What is the URL of the site

Re: Leap seconds and the Server Timer Protocol

2012-03-13 Thread Paul Gilmartin
On Tue, 13 Mar 2012 14:41:32 -0500, John Gilmore wrote: > >Be aware that the next leap-second insertion will be at 11:59:59 UTF >on 30 June 2012. > UTF? I don't know the TLA. But I'd say UTC 23:59:59.999..., perhaps a second later than yours. And I know we disagree on this, but, from: http

Re: Leap seconds and the Server Timer Protocol

2012-03-13 Thread John Gilmore
Quite right! It is WP102091. I am suitably repentent. --jg -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Leap seconds and the Server Timer Protocol

2012-03-13 Thread George Kozakos
The correct# is WP102081 George Kozakos z/OS Software Service, Level 2 Supervisor -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Leap seconds and the Server Timer Protocol

2012-03-13 Thread Field, Alan C.
It's actually WP102081. WP101091 talks about TS7770. Alan -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of John Gilmore Sent: Tuesday, March 13, 2012 14:42 To: IBM-MAIN@bama.ua.edu Subject: Leap seconds and the Server Timer Protocol

Leap seconds and the Server Timer Protocol

2012-03-13 Thread John Gilmore
This is the title of a new this month IBM Techdocs White Paper, WP101091, by Gregory Hutchison, a PDF of which can be downloaded from the IBM Techdocs website. Some of you may well find his discussion of the distinction between the insertion (or, in principle, removal) of a leap second 1) by stee