Job is in EXEC state but remains in "Waiting for initiator" status despite available initiators.

Products

• ESP dSeries Workload Automation
• ESP dSeries Workload Automation - Business Agents (dSeries)
• ESP dSeries Workload Automation - Scheduler (dSeries)
• ESP dSeries Workload Automation - System Agent (dSeries)

Issue/Introduction

After successful upgrade of the WA Agent (e.g., to version 24.1), jobs are submitted but are stuck in an EXEC state with a status of "Waiting for initiator".

Increasing the initiators.class_N parameter or recycling the agent does not resolve the issue. If the job is canceled, it moves job to  INTVRQ state with a status of "Flushed prior to execution".

Environment

ESP dSeries Workload Automation: 12.4 or above

Cause

The issue is caused by the agent being placed in a quiesce state during the upgrade process.  In some instances, the parameter agent.quiesce.state=true may be written to or remains active in the agentparm.txt file.

Resolution

Remove the "agent.quiesce.state" to set it to false in agentparm.txt file.  Restart the WA Agent.