Got "ESP601E NO MORE XX DATES DEFINED"
search cancel

Got "ESP601E NO MORE XX DATES DEFINED"

book

Article ID: 123147

calendar_today

Updated On:

Products

ESP Workload Automation

Issue/Introduction

The following event was suspended instead of triggering:
15.30.00 FRI 14DEC18 ESP6108I EVENTEX: CYBER.EVENT1 scheduled                                                   
15.30.00 FRI 14DEC18 ESP6106I EVENTEX: Next execution of Event CYBER.EVENT1 not scheduled: unsuccessful CYCLING –

Event -
/***************************************************************/            
/* DEFINED BY xxxx     AT 10.44 ON THU 21JAN2016 */            
/*            LAST RUN AT 15.30 ON SAT 30DEC2017     */            
/**************************************************************/            
EVENT ID(CYBER.EVENT1)  SYSTEM(-)  REPLACE
SCHEDULE AT 15.30 ON 1ST TB OF 12TH MONTH OF YEAR -            
         STARTING FRI 14TH DEC 2018                                              
INVOKE 'ESP.PROC(CHECK)'                       
ENDDEF        

Special days -
TB - 
TB                00.00 FRI 14 DEC 2018                    SYSTEM      730
TB                00.00 SUN  1 JAN 2040                    SYSTEM      730

And error below shows in ESP STC JESMSGLG:
ESPM601E NO MORE TB DATES DEFINED 
ESPM532W EVENT <event name> SUSPENDED 
 

Environment

Workload Automation ESP Edition

Cause

There should be at least an extra matching date for the special day defined.

Resolution

It's working as designed.

When the ESP event manager tried to update the value on STARTING parm, it couldn't find an available date, so it issued the errors and suspended the event.

The solution is to define matching special days, like Dec 18 2019.