Paul Gilmartin wrote:
On Tue, 17 Jun 2008 08:27:18 -0700, Edward Jaffe wrote:
Keep in mind that the TOD clock represents GMT (or UTC). Local time is
calculated by adjusting GMT by CVTLDTO and CVTLSO. If the TOD drifts by
a second or more, you can fix local time with a compensating adjustment
to the time zone offset. See SET TIMEZONE= command.
Gaaaaaah! Since Good Practice dictates that critical timestamps
be kept in UTC (or GMT) your suggestion more conceals the problem
of drift than fixes it.
The whole point of using UTC (or GMT) time stamps is to avoid issues
when the time zone offset is changed. For these logging applications,
local time is irrelevant.
How will this affect the time reported by z/OS Unix programs which
use time() to get UTC and strftime() to get civil time? How will
this affect Java applications?
I don't know how z/OS UNIX programs compute local time. If they use a
technique that does not rely on CVTLDTO and CVTLSO, they are already
out-of-sync with the rest of the system.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
