UC_CLIENT_SETTINGS - AUTO_FORECAST_DAYS - Restart needed?

book

Article ID: 198785

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine

Issue/Introduction

Changed in variable UC_CLIENTS_SETTINGS the parameter AUTO_FORECAST_DAYS to 7 . 

When recalculating Autoforecast still 2 days are calculated.

UC_CLIENT_SETTINGS - AUTO_FORECAST_DAYS - Restart needed?


Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

The autoforecast functionality takes a date/time frame as input (for example, 2016-09-29 03:00:00 to 2016-06-30 06:00:00) and returns all tasks with a logical start date within that period. It also informs you about the expected runtime and end time of each task. To do so, autoforecast simulates the execution by running the Scheduled jobs as it would occur in reality.

It does not use the real job scheduling engine, though. The simulation considers neither previously simulated runs nor the history of Job executions. Instead, it uses estimated runtimes calculated from the latest 25 runs of the selected tasks.

Only users who have been assigned the Access to Autoforecast privilege can execute this function.

Also, the autoforecast cache must have been calculated for the desired timeframe.

Restrictions

The result of autoforecast queries depends on the calculation period and on the interval in which tasks are executed. For Schedules, this is the period length; for Events, the time interval. The following limitations apply:

With the exception of Events, only tasks planned within Schedules are considered
Tasks that are activated through other tasks (ACTIVATE_UC_OBJECT) are not included
It is not possible to identify dependencies of tasks on other tasks
Modifications of attributes during runtime are not taken into account

Note: Event forecasts are calculated only once a day, even if the event runs more than once a day.