Condition - When the next generation or job is completed, In this case, the failed generation should be forced to complete.
Please advise the solution to it.
dSeries 12.3 version
Please see the execcommand syntax here -
Hello Ravi,Thanks for sharing the solution to our query. However, we need the previous failed generations to be force-completed only once the latest generation is completed successfully.
Original Message:Sent: Nov 17, 2023 01:10 PMFrom: Nitin DivakarSubject: Auto force complete failed generation/job
Yes, this new job like a link job should be the last job in the application. So all other jobs are completed then only this new job will start and it will force complete the previous generation.
Hope I am able to clarify it.
var a = parseInt(APPL._gen);var b = a -1;execCommand('TASK0', 'VERIFY.%(b)', 'ACTION COMPLETE Reason("complete to run the next job")');(or)execCommand('ALL','VERIFY.%(b)', 'ACTION COMPLETE');
execCommand('ALL','VERIFY.%(b)', 'ACTION COMPLETE'); ----- This command will Force Complete all the Jobs of last generation of VERIFY application.
execCommand('TASK0', 'VERIFY.%(b)', 'ACTION COMPLETE Reason("complete to run the next job")'); ---- This Command will force complete TASK0 job of VERIFY application of last generation of Application.
Original Message:Sent: Nov 20, 2023 05:59 AMFrom: Ravi Kiran KunduriSubject: Auto force complete failed generation/job
Thanks for the solution provided, we have tried but didn't fulfill the requirements (i.e. It does not mark the older generation force complete after its current generation got completed successfully).
Could you please assist us with this concern?
Original Message:Sent: Nov 21, 2023 12:50 PMFrom: Faiz AhmadSubject: Auto force complete failed generation/job
Ok. We will need to know why this did not work at your end by looking at logs and what you did. I will suggest that you raise a ticket for this with the support.
Faiz how many generations of failed Applications/jobs are there before you have one that completes successfully? Why would you only try and force the failed Applications complete once you get a good execution in later generations?
The solution you are looking for might be different depending on your answer. If you have a failed Application, yet you allow other generations of the same Application/Jobs trigger in, you might just want to put a COMPLETE All Link into every Application with a time delay or something to assure you have time to allow all jobs to complete successfully. I assume you have built in notifications for failure etc. to know a job failed?