Hi James,

We have a feature in Software Deploy and BLPackage based Deploy Jobs where you can choose the option of Run By Server.

Specifying job options - BMC Server Automation Documentation - BMC Documentation

If you are defining an advanced BLPackage Deploy Job, take the following steps: 

1. Under Flow Control, select one of the following options: 
   • By server — The job proceeds as far as it can for each server. When one server fails, the job continues on other servers. When the job completes a phase on one server, the job continues to the next phase on that server. This option is useful when you want the job to complete on as many servers as possible. A failure on one server does not impede the job on other servers.

Hope this is what you are looking for.

Thanks

Nitin

Have you explored the NSH script as an alternative to implement the above process.

You could run an NSH script Job with as per the pseudo algorithm:-

FOR EACH SERVER:

1> NSH script to stop services

2> Check result of step1

3> Create a Patching Job with Remediation and Deploy options - Refer BLCLI Help PatchingJob - BMC Server Automation Command Line Interface 8.6 - BMC Documentation

4> Run the Patching Job created above..

5> Check result of step 4.

6> NSH script to start services.

Thanks

Nitin

if you set the batch job to run 'by server' and set the 'member jobs must succeed' or whatever so a member job failure stops successive jobs from running will that work ?

also - what does 'remediate server' mean here ?