EASTER_SUNDAY Static Calendar Validity Key

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

EASTER_SUNDAY Static Calendar Validity Key

Environment

Release: AOATAM99000-9.0-Automic-One Automation Tools-Application Manager
Component:

Resolution

Detailed Description and Symptoms

Because time of Easter depends on the first full moon of spring, there is a static calendar validity key, Easter Sunday. All Easter validity keys rely on this static calendar entry.

With the latest updates you receive the latest version of holiday calendars and will be safe with the next year.

In v6.00A, EASTER_SUNDAY ends in 2011 already and needs to be modified manually.

Investigation

Open CALE.HOLIDAYS* CALE objects and check if validity period ?(of EASTER_SUNDAY) is next year or later.

Solution

Only if you have version 6.00A:

# load the 600A_final_holiday_cale?.xml into client 0 (will be available soon, note set on 2011/11/24).
It contains all available countries and ends 2013.

# OR modify EASTER_SUNDAY manually:
Open UC_HOLIDAYS.[country code] CALE object in client 0 (and if used in other clients there too):
1) right click on EASTER_SUNDAY validity key and "modify validity period manually" and set 2 or 3 years to future.
2) save calendar and reopen it. Check all other EASTER* days if recalculated.?