Applications Manager handles the special circumstances associated with the fall and spring daylight saving time changes.
Daylight Saving Time begins for most of the United States at 2 A.M. on the second Sunday of March. Time reverts to standard time at 2 A.M. on the first Sunday of November. In the U.S., each time zone switches at a different time. In the European Union, Summer Time begins and ends at 1 A.M. Universal Time (Greenwich Mean Time). It starts the last Sunday in March, and ends the last Sunday in October. In the European Union, all time zones change at the same moment.
Applications Manager scheduling during the daylight saving time conversions is done the same as usual. Special circumstances for each conversion are described below.
The Fall Conversion
Below is some information about the fall time change:
For example, a task scheduled to run at 1:30 A.M. will not run twice.
For example, a task scheduled to run every hour on the half hour will run at 1:30, and will not run again until 2:30 (which is actually two hours later).
If you want a task to run every hour on the half hour, including the second 1:30, you could schedule it to run every 60 minutes.
Tasks that are running during the transition time should finish as usual.
Evaluating Time-Relevant Conditions During the Fall Conversion
The conditions that reference time behave according to the time that the condition is executed. For example, if a condition with a DELAY TASK action executes at 1:59 and delays for 5 minutes before the time change, the task will execute at 2:05. This will be one hour and 5 minutes later.
Tasks That are Scheduled at 2:00 A.M. During the Fall Conversion
Tasks which are scheduled to run at 2:00 A.M. behave the same in v6.x as they have with other Applications Manager versions. Their appearance in the Backlog will be slightly different.
Jobs and process flows that are scheduled to run at 2:00 A.M. in v6.x will launch at 1:59 A.M. Their status will shortly change to DATE PENDING or PRED WAIT. Process flow components will go to a STAGED, STAGED_PW, or STG SKIP status. All tasks will remain in those statuses for an hour, until 2:00 A.M. They will then run normally.
The Spring Conversion
When the time jumps ahead at 1:59 A.M. in the Spring, all jobs and process flows with start times between 1:59 A.M. and 3:00 A.M. will be picked up by the automation engine and submitted immediately.
If you have done both of the following for one or more jobs, those tasks will abort during the spring time change:
If this happens, you can resubmit the task to run it to completion.
Evaluating Time-Relevant Conditions During the Spring Conversion
The conditions that reference time behave according to the time that the condition is executed. For example, if a condition with a DELAY TASK action executes at 1:59 and delays for 5 minutes before the time change, the condition will be evaluated again in 1 minute. The reason for this is that as soon as the hour ends, it becomes 3:00 and the action is eligible to be taken immediately.