Removing an operation from the current plan and restoring it

To remove (NOP) an operation that is already in the current plan, enter the NP command beside the row in the ready list. NP can be issued for any operation on the ready list that has status A, R, *, W, or (for computer workstations with automatic reporting only) C.

The scheduler processes status changes for NOP operations until they reach a status of A, R, or * (ready). The scheduler ignores time dependency, use of special resources, and other constraints. When a NOP operation reaches the ready status A, R, or *, IBM® Z Workload Scheduler immediately sets the operation to status C; the operation is not submitted, and successor operations are eligible to start. NOP operations are identified by the N extended status code.

Attention: Make sure that successor operations in a dependency chain are removed (NOP) before their predecessor operation. This prevents the successor operations from starting when you remove (NOP) their predecessor.

If you want to restore the operation, use the UN command. The UN command does not affect the status of the operation. It merely removes its NOP characteristics. The operation can be treated as any normal operation on the ready list.

The NP command gives to the operation the property NOP. This property can be removed from the operation by the UN command only. Neither the NP command nor the UN command changes the status of an operation directly. A NOP operation is automatically changed to completed status when it reaches ready status, regardless of whether other constraints are met.

Note: The EXECUTE command starts an operation even if it is NOP. See Running an operation immediately with EXECUTE.

Use the MCP panel for an operation that is not on the ready list. See Modifying operations for more details.

The NP and UN commands can be issued also on operations defined on fault-tolerant workstations, but the result of the commands is different depending on whether the operation has the centralized script option or not. When the centralized script option is used, the NP and UN commands have the same effect they have on operations defined on computer automatic workstations. When the centralized option is not used, the commands result in setting the CANCEL PENDING option in the Symphony file for the related job. Then the job is canceled locally when the usual conditions are satisfied and consequently the related operation is completed in the current plan. It is also possible for the operations that are handled in the distributed environment to respond differently than usual on time dependencies: if the keyword NOPTIMEDEPENDENCY(YES) is specified in the TOPOLOGY options when the Symphony is created through the daily planning jobs, the jobs are canceled only after the time dependencies are locally satisfied. In order to successfully execute the NP and UN commands on an operation that is defined on a fault-tolerant workstation and that does not use the centralized script option, the workstation should be linked.

Note: You can set the NOP option for an operation directly in the Application Description database, or you can associate the NOP option with a specific run cycle. When the operation is added to the current plan, either dynamically or not dynamically, the NOP option takes the following value in the following order:
  1. The value set in the associated run cycle, if applicable.
  2. The value set in the Application Description database.
  3. The value overwritten by the user when the operation is added to the CP (from the ISPF panel).