After adding new entries for special days and holidays with RESCHEDULE option, there is one ESP event ESP.AAAAA which was supposed get rescheduled, but it did not. Whereas other Events were rescheduled as expected. We also tried with CALSCH command, it didn't help.
Component: ESP Workload Automation
Release: ALL
If the event was updated recently, shown on "Defined by" in Event definition, then ESP won't attempt to adjust the STARTING date & time to the date prior to one actually coded for the STARTING parameter, when CALSCH command is issued or the new Special day is defined with RESCHEDULE option.
Here is a sample Event, update to the event was done recently after last run:
/******************************************************************/
/* DEFINED BY USERX AT 16.50 ON WED 4MAR2026 */
/* LAST RUN AT 20.00 ON TUE 3MAR2026 */
/*******************************************************************/
EVENT ID(USERX.WLM422) SYSTEM(-) REPLACE
SCHEDULE 20.00 WORKDAY DAILY LESS 1 DAY STARTING WED 4TH MAR 2026
NOSCHED AT 20.00 ON SPEC1 STARTING WED 24TH JUN 2026
NOSCHED AT 20.00 ON SPEC2 STARTING SUN 10TH FEB 2041
INVOKE 'ESP.PSS.PROC(procyy)'
ENDDEF
So if new entry for special days SPEC1 and/or SPEC2 added, ESP won't adjust the STARTING dates even CALSCH command is issued or the new Special day is defined with RESCHEDULE option.
The calendar entries should be added sooner, before the last valid entry date is reached. Note: the entry with the date that's far in the future, like 10TH FEB 2041, shouldn't show up before the calendar entries are added.