Why NOSCHED is not updated in ESP Event definition?

Products

• ESP Workload Automation

Issue/Introduction

We noticed that the NOSCHED information is not updated:

EVENT ID(cyber.event1)  CLASS(class)  SYSTEM(name)  REPLACE
SCHEDULE AT 07.30 ON 1ST SATURDAY OF 2ND AND 3RD COMPLETE WEEK -
OF MONTH STARTING SAT 16TH JUL 2022
NOSCHED AT 07.30 ON EACH DAY OF 6TH MONTH OF YEAR -
        STARTING FRI 10TH JUN 2022
ENDDEF

Environment

Release : 12.0

Component : ESP WORKLOAD AUTOMATION

Resolution

Every event in ESP is scanned only when it is scheduled. At that time all statements are read and adjusted. Statement NOSCHED is adjusted only at the time when the event is read,  usually when it is scheduled.

Here's the explanation why the event is not scanned at NOSCHED time: when NOSCHED would be every 1 minute and the SCHEDULE would be every 24 hours. The event would be scanned every minute to compare with the SCHEDULE time at 24 hours. This would cause unnecessary overhead.