Greetings,



We have been sitting on this one since DB2 v1.2... We are currently on
DB2 UDB v8.2.



Our main server is in the Eastern Time Zone, but our branches span into
the Central Time Zone. I believe we've always had the CTZ computers set
to ETZ time and never really thought much about it for the past 14(?)
years. In the age of modern computing, someone suggested that we let the
CTZ users have their PC's set to their local time. Since time is stored
on the server in GMT (as I understand it), how do I get computers in two
different time zones to store and display the correct time.



Example:

Someone performs a sales transaction in Tennessee at creates a receipt
at 16:00. If the offset from GMT is 6 hours, then the time stored is
10:00 (again, as I understand it). If someone in the ETZ looks at the
transaction, would it not then display as 17:00?



How do I get computers in two different time zones that are using the
same source server to consistently store and display the correct time.
Does anyone currently do this out there? How do you over come the
(possible) paradox of displaying the same transaction in two different
time zones?



Douglas Kostelnik

Senior Database Administrator/Architect




------------------------------------------------------------------------
The information transmitted is intended only for the person(s) or entity to which it is addressed
and may contain confidential and or privileged material and should be treated as a confidential
AAA Auto Club South communication. If the reader of this message is not the intended recipient, you
are hereby notified that your access is unauthorized, and any review, dissemination, distribution, or
copying of this message including any attachments is strictly prohibited.
========================================================================

DB2 & UDB email list listserv db2-l LazyDBA home page