BATCH_SERVER_SHUTDOWN is a special day that we define in the calendar as needed. When a BATCH_SERVER_SHUTDOWN date is encountered, however, the event ignores it and uses the normal schedule. Since this did work in test, we did some research and found that (1) the next trigger date/time is embedded within the event and (2) the event is not updated when the new BATCH_SERVER_SHUTDOWN special day is defined. Is this the way CA Workload should behave, and if so is there another way to implement this type of schedule? Please let us know.
The special day was added after the event had already been scheduled. In doing so, the special day is not re-read in to account for the new date conditions.
Release: Component: DSRIES
If you did not define the dates for BATCH_SERVER_SHUTDOWN before the time the last event was triggered, it will not run as you expect in the future. If you know the dates which should be defined in the BATCH_SERVER_SHUTDOWN special day, then you should have them added ahead of time. The calendar is not read after the calendar has been set unless you re-upload the event to DE.