3 of 3 people found this helpful
A job can wait for other constraints, beside predecessor jobs, like:
- It has a quantitative or control resource constraint (e.g. server availability);
- It has a time constraint (e.g. do not run until 23:00);
- A workload policy has been activated.
In the job's properties, look in the Scheduling and Prerequisite tabs to see if there are any additional constraints.
There would also be a system-wide stoppage if the ctm_pause or ctmsuspend utilities were executed. (This is less likely to be your cause since those stoppages affect all jobs, and should be known or publicized via your change control process or system availability/service level notice.)
The job's log tab in the monitoring domain could give you a better picture.
1 of 1 people found this helpful
Thank you for your response. It was related to server availability.