So I guess this will teach me to be off of the list for an extended period of time. I was essentially under the impression that this DST was really an OS change and we would not have to make any changes on the application side. My bad.
We're on ARS 6.0.3 patch 16, WIN2k, SQl2k, no Midtier, we are using web services for one piece of functionality. According to the pdf table on the BMC web site I would need to install patch 20 in order to keep everything in sync. There seems to be a lot of problems with patch 20. I am thinking how bad could it be if I don't apply this patch. Anybody care to give an opinion on this course of action? Thanks, Roger A. Nall Manager, OSSNMS Remedy T-Mobile USA Desk: 813-348-2556(New) Cell: 973-652-6723 FAX: 813-348-2565 sf49fanv AIM IM RogerNall Yahoo IM ________________________________ 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 12:41 PM To: arslist@ARSLIST.ORG Subject: Re: DST and Time Calculation White Paper? 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: arslist@ARSLIST.ORG 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: arslist@ARSLIST.ORG 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___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
