DE jobs are stuck in READY
Article ID: 74289
CA Workload Automation DE - System Agent (dSeries)
All jobs on one of the Linux servers are going to Ready state
The jobs stuck in READY means that the agent, to where these jobs were submitted, cannot reply back to the DE server; the common reasons are:
- Blocked communication (networking media) from the agent to DE
- Mismatched the agent's and the DE's encryption keys
- In case of the unix-like agent, the number of sub-directories in the agent's 'spool' has reached the kernel limit (by default, ~ 30K).
- Not often, it could be caused by a clogged transmitter queue - if the agent continues to send messages to a scheduler which is not available anymore.