nop
Using this keyword, you can specify that a job must be included in the plan, but not be
launched when the plan starts running. The job is placed in SUPPR
status. If the job contains standard dependencies, they are released and the successors
are launched. If the dependency is of conditional type, the condition has to be
satisfied before the successors can run.
Syntax
job-statement
[...]
[nop]
[...]
Example
In the following example, the JS_1 job stream contains three job
definitions:
- JOB_DEFINITION_0, which is flagged as NOP and therefore it will be placed in the
SUPPR
status when the plan starts running. - JOB_DEFINITION_1, which runs as the plan starts running.
- JOB_DEFINITION_2, which contains a dependency from JOB_DEFINITION_0 and therefore it will run when that dependency is released.
SCHEDULE WS_AGT_0#JS_1
:
WS_AGT_0#JOB_DEFINITION_0
NOP
WS_AGT_0#JOB_DEFINITION_1
WS_AGT_0#JOB_DEFINITION_2
FOLLOWS JOB_DEFINITION_0
END