On Sat, 15 Sep 2018 08:52:55 -0400, Peter Relson wrote: ><snip> >On Sat, 20 Apr 2013 14:39:08 -0400, Peter Relson wrote: > >... The documentation says "The STCKCONV macro converts an input > >time-of-day (TOD) clock value to time of day and date, and returns the > >converted values to the caller in the format requested. " This is correct > >and is complete and is all that the service can say. > .... >As has been mentioned before, there is no reason to talk about a timezone >in this context. >A time-of-day clock value is a time-of-day clock value. That value is >defined in PoP. Since 0 represents 1900 and since bit 51 ticks every >microsecond, bits 0-51 form a number that is the number of microseconds >since 1900. > What date and time in 1900, and what time scale? GMT? UTC? UT1? Ephemeris tme? Terrestrial dynamic time? ...?
I believe a programmer might reasonably expect that STCKCONV usefully return whatever TIME would have returned at the instant of the STCK. >I'd be quite happy to have the documentation clarify that the conversion >does not account for leap seconds. RCF submitted. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
