Jobs "Waiting for initiator"
search cancel

Jobs "Waiting for initiator"

book

Article ID: 226650

calendar_today

Updated On:

Products

CA Workload Automation AE - System Agent (AutoSys)

Issue/Introduction

Jobs stuck with <Waiting for initiator> message as below.

Job Name                                                         Last Start           Last End             ST/Ex Run/Ntry Pri/Xit
________________________________________________________________ ____________________ ____________________ _____ ________ _______
Murali_100                                                       09/22/2021 05:30:09  -----                RU    139529/1

  Status/[Event]  Time                 Ntry ES  ProcessTime           Machine
  --------------  --------------------- --  --  --------------------- ----------------------------------------
  STARTING        09/22/2021 05:30:05    1  PD  09/22/2021 05:30:07   xxxxxxxxxxxxxxx.xxx.xxxxxxxx.xxx
  RUNNING         09/22/2021 05:30:09    1  PD  09/22/2021 05:30:10   xxxxxxxxxxxxxxx.xxx.xxxxxxxx.xxx
    <Executing at WA_AGENT>
  [CHK_TERM_RUNTIME]  09/22/2021 05:34:10    1  PD  09/22/2021 05:34:10
  [STATE_CHANGE]  09/22/2021 05:34:10    1  PD  09/22/2021 05:34:11   xxxxxxxxxxxxxxx.xxx.xxxxxxxx.xxx
    <Waiting for initiator>

Environment

Release : All Supported Agent version

Component : CA Workload Automation System Agent

Cause

When too many KILLJOBS are issued at once this issue may occur.

Resolution

You may have to increase the control initiators by default there are only 10 slots. You need to add something like initiators.class_2=CONTROLCLASS,100 there should already be a _1 in agentparam.txt file and bounce the Agent services.

 

Additional Information

For more info you may refer to below link.

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-system-agent/12-0/reference/ca-wa-agent-for-unix-linux-windows-or-iseries-agent-parameters.html#:~:text=initiators.class_,number_of_initiators