WA Agent: Is there a way to force a job out of the "waiting for initiator" state?
search cancel

WA Agent: Is there a way to force a job out of the "waiting for initiator" state?

book

Article ID: 113571

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) Workload Automation Agent CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation DE - Business Agents (dSeries) CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

Can a job in STARTING status but is waiting for an available initiator on the agent side be force completed?

Environment

Release:
Component: SYSAGT

Cause

The default initiators is 1000.  The WA Agent can concurrently run 1000 jobs. The "waiting for initiators" message indicates that agent has used maximum number of initiators for jobs.  Each job will use an initiator and it is returned or freed up when the job completes.  Long running jobs and file monitoring will use an initiator for a long time.  This will sometimes result in WA Agent in out of initiators.

Resolution

Users may temporarily increase the number of available initiators for the job class on the agent side. Edit the agentparm.txt file on the agent machine and increase the initiator value:

initiator.class_1=Default,1000

Restart the WA Agent once the parameter has been increased.  Once the agent is restarted, the jobs will start executing.

Note: It is recommended to increase the default initiator class by 100.

Additional Information

Here is the documentation link with more details about initiators.