ESP Workload Automation

 View Only

 ESP601E NO MORE (calendar name) DATES DEFINED

Thaina Muntoreanu's profile image
Thaina Muntoreanu posted Dec 05, 2025 11:50 AM

Hello,

We're having an issue now where we're getting ESP601E errors and the event is not getting triggered. (It worked properly the entire year),

The error is:

ERROR OCCURRED PROCESSING EVENT REVCRIS.CRIST_STATINFO CN(DL04)     
NO MORE BILL_MONTH DATES DEFINED CN(DL04)                           
ABOVE ERROR OCCURRED ON FOLLOWING STATEMENT IN JOB PAGEBP1T CN(DL04)
RUN 1ST BILL_DAY OF BILL_MONTH CN(DL04)                             

On the calendar we have the following entries (from dec 2025 on):
For BILL_DAY



For BILL_MONTH




If we do have a BILL_MONTH date for future (2026), why are we getting ESP calendar errors preventing the events to trigger ?



dharwood's profile image
dharwood

If you try to use a calendar date in the future, and there are no entries, you will get Event Errors. The workaround is to set a calendar entry way in the future, so you never 'run out' of dates. We use Jan 01 2042. 

Lucy Zhang's profile image
Broadcom Employee Lucy Zhang

Hi Thaina,

As the explanation from our doc link below:
https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-workload-automation-esp-edition/12-0/using/use-schedule-criteria/special-periods.html
..... include one extra period at the end of your definitions to give ESP a final reference point. For example, define the first day of at least two consecutive fiscal years, so that ESP can calculate the start and finish of the first year. 

So you would need one extra special period. And the response from dharwood is a very good method to avoid it.

Now we are approaching the end of the year, hope everyone can find the time to define the holidays and special days proactively for next year.

Happy holidays!

Lucy