ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Detect Task and MU name of Tasks outside calendar

book

Article ID: 132549

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

In Dollar Universe 5 the error message "year is outside the bounds of calendar " used to appear in universe.log when the calendar expires, but it did not inform which Task and MU are affected.
We would like to have the same error in Dollar Universe 6 along with the affected Tasks and Management Unit.

Cause

Error was not written in universe.log by default as on version 5.

Environment

Dollar Universe 6

Resolution

Update to a fix version listed below or a newer version if available where the universe.log will contain the impacted Task and MU.

Fix version:
Component(s): Application ServerĀ 
Dollar Universe 6.10.01 - Available 30th May 2019

Additional Information

The example of ERROR message that will appear in universe.log is:

 [TSK(SESSION_NAME)(000)(UPROC_NAME)(000)][MU_NAME] - year is outside the bounds of calendar [2016-2036]: 2014. Force it to calendar period

 

In order to avoid these errors, you have two options:

  1.  Update the Task indicated in the message and update its Start Date or the Application Date of the Rule/s attached with a recent date (ie. 01/01/2021)
  2. Increase the Calendar range (ie 2014-2036) so that it includes the year 2014