** Thanks all. I believe we will just disable escalations for that hour on the night of the change, as we do use the ITSM 6.0 apps and I really don't want to customize all of them right now. I appreciate all the insight and suggestions.
Thanks a lot everyone!!!!!!!!! -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David Sent: Monday, October 01, 2007 2:14 PM To: [email protected] Subject: Re: Clarification on DST ending Joe, This might not help. Part of what I've seen in the past is that a duplicate pair of escalations are spawned. It might help to stop the second one from triggering but depending on timing they might fire at the same time. We usually have to cycle the app to get rid of the dups. Dave _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Monday, October 01, 2007 2:06 PM To: [email protected] Subject: Re: Clarification on DST ending ** Its a pretty rare exception so I'm not surprised its not handled. Its not applicable to a lot of countries anyway, but considering the ARS was primarily designed and used in the west, where use of DST is more common, maybe its time they do include such exceptions in their workflow where workflow based on time as in Escalations could stand impacted. Honestly if Jolie hadn't pointed out her problem I wouldn't have thought of that exception either.. not until an application was impacted.. Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Shellman, David Sent: Monday, October 01, 2007 1:57 PM To: [email protected] Subject: Re: Clarification on DST ending ** It would be nice if we would have designed our escalation to run that way here at TycoElectronics but we haven't. I doubt that the OOB escalations execute that way either. Good suggestion though. Dave _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Monday, October 01, 2007 1:54 PM To: [email protected] Subject: Re: Clarification on DST ending ** Yes I understand the reason why its happening. I was suggesting a workaround for it not to happen by time stamping the run time of the escalation and having an inclusion on the run if condition to make sure that the last time it has fired is greater than 1 or 2 hours as the case may be so it fires the next time only on the next night, thus eliminating the exception when the time is reset due to DST adjustments. Cheers Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Shellman, David Sent: Monday, October 01, 2007 1:48 PM To: [email protected] Subject: Re: Clarification on DST ending ** Joe, We've seen this behavior for years. It happens with escalations that are set to fire in the 2:00 AM to 3:00 AM time frame. I think it also happens with escalations that are just set to fire at intervals. Dave _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Monday, October 01, 2007 1:41 PM To: [email protected] Subject: Re: Clarification on DST ending ** Joelie, A workaround could be having the escalation check for the last time it fired, and not fire if it has already fired an hour or 2 ago. This would mean you would have to customize your form for having the last time the escalation fired and setting that timestamp there and fixing the run if condition on your escalation accordingly.. Cheers Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Shellman, David Sent: Monday, October 01, 2007 1:17 PM To: [email protected] Subject: Re: Clarification on DST ending Joelie, I would say that it depends. A lot has to do with how the system clock is reset. In the past with systems where the system clock is reset immediately we often saw this happen. Some of our UNIX servers were set in a manner that the time change took effect over a period of time and we wouldn't see double escalations. With 7.0.1 Patch 3, I'm seeing slightly different behaviors with escalations than I did with 6.3. Under 6.3 on SUN, when we would set an escalation to fire once a day, it would fire as soon as we saved the escalation. With 7.0.1, patch 003 on Windows, it doesn't fire immediately but will trigger 24 hours later. We may need to have someone from BMC/Remedy give us the true answer. Dave -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Dudley, Joelie Sent: Monday, October 01, 2007 12:38 PM To: [email protected] Subject: Clarification on DST ending I just want to make sure I understand this correctly. When DST ends the first weekend in November the clocks get turned back one hour, in the past this would cause escalation between 2-3 am to fire twice is this still the case? The patch back in the spring was only to change the timeframe of when it was to occurred, correct? Thanks in advance for the clarification. Joelie Dudley Application Developer 555 Walnut Street 7th Floor, Forum Place Harrisburg, PA 17110 Phone: (717) 772-8143 __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"
