In a recent note, john gilmore said: > Date: Wed, 19 Apr 2006 18:47:02 +0000 > > STCKCONV and CONVTOD both use a table, the current instance of which can be > examined on page 7-189 of the z/Architecture principles of operation > publ.ication, SA-227632-04. (Worth noting is that this manual, published in > 2005 September, already included the EOY 2005 leap-second entry.) > Good. Perhaps the schedule the publication deadline to match the IERS announcement.
Heh. Heh. Heh. I wonder what happens if I give it an ETOD reading corresponding to 2005-12-31 23:59:60.5? It should be allowed to report Invalid Argument, since the z/OS protocol is to dispatch nothing during the Leap Second, so no such value can be returned to a program by STCKE. Of course, it could result from a naive arithmetic operation. And there is the matter that some sites may have implemented leap seconds late in the process; at least later than the origin of the table. Maybe it's best just to ignore that. > These conversions are to and from ETOD and UTC, as I think they should be. > Civil time is another kettle of fish/can of worms. I can imagine wishing to > display it, but saving it is always and everywhere unwise. > Similar can of fish, merely requiring a larger table. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
