On Fri, 7 Jun 2013 07:29:09 -0500, John McKown wrote: >IMO, if IBM were to store the creation date & time, then the only logical >value to store is the STCKE value taken somewhere within the allocation >process. It is 16 bytes in length and cannot be made any more accurate >because the hardware doesn't support a greater accuracy. It is not human >readable, but SO WHAT? It is easy to convert using HLASM and the STCKCONV >macro. I wish that the LE people had an STCKE value to Lilian date/time >conversion routine. But, again, that would be easy to write in HLASM. > Does STCK still guarantee unique readings, even subsequent to the advent of STCKE?
24 hours of binary mircoseconds isn't very human readable either. And still using local time leaves wide open the hour of uncertainty every fall. It makes no sense to provide microsecond resolution while tolerating that hour of uncertainty. Were the designers even thinking? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
