How to stop the job for next schedule when previous job status failed

[Inaganti Ramesh]

We have a box and containing two command jobs (JobA and JobB). JobB dependent on JobA.
The box is running every 5min, if the jobB fails , next irritation of jobB should not be happen until user take manual or success. but box job will run as usual as per schedule.

user is looking for don't want schedule for 2nd time(instence) when jobB fails at 1st time(previous instence) until user take any action.

do we have any solutions for this scenario?

[Corrie Kantowski]

We have a box conditioned to start only when it has a status of SUCCESS - a circular reference. If it fails, it will not run until the user takes the necessary action and manually sets the status to SUCCESS>

[Michael Woods]

Hi,

I can think of two similar approaches.  They both add a third job that runs on failure of jobB.

The first is to move jobB out of the box and the new job will issue a sendevent -E JOB_ON_HOLD -j jobBso that it doesn't run until you manually take it off hold.  Since jobB is outside the box, it and jobA both run every five minutes as desired.  Jobs downstream of jobB will not run, but those on the box will run.

The second way is that the new job issues a sendevent -E JOB_ON_NO_EXECUTION -j jobB.  The box runs as normal, but jobB does not run the actual command.  Any downstream dependencies on jobB will still process in this case as will those on the box.

Regards,

Mike