On CA Automic Workload Automation Agents the Agent resource (Max. Resources Jobs) is not released
Article ID: 84323
CA Automic Workload Automation - Automation EngineAUTOMIC WORKLOAD AUTOMATION
The Agent resources that a CA Automic Workload Agent provides for Jobs (Max. Resources Jobs) are not freed under certain conditions.
The following setup must be given, according to tests, so that the maximum number of resources (Max. Resources Jobs) is not set back:
The Job has a HostGroup entered
The Hostgroup parameters must be either set to Any, Next Listed or Load Dependent
"Generate at runtime" is set on the Job
The Job uses a script with the statement "ON_ERROR ABEND"
The Job uses the script function "ACTIVATE_UC_OBJECT" for a starting any object type (e.g.: JOBS, SCRI,…)
The activated task has "Generate at runtime" not set
The activated Job fails
The job uses the script function "EXIT" when the follow-up JOBS has a certain status (it does not matter if the follow-up JOBS ends ok or fails)
When all these options are met the Agent resources are not freed and set eventually to 0.
Therefore any job activated after the defined Agent resources are used the Jobs will stay in the activity window in a status of "Waiting for the host of an AgentGroup". In this case only a restart of the Agent helps to free the resources.
Agent resources are not released after the end of a job. This happens if agent groups are used in combination with the script function ACTIVATE_UC_OBJECT.
OS Version: N/A
Update to a fix version listed below or a newer version if available.
Component(s): Automation Engine
Fix Version(s): Automation Engine 12.0.6 - released Automation Engine 12.1.2 - released Automation Engine 12.2.0 - released
Workaround : -) Use Agent instead of HostGroup -) Use “Generate at Activation” instead of "Generate at runtime" in the Job -) Don`t use the script function "EXIT" -) When a HostGroup is used set the parameter either to All Active or First -) Monitor the used "Job res. max" and restart the Agent if necessary.