When an incorrect command within an abox is executed via swbatch command, why does swbatch exit with the same exit code as when it suceeds correctly?

When an incorrect command within an abox is executed via swbatch command, why does swbatch exit with the same exit code as when it suceeds correctly?

book

Article ID: KB0091392

calendar_today

Updated On:

Products Versions
TIBCO iProcess Engine (Oracle) -
Not Applicable -

Description

Resolution:
When swbatch fails (for example the wrong procedure name is inputted) it produces the same exit code as when it suceeeds.

This is the expected behaviour, swbatch returned 1 that means successful.

Although one of the START commands can not to be executed, it does not influence the others . SWBATCH  will continue to execute the other commands.

Basically the error code is the status of the entire program rather than the individual execution.

Issue/Introduction

When an incorrect command within an abox is executed via swbatch command, why does swbatch exit with the same exit code as when it suceeds correctly?
Powered by Wolken Software