Converting from local time to GMT
- From: Low.David@xxxxxxxxxxxx (Low, David)
- Date: 10 Nov 2005 12:37:59 -0800
> I'm engaged in an internal dispute about best practice for
> the TOD clock:
> should it be set to universal time (or whatever GMT is now
> called) with the
> appropriate local offset, or alternatively, to local time
> (with an offset of
> zero)?
I'm glad you brought this up. If converting to GMT time will allow us to make time changes without IPL I'm all for it. Looking in the archives I see it's been discussed to death. But I still have questions...
Right now the hardware clock is set to local time with an offset of 4W (which is wrong.) Our CLOCKxx is set to 5W. Command D T shows this:
IEE136I LOCAL: TIME=14.59.44 DATE=2005.314 GMT: TIME=19.59.44 DATE=2005.314
There is a 5 hour difference, all appears to be well. So where does the hardware TZ offset come into play?
Dave Low
Auto-Owners Insurance
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.
- Follow-Ups:
- Re: Converting from local time to GMT
- From: JO . Skip . Robinson
- Re: Converting from local time to GMT
- Prev by Date: Re: WLM Transaction Instrumentation
- Next by Date: Re: Best practice for TOD clock
- Previous by thread: WebSphere AS -- DB2 required?
- Next by thread: Re: Converting from local time to GMT
- Index(es):
Relevant Pages
|
|
