Updates to the ON_NOEXEC Feature
In the current release ( 11.3.6 SP2) , the following changes are made for the ON_NOEXEC feature:
- JOB_ON_NOEXEC event The scheduler processes the JOB_ON_NOEXEC event similar to that of the CHANGE_STATUS event to INACTIVE.
For example, if you send the JOB_ON_NOEXEC event to a job in a box, the effect is the same as sending the CHANGE_STATUS event to INACTIVE for a job in a box. The job enters the ON_NOEXEC status and the scheduler evaluates the overall box status as if the job entered the INACTIVE status.
To take the job off the ON_NOEXEC status, you must send the JOB_OFF_NOEXEC event. Sending manual CHANGE_STATUS event does not change the status of the job. To complete the NOEXEC job immediately so that the scheduler evaluates the job as if the job entered the SUCCESS status, send the FORCE_STARTJOB event.
- JOB_OFF_NOEXEC event When the scheduler processes the JOB_OFF_NOEXEC event for a job, it places the job in the INACTIVE status. If the job is in a box, the scheduler evaluates the overall box status as the job is entering the INACTIVE status. If you send the JOB_OFF_NOEXEC event to a box, all jobs in the box (including all jobs contained in lower level boxes within the box) are reset to the INACTIVE status.
- Evaluation of downstream dependent jobs When you send the JOB_ON_NOEXEC event to a job, the effect is the same as if the job enters the INACTIVE status. The scheduler does not immediately schedule jobs that have a dependency on the NOEXEC job nor does it evaluate their success conditions to success.
When the job's starting conditions are met and the scheduler sends the BYPASS event, the effect is the same as if the job enters the SUCCESS status with an exit code of 0. The scheduler schedules jobs that have a dependency on the NOEXEC job and evaluates their success conditions to success.