Page History

...

• Adds 10 temporary ad hoc orders to the specified job chain, see Add-Order.
• The order identification is not specified but is generated by the JobScheduler Master.
• All orders are submitted to the JobScheduler Master in a single transaction at the end of the bulk operation.

...

• Line 1 adds 10 temporary ad hoc orders.
  • Consider use of the switch -Immediate to submit each order individually to the JobScheduler Master and to receive the newly created order identification immediately.
  • The result of the Add-Order cmdlet is assigned to a variable for later use.
• Line 2 pipes the recently created orders to the Remove-Order cmdlet.

Identify temporary orders

...

Suspending temporary orders allows to keep such orders for further investigation. Suspended orders are not carried out by the JobScheduler Master:

...

• In a pipelined operation temporary orders are retrieved and suspended, see Suspend-Order.
• Consider use of additional parameters such as -Directory and -JobChain to further restrict the number of orders.

...

• Line 1 retrieves exclusively temporary ad hoc orders by use of the -NoPermanent switch.
  • Consider use of additional parameters such as -Directory and -JobChain to further restrict the number of orders.
  • The result of the Get-Order cmdlet is assigned to a variable for later use.
• Line 2 displays the number of orders that meet the conditions.
• Line 3 displays the $order variable, i.e. the list of orders.
• Line 4 pipes the list of orders to the Suspend-Order cmdlet,

Remove temporary orders

...

• In a pipelined operation temporary orders are retrieved and removed, see Remove-Order.
• Consider use of additional parameters such as -Directory and -JobChain to further restrict the number of orders.
• Tasks that are currently running for an order are not affected by this operation. Such tasks will continue until completion. Consider use of the Stop-Task cmdlet to kill running tasks.

...