We have a CMD job which is terminating with a code 20003 when it reaches its "term_run_time:" value.
in the log (also attached) i can see that this job is routinely getting a termination status of
<Process has been cancelled>
[10/17/2021 03:00:03] CAUAJM_I_40245 EVENT: STARTJOB JOB: <name of job>
[10/17/2021 03:00:04] CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: STARTING JOB: P<name of job> MACHINE: <name of machine>
[10/17/2021 03:00:04] CAUAJM_I_10082 [CTBBITSDPVD51S connected for <name of job> 26206.45708129.1]
[10/17/2021 03:00:13] CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: RUNNING JOB: <name of job> MACHINE: <name of machine>
[10/17/2021 07:00:45] CAUAJM_I_40245 EVENT: CHK_TERM_RUNTIME JOB: <name of job>
[10/17/2021 07:01:04] CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: TERMINATED JOB: <name of job> MACHINE: <name of machine>
[10/17/2021 07:01:04] <Process has been cancelled>
where as normally, when a job reaches its "term_run_time:" value it gets a status of <Terminated by user>
example:
[10/17/2021 07:02:39] CAUAJM_I_40245 EVENT: CHK_TERM_RUNTIME JOB: <name of job>
[10/17/2021 07:02:40] CAUAJM_I_40245 EVENT: CHANGE_STATUS STATUS: TERMINATED JOB: <name of job> MACHINE: <name of machine>
[10/17/2021 07:02:40] <Terminated by user>
Not sure if this additional status is causing the 20003 error or why this error would be occuring. We have various monitoring around 'terminated' jobs but this errant 20003 status is evading our log scrubbing. Not sure what's causing it.
Release : All
Component : AutoSys
The difference between Windows and Linux event text is expected as the event text comes from Agents running on Windows/Linux.