Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Managing daylight saving time and time-initiated automation

BMC AMI Ops Automation

 supports running time-initiated EXECs and time-initiated Rules through a daylight saving time change without requiring you to recycle 

BMC AMI OpsA

.

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.

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*