Updates to the ON_NOEXEC Feature
In the current release ( 11.3.6 SP2) , the following changes are made for the ON_NOEXEC feature:
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.
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.