Solving Year out of Calendar error by expanding calendar
search cancel

Solving Year out of Calendar error by expanding calendar

book

Article ID: 89490

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

Subject

Solving the "Year out of Calendar" error by expanding the calendar

Prerequisites

DUAS V500 or later.

Application Validation Tests

Please check calendars from the windows desktop or command line, to see if your calendar ends in 2010.
To check the default calendar from the command line, you could try:
Windows:
%UXEXE%\uxshw cal exp mu=\" 00\"
Unix:
$UXEXE/uxshw cal exp mu=\" 00\"
Or you could specify a MU name for a specific calendar.

Environment

Release: 5.x and  6.x
Component: Dollar Universe

Cause

Explanation

If you see the following error in the universe.log, you may have a job that needs to run at a date out of the calendar coverage. For example, the calendar ends in 2010, and the job should run in 2011.
<< 2009-12-30 14:13:33 0031711/uxcal           /GACALC32            /134450698 - %UNI_-E-U_EGACALC3209,  Year out of Calen
It is easy to find out the coverages of all calendars from the Windows desktop. Or you could run the command in the "Application validation tests" section to find out.

Resolution

Implementation Procedure

If a calendar ends in 2010, we would recommend updating it to add at least 2 more years. It can be done with the following commands.
The following commands use the default calendar as an example, you could specify a MU name for a specific calendar.
1. Since the calendar is limited to cover a maximum of 25 years, you may need to remove 2 years before you can add more years to a calendar.
Windows:
%UXEXE%\uxdlt  cal exp  mu=\" 00\"   since=2000 before=2001
Unix:
$UXEXE/uxdlt  cal exp  mu=\" 00\"   since=2000 before=2001
2. Add 2 more years to the calendar
Windows:
%UXEXE%\uxadd  cal exp  mu=\" 00\"   since=2011 before=2012
Unix:
$UXEXE/uxadd  cal exp  mu=\" 00\"   since=2011 before=2012

Additional Information

Implementation Check

To check if the calendar has been expanded properly, you could run a simulation on a scheduled task using, the concerned calendar, from the Windows desktop on a newly expanded date. In our example, it could be Jan 1, 2012.
Or you could use the following command line:
Windows:
%UXEXE%\uxlst prv upr=upr_name ses=ses_name mu=MU_NAME dsince=01/01/2012 dbefore=01/20/2012 tsince=0000 tbefore=0000

Unix:
$UXEXE/uxlst prv upr=upr_name ses=ses_name mu=MU_NAME dsince=01/01/2012 dbefore=01/20/2012 tsince=0000 tbefore=0000

In Case The Procedure Is Unsuccessful

If the above procedure can not expand your calendar properly, please open a case with technical support and mention this article.