We are experiencing issue with our some of the autosys capchain jobs which are getting terminated with aborted signal 11 within a minute or so when they are started on agent but the process chain starts running and gets completed successfully.
Its happening intermittently and not to any specific job or SAP system. Only isolation of the issue is that all these jobs are process chains and have term_run_time defined to some value which is way greater than a minute.
I am suspecting that some timeout is occurring while retrieving job status from either SAP adapter to agent or SAP system to SAP adapter but not able to find exact issue.
Can you please help us on this issue. Thanks !
- Aditya B.
There's an sap plugin update. get the latest sap.pak. i am assuming you are using the sap job types etc.
We dont have SAP Plugin. We are using SAP adapter connected to run job in SAP system. Thanks !
We typically have to look at the full std_out_file for the job to see what the last thing the adapter was doing when it aborted.
What is the exact version of the CA JMA for SAP r3.2? SPx?
What is the CA WA System Agent version?
Did capchain jobs work previously? If yes, what changed?
I guess some kind of heartbeat is being sent across to the Scheduler by the SAP Adapter to the CA WA System Agent and either the System Agent or the Scheduler does not seem to like it.
CA JMA for SAP r3.2 SP3 removes heartbeat by default.
CA WA System Agent 11.3 SP7 handles heartbeat signals from SAP Adapter better.
Hope this helps.
Thanks for your detailed reply.
CA JMAdapter Version: 03.02.00.11CA Agent version: 11.3 SP4 INCR1Yes capchain jobs were working fine. No activity was performed on Autosys as whole when the issue started.
Can you suggest more on this issue.If this can be fixed by changing any parameter instead of upgrading the agentor adapter.
Consider upgrading the WA Agent to 11.3 SP7 and the SAP Adapter to SP3.
As Scott said, we need to review the entire std. out to be able to determine what is causing signal 11. If you are using the capchain executable then turn on additional logging using the B option and review the steps from the log.
If you are unable to ascertain the cause, please open a Case w/ CA Support.
If you prefer to extend the heartbeat to its maximum value (25 hours) instead of installing UJMSAP 3.2 SP3 to disable the heartbeat feature, open the UJM SAP configuration assistant with command casapjmacfg and increase the Heartbeat pace to 999 with a polling interval set to 120.
Then let's see what happens to your new long running SAP jobs.