When using certain applications (like DNA), sometimes the application returns a non-zero return code but needs to be considered successful based on information in the Job Report itself. This is a guide for an example in setting that up so that whatever causes it to abort in Automic Workload Automation is ignored and it instead completes successfully. Please reach out to the community or to your account team to discuss customized solutions specific to your requirements and environment.
Release : 12.3
Component : AUTOMATION ENGINE
Please take a look at the documentation regarding output scans in Automic Automation: https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/12.3/Automic%20Automation%20Guides/help.htm#AWA/Objects/obj_output_page.htm#link4
As a very basic example:
If there is a Windows job that runs the command: dur
It will fail with a return code 9009 which can be seen in the footer info on the job report (REP):
UCMDJP: ** RET-CODE: 9009 **
To "catch" this and say that it should end ok instead, use the following steps:
Now when the job runs and has that string in the report, it will get an ENDED_OK status instead of ENDED_NOT_OK.