Daylight Saving Time Impact on the Robot Products

Before You Begin

Starting in 2007, Daylight Saving Time (DST) was extended to start on the second Sunday in March and end on the first Sunday in November.

This document describes the impact of this extension of Daylight Saving Time on the Robot automated operations products. This information applies whether you change the system time manually, or use the IBM system value QTIMZON to switch to and from daylight savings time automatically. If you change the QUTCOFFSET system value manually, these instructions also apply.

Robot/SCHEDULE is affected by the time change as it is very time sensitive. Robot/ALERT and Robot/NETWORK also can be affected. See the following instructions to review your setup: "Assessing the Impact of DST."

Robot/SCHEDULE

Robot/SCHEDULE must be inactive when the system time changes. See the Help/FACTS “Using Robot/SCHEDULE with the QTIMZON System Value” to update the system time automatically.

If you prefer to manually control the system time change, as well as the shutdown and startup of Robot/SCHEDULE, see the Help/FACTS “Using Robot/SCHEDULE to Automate Daylight Saving Time Change.”

Robot/ALERT

Robot/ALERT has a time zone offset value under System Setup/System Defaults that you should review to see if it needs to be changed. You can change this offset value to default to the QUTCOFFSET value.

Robot/NETWORK

You must end and restart Robot/NETWORK version on the Host(s) and Nodes to ensure it recognizes the new time zone offset. Robot/NETWORK places the QUTCOFFSET system value in the NETNODE and NETHOST job logs at startup, and doesn’t update it again.

Updated March 22, 2012 JR