I confess that I have found this thread puzzling.
IBM has provided the "fixes" needed to cope with the overflow of the traditional 8-byte/64-bit STCK value that will occur in September 2042. They take the form of an STCKE value which is 16 bytes/64 bits in aggregate size Its structure is not, however, so simple as that of an STCK value, which is a single 64-bit unsigned binary integer. The STCKE has three components. From left to right, low to high storage address, they are +-----+ | x'00' |, a one-byte prefix, +-----+ +----------------------------//---------+ |<---104-bit unsigned binary integer---->| +---------------------------//----------+ +-----+-----+ | | |, two-byte TOD programmable register. +-----+-----+ I leave it as an exercise for the reader---The answer can be found in at least one Redbook---to determine when this register will overflow for the epoch origin midnight, 31 December 1899; but 2^104 = 20,282,409,603,651,670,423,947,251,286,016. Timely support for STCKE values will certainly be provided (is in some cases already provided) in statement-level procedural languages and the like. HLASM programmers do, however, need to replace STCKs with STCKEs and make the necessary target field-width changes in existing code (and, of course avoid STCKs in new code); but this has been obvious for years. John Gilmore Ashland, MA 01721-1817 USA _________________________________________________________________ Hotmail® is up to 70% faster. Now good news travels really fast. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009 ---------------------------------------------------------------------- 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
