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.

Control number of job run by initiator.class parameter in WA Agent

book

Article ID: 239090

calendar_today

Updated On:

Products

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

Issue/Introduction

How can users control number of job runs on WA agent to prevent errors like "initiator busy" or other OS issues?

Cause

By default WA Agent can run 1000 jobs concurrently.  If Agent is expected run more than default number of jobs, then increase Default initiator class:

initiators.class_1=Default,1000

However, increasing the default to a very number can result in OS issues such as number of open files (limits vary by OS), performance, memory etc.

Environment

Release : 12.x

Component :

Resolution

The WA agent has "initiators.class_n" parameter to limit or control job runs.  When number of job runs exceed, the agent will wait till an initiator is available and then executes the job.  The agent allows limiting job by types.  

Example to  limit command/system jobs (Windows command, Unix) in agentparm.txt:

initiators.class_1=Default,1000
initiators.class_2=CMD1,500
#The initiators.class_2 is class that can be used in afmjobclassmap
#Any name can be given, but the name must match in afmjobclassmap

initiators.afmjobclassmap_1=RUN,.,CMD1
#The above will allow only 500 concurrent command job runs.
#The afmjobclassmap will look at job type when it arrives and then check if initiators are available

Note: The 'initiators.class_<n>'  needs to be incremented sequentially independent of  'initiators.class'. 

 

Additional Information

For more details, see this doc link for WA Agent.