It sounds like Autosys is not receiving notification from the remote machine and/or subsystem on the command's disposition. This is especially common for commands that start a process on a subsystem (or remote application) and then there are issues with that subsystem/remote application not returning a disposition. So Autosys can only report it's last known status, which is "RUNNING".
Bo Marshall
Applications Systems Analyst/Programmer
IS_PCT - Production Control Team
[cid:
image001.png@01DB0C07.BAB6FB20]
2050 S. Linden Road | Flint, MI | 48532
Cell: (586) 243-6126
jmarshal@hap.org<mailto:
jmarshal@hap.org>
For faster response to your needs & better collaboration, kindly email:
IS_PCT<mailto:
is_pct@hap.org> email group for PCT requests
Support Hours:
Normal: M-F 8:00am - 4:30pm
On-Call: M-F 6:00pm - 6:00am/Sat & Sun (Emergency & P1/P2 Incident related requests)
[A picture containing clipart Description automatically generated]<https:
www.hap.org/="">[A close up of a sign Description automatically generated]<https:
www.linkedin.com/company/health-alliance-plan/="">[A picture containing object, first-aid kit Description automatically generated]<https:
www.facebook.com/hap/="">[A picture containing ax Description automatically generated]<https: twitter.com/hapmichigan?ref_src="twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor">[cid:
image006.png@01DB0C07.BAB6FB20]<https:
www.instagram.com/hapmichigan/="">CONFIDENTIALITY NOTICE: This communication contains information from HAP that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY, or otherwise protected from disclosure. The communication is intended for use only by the person to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this communication, is strictly prohibited. If you received this communication in error, please contact the sending party at the above telephone number and shred or delete the communication.
Original Message:
Sent: 9/20/2024 3:24:00 AM
From: Antony Askew
Subject: RE: Job = Terminated, but job was successful
I'd start with the Agent log/spool files from the terminated job executions. The Agent should be waiting for the child (job) process to complete, and return an exit code back to the Agent.
Original Message:
Sent: Sep 19, 2024 02:06 PM
From: Corrie Kantowski
Subject: Job = Terminated, but job was successful
We are running Version: 12.0.01/Oracle 19c, Agent Version: 12.1.01.00-7314 on Operating System: Red Hat Enterprise Linux 7.9. We have one WCC server.
We have a situation where a command job (run in CaaS) runs successfully most of the time in less than 1 minute. However, at times, it appears that the result does not get reported back to Autosys, and the job ends up terminating after the 10 minutes specified in the job definition. This looks like it has occurred (quite often) on other jobs as well. Can you tell me how I should begin to troubleshoot this?
</https:></https:></https:></https:></https:></mailto:is_pct@hap.org></mailto:jmarshal@hap.org>