Running an operation immediately with EXECUTE

The EXECUTE command overrides normal scheduling rules except dependencies. You can use the EXECUTE command when:
  • An operation is waiting for a resource that is not actually required.
  • You want only one job to be submitted through IBM® Z Workload Scheduler.
  • Automatic job submission is not active for all operations.
  • A planned shutdown of a workstation is in progress and an operation is not submitted by IBM® Z Workload Scheduler because the job cannot finish in time.
The EXECUTE command, EX, can be issued for an operation on a computer workstation with automatic reporting if the status of the operation is A, *, or R. The EXECUTE command causes IBM® Z Workload Scheduler to start the operation without regard to normal scheduling criteria. An operation that you EXECUTE will be started even when:
  • Job submission is not active.
  • Job options for the operation do not specify automatic submit.
  • Time dependency for the operation is not satisfied.
  • Required resources are not available.
  • The operation has H (manual hold) extended status. It remains in held status.
  • The operation has N (NOP) extended status. It remains in NOP status.

To successfully execute the EX command 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. Moreover, for these operations the EXECUTE command works only if the job is in a consistent status (that is, not running or canceled) at the time it is received by the appropriate fault-tolerant agent. Otherwise, it is discarded.

Note: If the workstation where the operation is defined is not active and there is no active alternate workstation connected, or the operation is not re-routable, the EXECUTE command is rejected and the operation status is not changed.

You can also request EXECUTE from the MCP panel. For details, see Modifying operations.