The display of Batch Job results differs, depending on whether you enabled a rolling execution for the Batch Job and depending on the mode of execution that you chose for the individual jobs contained within the Batch Job (sequentially, in parallel, or by server).
The following table summarizes the effects of these settings (as defined on the Batch Job Options panel) on the display of Batch Job results.
Mode of execution of child jobs | Description of display without rolling execution | Description of display with rolling execution |
|---|
| One set of child job runs directly under the Batch Job run.
Within the set of child jobs, times of execution are unique and progressively later.
When you click a child job, you can see that the job executed against all servers (in the table on the right). | Several nested Batch Job runs under the main Batch Job run. Each nested Batch Job run connects to a set of child job runs.
Times of execution of child jobs are unique and progressively later, both within and between child job sets.
When you click a child job, you can see that the job executed against a subset of servers (consisting of no more than the number of servers that you specified on the Batch Job Options panel). |
| One set of child job runs directly under the Batch Job run.
Within the set of child jobs, times of execution are all the same.
When you click a child job, you can see that the job executed against all servers (in the table on the right). | Several nested Batch Job runs under the main Batch Job run. Each nested Batch Job run connects to a set of child job runs.
Times of execution of child jobs are all the same within each set, but progressively later between sets.
When you click a child job, you can see that the job executed against a subset of servers (consisting of no more than the number of servers that you specified on the Batch Job Options panel). |
| Multiple Batch Job runs nested under the main Batch Job run, one for each target server. Each nested Batch Job run connects to a set of child job runs.
The time of execution of the first child job is the same in all sets. Subsequent jobs execute one after the other within each set, but times of execution may differ between sets. See Example of Batch Job running by server without rolling execution.
When you click a child job, you can see that the job executed against a single server. | Multiple Batch Job runs nested under the main Batch Job run, one for each target server. Each nested Batch Job run connects to a set of child job runs.
Times of execution reveal that the nested Batch Jobs are grouped together based on the number of maximum servers specified on the Batch Job Options panel. See Example of Batch Job running by server with rolling execution.
When you click a child job, you can see that the job executed against a single server. |
[The following figures present examples of results for a Batch Job running by server with and without rolling execution enabled. In this example, the Batch Job has 5 child jobs and runs against 4 servers, and rolling execution (if enabled) is set to 2 servers.
The macro unmigrated-inline-wiki-markup from Confluence is no longer available.
The macro unmigrated-inline-wiki-markup from Confluence is no longer available.