Daylight saving Time and implications
Posted: Mon Oct 30, 2006 1:06 pm
Hi,
Our jobs are scheduled daily, via Director, at 1:40AM. In the morning of 10/29/06 (daylight saving time enforced), the job that was running when the time switch was to take place, kept running for about 24 hours and then completed successfully. My question is, when the clock struck 2AM, the server time was clocked back by an hour to 1AM. This would mean that the jobs are not yet scheduled (as per windows scheduler), but jobs are already running (as per DataStage server).
1. What should, ideally, happen in this situation? I am assuming the execution should proceed forward without any glitch since the event has already been triggered and there is no mechanism to trace time and backtrack.
2. Now, after 45 minutes (at the 'new' 1:45AM), will the scheduler kick in again?
gateleys
Our jobs are scheduled daily, via Director, at 1:40AM. In the morning of 10/29/06 (daylight saving time enforced), the job that was running when the time switch was to take place, kept running for about 24 hours and then completed successfully. My question is, when the clock struck 2AM, the server time was clocked back by an hour to 1AM. This would mean that the jobs are not yet scheduled (as per windows scheduler), but jobs are already running (as per DataStage server).
1. What should, ideally, happen in this situation? I am assuming the execution should proceed forward without any glitch since the event has already been triggered and there is no mechanism to trace time and backtrack.
2. Now, after 45 minutes (at the 'new' 1:45AM), will the scheduler kick in again?
gateleys