Workload management with bulk nop control

Streamline your scheduling environment by setting one or more jobs or entire job streams as operational or non-operational in the database.

Streamline your scheduling environment quickly and easily. You can now use both the Dynamic Workload Console and the Orchestration CLI model commands to smoothly set one or more jobs—or entire job streams—as operational or non-operational in the database.

Whether you need to temporarily skip a notification job due to a sudden service outage or bypass a set of tasks during system maintenance, this feature saves you time and effort. By setting a job to non-operational (nop), you temporarily disable it without having to delete it or alter your complex dependency chains.

With this granular control feature, you can take advantage of:

Flexible bulk operations

Apply the command at the job stream level to automatically update all the jobs contained within that job stream. If you apply the command to multiple job streams, the action is executed on all jobs within all the job streams returned by your query. Alternatively, specify an individual job name to apply the setting precisely to that specific job.

Smooth workflow continuity

After the command runs, the specified jobs change to the CANCEL PEND status. If a job contains standard dependencies, they are automatically released so that your successor jobs can launch without delay. For added safety, if a dependency is conditional, the condition must still be verified as true before any successors can run.

Targeted security control

Enforce the principle of least privilege with ease. A specific security permission, NOOPDB, enables administrators to grant users the exact access they need to set objects as operational or non-operational. This ensures your environment remains secure, as users do not need broader MODIFY access (which allows changing all object properties) just to perform this targeted action.