I'm in the same boat. I use Help Desk, Change and Approval, all 5.0. ARS 5.1.2 and Mid-Tier 5.1.2. The approval and acceptance process is nuts here, to do an upgrade of such a visible system in short order is impossible.
>From what I read, the big areas of concern (Web Services, import and export of applications and times displayed via mid-tier) aren't a concern for me. We don't use web services, won't import/export apps and only end users use mid-tier for self service, and they don't care if the time is an hour off. So am I missing anything or can we get by w/ just patching the OS/DB? Jack -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Scott Sent: Thursday, February 01, 2007 7:01 AM To: [email protected] Subject: Re: DST and consequences Ann, I'm right there with you. We're stuck on 5.1.2 until we can put new hardware In place to handle 7.0.1 and CMDB 2.2. However, I am even less affected because our servers are located in Arizona, so even the OS won't change time zones, which is a bigger consideration in regards to the way escalations will play at the 2:00 am to 3:00 am time shift. But since you have been through DST throughout the life of your setup, this shouldn't be an issue unencountered. As long as the users who look at the submission times for there records are comfortable knowing that the time offset between the web view and their system clock is only cosmetic, there shouldn't be any real issues in your (and my) case. Thanks, Bruce Scott Application Developer - Remedy SSG, PetSMART, Inc. eMail: [EMAIL PROTECTED] -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of A R Kosch Sent: Tuesday, January 30, 2007 2:03 PM To: [email protected] Subject: DST and consequences We are using ARS 5.1.2 and Mid-Tier 6.3 on Solaris 8. Solaris is patched for DST already. I'm trying to make sure I'm understanding everything about DST and this mix because I'm not convinced an "hour off" for a month matters for us. This isn't Y2K all over again; done that. According to the DST Product alert, the consequences for not mitigating for DST changes under ARS 5.1.2 are "Web Services and Import/Export time calculations will be off by 1 hour". We don't use these things in a way that it would matter. No mention of Java specifics in that table for ARS 5.1.2. Also, the Mid-Tier 6.3 will be off an hour. Looking at patch 20, java then needs patching. Given how simply we use Remedy Help Desk and lite Change, I can't see why this makes much difference. Web client customers don't take an hour-by-hour view; it isn't that granular for them. Also, in April the old DST rules kick in and the difference should be corrected. Right? So, some things will be off for web client activities by an hour for a month.... I don't mind patching Mid-Tier 6.3 to patch 20, although I'd like some reassurance that it will work with unsupported ARS 5.1.2. That seems risky for other reasons. =20 I've asked my unix sys admin about moving the dev server clock to March 10 to follow Remedy through the change and to test the clients.=20 I wish we weren't stuck at ARS 5.1.2 but I've no support yet for hardware to be otherwise. We may even survive Vista, IE7, and DST but something will get us eventually. I really appreciate all the time people have taken to post information about this and other issues. Maybe if someone else was considering being ornery about riding this out, this will help the process. Cheers, Ann Kosch ~*~ ~*~ ~*~ Ann R Kosch Special Projects/Analyst Remedy ARS Administrator/Coordinator [EMAIL PROTECTED] 785-532-4933 Kansas State University Computing and Telecommunications Services Web Technologies section ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ######################################################################## #= ############ The information contained in this electronic mail message, including atta= chments, if any, is PetSmart confidential information. It is intended on= ly for the use of the person(s) named above. If the reader of this messa= ge is not the intended recipient, or has received this message in error, = you are hereby notified that any review, dissemination, distribution or c= opying of this communication is strictly prohibited. If you are not the = intended recipient or have received this message in error, please notify = the sender via e-mail and promptly delete the original message. ######################################################################## #= ############ ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
