Defining a job as non-operational (NOP)

Defining a job as non-operational (NOP)

You can define a job as non-operational so that when the plan runs, the job is put in Cancel Pending status and is not run. The successors of this job are however run. You can define a job as non-operational by either checking the NOP box in the job definition window in the Dynamic Workload Console, or by adding the NOP option in the job statement in composer. You can make a NOPed job operational at plan run time from either conman or the Dynamic Workload Console. This sets the job to the Ready status for that particular job stream instance only (to make the job permanently runnable, you must remove the NOP flag from its definition).

For more information, see nop.