Managing daylight saving time and time-initiated automation

In earlier releases of BMC AMI OpsA, when you changed the IBM MVS Local Time to observe daylight saving time, time-initiated EXECs and time-initiated Rules would not detect the change in the MVS Local Time; you had to restart the BMC AMI OpsA address space.

You must still carefully review your time-initiated EXECs or time-initiated Rules to determine how the time change might affect your automation. As the examples in Scenarios show, you might discover that the time-initiated automation might execute more or fewer times depending on whether the MVS Local Time is changed to an earlier or later hour.