This should be an easy one. What if any are the impacts to scheduled agent run-times resulting from the change in DST? For example, would a daily scheduled agent start running an hour later for 3 weeks in March, or would an hourly agent think it needs to run 2 minutes after finishing at 1:58AM Sunday March 11?
Subject: DST Affects on Scheduled Agent Runtimes
DST is not a new thing, it’s just starting on a different day this year.
Subject: RE: DST Affects on Scheduled Agent Runtimes
Hi,
Someone post something about the Agent manager and the DST issue :
http://www-10.lotus.com/ldd/nd6forum.nsf/DateAllThreadedWeb/a2eb3371b4faae458525726d004e4cf5?OpenDocument
It seems that the agent manager will be mixed during the next 24 hours when the time changed…
I’ve asked IBM 2 weeks ago and i’m waiting for a “final” answer…
JYR
Subject: RE: DST Affects on Scheduled Agent Runtimes
Best way to know for sure would be to test it yourself on a VmWare image or a test server that has not had the DST 2007 hotfix yet.
Subject: RE: DST Affects on Scheduled Agent Runtimes
yeah but that happens every year, regardless of whether it starts on the first Sunday in April (old) or the second Sunday in March (new) so it really has nothing to do with the recent change other than it will happen 3 weeks sooner.
Subject: RE: DST Affects on Scheduled Agent Runtimes
FYI…
Subject: DST Affects on Scheduled Agent Runtimes
There will not be any impacts on scheduled agents as long as the server is properly patched (OS and Domino if needed) as far as I know. There’s no timezone setting in the agent itself, it basically takes the time from the server to know when to run, and IBM didn’t mention any of this in all of the DST 2007 related documentation they have on their site since December…
Subject: RE: DST Affects on Scheduled Agent Runtimes
Thanks guys. I figured it was a non-issue given the lack of any noticeable mention of it anywhere.