I don't want to beat this to death, but locale settings are about "formatting output" given a locale. I don't think it is common at all to apply UTC offset (or timezone / DST) using locale. Even if locale did support this, what is the effect of this on your database and applications? The data stored in the file is whatever you put in. Is the timestamp stored by DB2 as UTC (0 offset), so that after you read a record, you can manually apply job level offsets to present the timestamp in locale context?
All of that can be done if you write your applications that way... The developer must apply those conversions to date-time values so that it overrides the standard default behavior of the platform.
In this case, OS400 does NOT manage date-time offsets in the database I/O functions, so all date/time functions take on the same context... System time...
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Darryl Freinkel
Sent: Friday, April 13, 2012 12:43 PM
Subject: RE: MIDRANGE-L Digest, Vol 11, Issue 566
What you are saying is not true. I know that using Java or C you can change
the value in the locales for the time. It is obviously commonly used in C or
Java environments. As I am not a C or Java person, I do not have access to
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact