Does ESP have to be recycled during the time change shifts in spring and fall.
Release: All Releases of Workload Automation ESP
The TIMEZONE initialization parameters are read during initialization of ESP Workload Manager to tell ESP Workload Manager the meaning of various time zone names.
The TIMEZONE initialization parameter has the operand SYSZONE(YES).
The z/OS zone shift will be added to the shift value provided in the initialization parameter. The TIMEZONE initialization parameter with SYSZONE(YES) specifies the zone offset relative to the system's local time.
The following example shows that the local time zone is equal to the central time zone and all other time zones are relative to local. With time zones defined this way, ESP Workload Manager is aware of the change when the system clock is changed. You do not have to recycle ESP Workload Manager.
TIMEZONE 0 LOCAL 0 SYSZONE(YES) TIMEZONE 17 CENTRAL 0 SYSZONE(YES) TIMEZONE 16 EASTERN 1.0 E SYSZONE(YES) TIMEZONE 18 MOUNTAIN 1.0 W SYSZONE(YES) TIMEZONE 19 PACIFIC 2.0 W SYSZONE(YES) TIMEZONE 20 ATLANTIC 2.0 E SYSZONE(YES) TIMEZONE 21 NFNDLAND 2.30 E SYSZONE(YES)
Because the clock moves back in the autumn, there will be 25 hours on the last Sunday of October, with one hour repeating itself. All scheduled activity, including overdue recognition, will happen the first time through the duplicated hour. During the second pass through, ESP Workload Manager will react to triggers and will release successors to work that completes, but will otherwise just wait. Normal activity will resume at the end of the duplicate hour.
You do not need to recycle ESP Workload Manager:
When you are using SYSZONE(YES)
You need to recycle ESP Workload Manager and possibly IPL your system when the time changes:
When running ESP Workload Manager using SYSZONE(NO)