Default error handling ensures that during job execution, if a restrictive constraint is effective, the processing flow is interrupted and the transaction is rolled back.
In addition, you can add user-defined error messages to raise errors that you only want to occur in specific situations.
Return status in Batchrunner calls
When a job called using the RunJob method or using a job method fails, the error is displayed and the statement fails, just like any other INVOKE statement. For example, when the RunJob method is called from a SQL task, the SQL task stops when the Abort Mode attribute of the task has been set to Abort Task on Error, or Abort Job on Error.
You can modify this behavior using the RunJob ReturnStatus parameter to ensure that the BatchRunner statement does not fail. See BatchRunner.RunJob() for more details.
If the RunJob ReturnStatus parameter is set to yes, you can use the ensuing statement in a decision.
WHERE '<Result>Error</Result>' != BatchRunner.RunJob('J1' as jobname, 'true' "-quiet", 'Yes' "ReturnStatus")