Skip to Content

Considerations for changing the IBM MVS local time

Consider the following recommendations when you prepare to change the MVS Local Time to observe daylight saving time:

  • Change the MVS Local Time during a quiet (or low activity) period when no timer requests are scheduled to run.
  • Avoid changing the MVS Local Time precisely on the hour because it is more likely that you have defined automation (such as time-initiated Rules and EXECs) to execute on the hour.

Related topic

Managing-daylight-saving-time-and-time-initiated-automation

To view the MVS Local Time, enter the MVS command:

D T
Success

Tip

You must advance the MVS Local Time at least 30 minutes later so that BMC AMI Ops Automation can recognize that a DST time change has occurred. This lessens the possibility that BMC AMI OpsA erroneously detects a DST time change when higher priority work in the PAS prevents BMC AMI OpsA from running.

In contrast, BMC AMI OpsA recognizes a DST time change whenever you adjust the MVS Local TIme backwards (or earlier) by any amount of time.

When BMC AMI OpsA detects the daylight saving time change, two new messages are issued and you can write automation that is triggered by these messages:

AL3004I   TIME CHANGE DETECTED hh.mm.ss -> hh.mm.ss
AL3022I  TIMERS ADJUSTED FOR DAYLIGHT SAVING TIME

Additional considerations

BMC recommends that you try to follow the IBM guidelines and that for both sysplex and non-sysplex installations, you change the time by changing the TIMEZONE offset setting and you do not change the TOD clock.

For IBM recommendations for setting the TOD clock, see the IBM documentation MVS Planning: Operations.

IBM explains the recommended method for setting the MVS clock in the IBM publication MVS Planning: Operations.

This section contains the following topic:

 

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

BMC AMI Ops Automation 8.4