how to adjust chase settings to allow for more time in STARTING status

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - System Agent (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent
• Autosys Workload Automation

Issue/Introduction

We are using the initiator class to throttle the number of the jobs on each server.

In doing so we found that jobs in the queue for more than 2 minutes are throwing chase error.

Is there an additional setting required to prevent chase sending an alert for a valid prolonged stating status?

 

Environment

Release : 11.3.6

Component : CA Workload Automation AE (AutoSys)

Resolution

See CHASE_STARTING_WAIT_INTERVAL

Specifies the minimum time (in minutes) that the chase utility allows jobs to remain in the STARTING state before raising the CHASE_ALARM alarm. During periods of network load or high workload activity, it might take more than the default two minutes for the agent to notify the scheduler that a job is executing. Setting this environment variable helps reduce the number of alarms that the chase utility generates during this time. Set this environment variable on the computer where you are running the chase command.

 

Default:

 2

Limits:

 1 to 35791394

Here is the link to the documentation for the setting:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-ae-and-workload-control-center/11-3-6-SP8/administrating/ae-administration/configuring-ca-workload-automation-ae/environment-variables-client-utilities-or-sdk.html