#daylightsavingtime#time #espmainframe #event
This is a complex topic. Below are a few notes and references.
Below is a link to the doc on setting up timezones. I don't think IST moves with daylight savings time. Use SYSZONE(NO) so it does not spring forward and fall back along with to the system time.
TIMEZONE: Define a time zone - CA Workload Automation ESP Edition - 11.4 - CA Technologies Documentation
After the IST time zone is set up it can be used in statement.
If it is used at the application level, when the schedule builds it will change the time to central time.
If it is used at the event level, inside the event will show IST time. Outside the event will show Central time.
DELAYSUB 08.00 IST
SCHEDULE 08.00 IST DAILY
Below is a link to the doc on using schedule criteria.
Use Schedule Criteria - CA Workload Automation ESP Edition - 11.4 - CA Technologies Documentation
Can we define time zone dynamically by giving the command 'TIMEZONE 22 IST 5.30E SYSZONE(NO)' in Page Mode?
Do we need to include in the Initialization Parameter and recycle ESP ?
Unfortunately TIMEZONE is a statement and not a command. It can only be used in the init parms. It will require a bounce of ESP to take effect.
If you would like respond with the output of the LTZONE command so I can see what is set up currently.
This is the output
Thanks for the output. It looks good. The TIMEZONE statement that you mentioned previously for IST will work correctly.
I see the statement that "No time zone with DST defined". I think this message is because there is no SYSZONE(YES) defined for any of the timezones. This would require ESP to be bounced to pick up the timechange. If SYSZONE is specified like the one below ESP does not need to be bounced at timechange. You may have it this way on purpose.
TIMEZONE 0 LOCAL 0 SYSZONE(YES)
Below is a link to the TIMEZONE doc.
Let me know if you have any questions.
powdo03 #daylightsavingtime #espmainframe
Apologies for the delay!. Stuck up with a project work.
I have created a below test event
EVENT ID(DP.DALD_PUSHTEST) SYSTEM(DALD) REPLACE
SCHEDULE 02.00 IST MONTHLY STARTING TUE 21ST MAY 2019
EVENT NEXT DUE AT LAST RUN SYS HC SC
DP.DALD_PUSHTEST ,15.30.00 2019/05/20 ,2019/04/20 DALD , 0 , ,0 ,
Like you mentioned earlier, Since I have used at the event level, inside the event it shows IST time. Outside the event showing Central time.
As you mentioned , used SYSZONE(NO) so it does not spring forward and fall back along with to the system time.
Now the event is running at 2 am IST and 3.30 pm CT , Daylight saving ends on Nov 3rd .After that , event should run at 2 am IST and 2.30 pm CT. Basically IST should not change but CT should change. Above setup will work in the desired way right?
Is there any way to test it ? because when I check the next run after Nov 3rd it still shows 3.30 pm CT as below
NEXT 99 DP.DALD_PUSHTEST
SCHED AT 15.30.00 ON MONDAY MAY 20TH, 2019
SCHED AT 15.30.00 ON THURSDAY JUNE 20TH, 2019
SCHED AT 15.30.00 ON SATURDAY JULY 20TH, 2019
SCHED AT 15.30.00 ON TUESDAY AUGUST 20TH, 2019
SCHED AT 15.30.00 ON FRIDAY SEPTEMBER 20TH, 2019
SCHED AT 15.30.00 ON SUNDAY OCTOBER 20TH, 2019
SCHED AT 15.30.00 ON WEDNESDAY NOVEMBER 20TH, 2019
SCHED AT 15.30.00 ON FRIDAY DECEMBER 20TH, 2019
SCHED AT 15.30.00 ON MONDAY JANUARY 20TH, 2020
SCHED AT 15.30.00 ON THURSDAY FEBRUARY 20TH, 2020