We’re excited to introduce Submit Job Run in Parallel feature in IBM DevOps Deploy, a new capability designed to help you run multiple independent z/OS jobs at the same time instead of waiting for each one to finish before starting the next.
In many deployment and operational workflows, several jobs do not depend on each other. Traditionally, these jobs are often submitted one after another, which increases total execution time and slows down the overall process. With Submit Job Run in Parallel feature, you can now submit multiple jobs simultaneously and reduce pipeline duration significantly.
Why This Matters
When jobs are submitted sequentially, the total runtime is the sum of all individual job durations. For example, imagine you need to run these three jobs:
- Job 1 Takes 5 seconds
- Job 2 Takes 15 seconds
- Job 3 Takes 10 seconds
If submitted one after another, the total execution time would be:
5 + 15 + 10 = 30 seconds
With Submit Job Run in Parallel feature, all three jobs start at nearly the same time. In that case, the total runtime is driven by the longest-running job, not the sum of all jobs. So the total execution time becomes:
max(5, 15, 10) = 15 seconds
50% reduction in overall execution time. That means your process completes in half the time.
How to Setup
Upgrade z/OS Utility plugin to version 103 or latest version in IBM DevOps Deploy application. After the upgrade, In the Submit Job step a new input checkbox Run in Parallel will be available as shown below.
By default, the Run in Parallel input is unchecked. When selected it submits all jobs first and then wait for each job to complete until all the jobs are completed. The input checkbox Stop on Fail stops submitting jobs sequentially whenever a Job is failed. When Run in Parallel option is enabled, the input Stop On Fail must be unchecked as the Submit Job step cannot stop on a failure of one job as all the Jobs are submitted at once and must be processed. However if any job is failed the resultant status of the Submit Job step is marked as failed.
Conclusion
The new Submit Job Run in Parallel feature helps teams accelerate job execution by removing unnecessary waiting between independent submissions. In the example above, three jobs that would normally take 30 seconds sequentially can finish in just 15 seconds when run in parallel.
For teams looking to optimise automation and reduce overall processing time, this feature delivers an immediate and measurable improvement.
References