On Sat, 11 Apr 2009 14:50:17 -0500, Joel C Ewing wrote: >There are what looks like some very versatile z/OS macros to convert >"readable" date-time values to and from TOD and ETOD values, which >someone might be tempted to use as a basis for date-time manipulation. > >It is still a documented restriction (don't know if it is actually true) >that even when ETOD values are used that dates handled by these macros >must still fall within the 2042 limitation. > I tried STCKCONV with X'010000...'. It gives 1900-01-01 (z/OS 1.7 and 1.10).
> ... This is an example of >things that obviously need to change well in advance of when the actual >ETOD overflow occurs into the high order byte, so that code can be >written and tested using dates beyond 2042 well before 2042 arrives. > The format isn't set yet, AFAIK. It's within IBM's prerogative to make it a signed value to support dates before 1900. Should we expect to see an extended clock comparator register, or is that better handled in software, by windowing? -- gil ---------------------------------------------------------------------- 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
