Batch Job - Options

The Batch Job Options panel lets you define how a Batch Job functions.

Using the Batch Job Options panel, you can

  • Identify a Batch Job
  • Specify whether the Batch Job should stop if it encounters errors in one of the individual jobs included in the batch
  • Specify whether you want the individual jobs in the batch to execute sequentially, in parallel, or by server
  • Specify whether you want to enable a rolling execution of the Batch Job divided across multiple job runs, so that each time the Batch Job runs, it executes against a certain (user-defined) maximum number of servers

The Batch Job Options panel also lets you specify target servers. Each of the individual jobs included in the batch can run on the target servers specified in the definition of that job, or all of the individual jobs can run on the same set of target servers that you specify for the entire Batch Job. When first defining and saving a Batch Job, you do not have to specify target servers. You can specify target servers at a later time.

If you define a Batch Job that includes other nested Batch Jobs, the settings you define for the current Batch Job only apply to the jobs it contains. A Batch Job's settings do not apply to any jobs contained within nested Batch Jobs unless you specify target servers on this panel. In that case, the specified target servers apply to all jobs nested within the Batch Job.

Field definitions

Name

Identifying name.

Description

Optional descriptive text.

Save in

Folder in which to store the object.

Continue executing batch when individual jobs return non-zero exit code

The Batch Job should continue despite individual jobs that might return an exit code other than zero.
This option is particularly useful when you are using a Network Shell Script Job to reboot a Windows server. That process typically generates errors until the server successfully reboots.

Execute jobs sequentially

Each individual job in the Batch Job runs against all specified targets before moving on to the next individual job listed in the jobs list.

Execute jobs in parallel

All the individual jobs in the Batch Job run against all targets simultaneously.

Execute by server

All the individual jobs in the Batch Job run against each target sequentially but the Batch Job processes all targets in parallel. This option is identical to running multiple Batch Jobs simultaneously, with each Batch Job configured to have only one target and to execute individual jobs sequentially.

Enable Rolling Execution

The Batch Job runs against a limited number of servers — a subset consisting of no more than the number that you specify here — before moving on to the next subset of servers.

Set execution override

Select if this job should always execute as if your current role and user are scheduling the job. After you click this option, the job definition shows the role:user combination under which the job executes.

Clear execution override

Remove an existing execution override.

Servers/Server Groups

Select one of the following:

  • If all the jobs included in the batch should execute on the servers specified in the definition of each job, select Use servers from individual jobs. This option is not available if you chose the Execute by server option, described above. When you select this option, you do not have to specify any servers where the job executes.
  • If all the jobs should execute on the servers that you specify, select Use the following servers for all jobs. If you select this option, click Add Servers g_V95_AddIcon.gif. The Select Servers/Groups window opens. Use it to specify the servers or server groups where the Batch Job, including all jobs that are part of any nested Batch Jobs, should execute.

Where to go from here

Batch-Job-Default-Notifications

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*