Some folks run their entire network (clients, Mid-Tier, DB, servers, etc.) under GMT/UTC - i.e. they do not use local time zones. Since they do not use local time zones, they are unaffected by changes to DST anywhere within the network. I do not know if anyone on the list is actually doing this but if they are, perhaps they can give you the pros and cons of such a setup. -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc.
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Susan Palmer Sent: Tuesday, February 27, 2007 10:30 AM To: [email protected] Subject: Re: DST and Time Calculation White Paper? ** I don't understand what you're saying here Norm .... GMT?????? Susan On 2/27/07, Kaiser Norm E CIV USAF 96 CG/SCWOE <[EMAIL PROTECTED]> wrote: ** So then what's all the talk we've been hearing of, "Set the server to GMT! Set the server to GMT!" I don't see what that would get you. ________________________________ From: Action Request System discussion list(ARSList) [mailto: [EMAIL PROTECTED] On Behalf Of Easter, David Sent: Tuesday, February 27, 2007 11:23 AM To: [email protected] Subject: Re: DST and Time Calculation White Paper? Both the client and server use the operating system for localtime calculations. The Mid-Tier, web services and import/export use a 3rd party library supplied within AR System or Java for localtime calculations. This is why the technical bulletin refers to these functions in explicitly and why the patches for 6.3 and 7.0.01 contain an updated version of these libraries and/or require the patched versions of Java. The conversion is done at the client for client queries, displays or submissions. It's done at the server for workflow driven manipulations ( e.g. push field) of date/time information. Thanks, -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CG/SCWOE Sent: Tuesday, February 27, 2007 8:34 AM To: [email protected] Subject: DST and Time Calculation White Paper? ** Hi all: I'm still trying to wrap my head around all the DST ramifications for 5.1.2, and I guess I'm thinking it would help if I had a technical white paper or other document that specifies exactly how Remedy 5.1.2 calculates time and time conversions. Here's my thinking: The Remedy server stores all time values as Unix time, which is the total of seconds since 1 January 1970 GMT. Time values, then, get stored in a number field in the database (as opposed to a date/time field). Accordingly, if a user passes a date and time in a search query, Remedy must convert the date and time supplied by the user to the equivalent Unix time. It must do this by first adding or subtracting the appropriate number of hours based on the time zone and then possibly add an hour for DST. If you run such a query, which piece of Remedy does this conversion before the query is passed to the underlying database? Is it the server or the client? Does the client do the time conversion before the query is passed to the server or does the client just pass the query to the server as-is and the server does the time conversion? If the server does the time conversion, is it saying, "OK, I got a time value in this query I'm to execute. So let me convert the time to something I truly understand. So let's see now...what time zone am I in...and are we observing daylight savings time?" I assume, then, that the server queries the operating system for the timezone??? And does it query the operating system for whether or not the time zone is currently observing DST? It can't, in my mind, otherwise there wouldn't be a bug. It must be calculating whether or not DST is being observed itself based on its own internal date/time algorithm? Yes? Does anyone know the answers to these issues or know of a whitepaper that definitively describes how Remedy calculates time? Thanks, Norm __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
