Windows job finish successfully with exit code 0 even if a child process has a Dos err

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

An Windows SQL Job may end in a Finished status even though a sql error is thrown running the Job's sql script.

Below is an example output where a sql Jobs ends with a non zero error code but the final error code is set to zero resulting in a Finished status.

 

SQLPROCED2P: Exiting with return code 2304.

AFTER WAIT FOR EXIT
                                                       
Windows return code 0
ErrorLevel

Set exitCode to 0
ntspawn exiting with exitCode 0
Closing debug file
Closing debug file
                               
end of C:\Appmgrqa\Master\exec\BODY2.BAT status 0 Fri 09/22/2023 11:48:00.00
err is:'0'

 

Cause

Windows Job is not reading the dos error log file

Resolution

This will be fixed in a Applications Manager version 9.6 (fixed version and release date is tentative)