×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I agree with this. The offset changes for daylight savings, not UTC. If IBM does it the other way, IBM is wrong. UTC is used for a lot of things other than computer times. One particularly sensitive application is Navigation. If UTC were sensitive to daylight savings all navigation systems on the planet would be messed up, not only that, but daylight savings is applied differently across the globe (and even within the US), so the real UTC could not be daylight savings sensitive.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
-----Luis Rodriguez <luisro58@xxxxxxxxx> wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Luis Rodriguez <luisro58@xxxxxxxxx>
Date: 04/24/2015 10:11AM
Subject: Re: FW: issue with dates in sql server---- Now ESRI issue
On Fri, Apr 24, 2015 at 8:55 AM, <rob@xxxxxxxxx> wrote:
Turns out that IBM i adjusts UTC when you do the time change.
Which makes perfect sense. Greenwich Mean Time - UTC offset = local time.
UTC rightly should change when the time change occurs.
Rob,
Excuse me, but I'm afraid I don't quite follow your reasoning here... Why
should UTC change when adjusting for daylight savings? UTC should be,
AFAIK, independent of any daylight time changes.
Now then, please remember that English is not my primary language, so it
could be that there is something here that I'm not really understanding
properly.. :-)
Regards,
Luis Rodriguez
--
midrange.com
