Tim Shoppa's contention,
I believe this means that the clock time is actually more directly
related to the TAI timescale or
GPS hex time than UTC.
is in fact right on.
Like most discussions of dates and times here, this thread has failed to
make some necessary distinctions. The current z/Architecture TOD clock
value, accessed using the [unprivileged] instruction STore ClocK Extended,
STCKE, yields a monotone increasing ETOD-clock value that is a count of the
number of clock units that have elapsed since midnight, 1899 December 31.
The TIME macro (q.v.) can be used to convert ONLY a current STCKE value into
a Gregorian date-time value and format in various ways.
Two other IBM-supplied callable services are available:
o STCKCONV converts arbitrary, in general non-current ETOD values into
date-time ones; and
o CONVTOD converts an STCKCONV date-time value [back] into an ETOD value.
All three of these facilities make the necessary corrections for the
peculiarities of the Grergorian calendar; the facilities they provide are
comprehensive; and they should always be used in preference to homegrown
conversion routines, which no non-specialist programmer ever gets right.
John Gilmore
Ashland, MA 01721-1817
USA
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
----------------------------------------------------------------------
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
