nop/unnop

The model command to set one or more jobs or one or more job streams in the model operational or non-operational. It temporarily disables one or more jobs in one or more job streams without changing their dependencies.

Overview

The command updates one or more jobs in one or more job streams without deleting them or changing their dependencies. If the job contains standard dependencies, they are released and the successors are launched. If the dependency is conditional, the condition must be verified as true before the successors run. After the command runs, the specified job changes to CANCEL PEND status.

If you apply the command at the job stream level by specifying the job stream name in the Orchestration CLI, the operational or non-operational setting applies to all jobs contained within that job stream. Alternatively, you can specify the name of an individual job to apply the setting only to that specific job within the job stream.

For example, if you need to temporarily skip a notification job due to a service outage, you can nop that job in the job stream until the service is restored.

Authorization

You must have NOOPDB or MODIFY access to the job. If you have NOOPDB access, this means you can only set the object as operational or non-operational. If you have MODIFY access, you can modify all the properties of the object. For more information about authorization for Orchestration CLI commands, see Access required to run Orchestration CLI commands.

Syntax and command line options

ocli model [nop|unnop] [jobselect|jobstreamselect] [;noask]

You can enter the command as follows:

jobselect|jobstreamselect: Specify the job or job stream name. The job or job stream must exist in the model; otherwise, an error occurs. You can operate on multiple jobs and job streams by using wildcards.

noask: If specified, the nop/unnop option in the job or job stream is updated without a confirmation prompt.

Examples

Run the following command to temporarily disable the specific job (JOB inside JOB_STREAM on workstation WKS_AGT) in the model without deleting it or modifying its dependencies:

OCLI model nop WKS_AGT#JOB_STREAM.JOB

Run the following command to restore a job previously set as non-operational (JOB inside JOB_STREAM on workstation WKS_AGT) to an operational state:

OCLI model unnop WKS_AGT#JOB_STREAM.JOB

Run the following command to apply the "no operation" action to all jobs across all job streams on all workstations in the model:

ocli model nop /@/@#/@/@.@

Run the following command to apply the "no operation" action to job1:

ocli model nop wks#js.job1

Run the following command to apply the "no operation" action to all jobs in the JS job stream:

ocli model nop wks#js.@

Run the following command to apply the "no operation" action to all jobs defined on a specific workstation:

ocli model nop wks#@

Run the following command to apply the "no operation" action to all jobs in the JSfolder:

ocli model nop wks#/JSfolder/@