HCL Workload Automation, Version 9.4

Jobs in READY status do not start

When monitoring a job, it appears to be ready to run, but it does not start. All of the dependencies have been satisfied and the start time has passed, but something is holding it back.

Cause and solution:

There are a few reasons why a job cannot start. The most common reasons are the following:
  • The workstation limit is set to zero.
  • The workstation is stopped.
  • The workstation on which the job should run is not linked.
  • The number of jobs running on the workstation is greater than the limit set on the workstation.
The Dynamic Workload Console provides the capability to detect the problem and provide the solution for these most common reasons.
From the Dynamic Workload Console, when monitoring the job status, you can request problem determination for a job in READY status that does not start. To determine why a job does not start:
  1. From Monitor Workload, run a query to monitor jobs.
  2. Select one or more jobs in READY status and then click More Actions > Why a job does not start.
  3. A window displays an explanation and a solution for each selected job in READY status.