Page 1 of 1
Control-M SAP
Posted: 20 Jun 2013 3:58
by Nick_2309
Hi All!!
We have around 100 jobs running with SAP module. But one job fails every day. When we check its logs it states that it submit but then disappear in 2 seconds.
When we verified with SAP team they told us that it never executed and also no sysout is generating.
But all other SAP jobs are running fine on same server.
Try LOAD on Account, Program, Variant etc
Posted: 21 Jun 2013 2:14
by Nightwatchrenband
Very odd to get no Sysout. My first try would be to open up the Job in the Desktop and do LOAD on the SAP account, Program, Variant. I suspect something is not quite right. Program will never run without these loading, and most of the time when these load the job runs. Good luck.
Posted: 25 Jun 2013 12:29
by Nick_2309
Thank you for your reply.
By No sysout I mean Sysout is created but of 0 size.
This job was running fine 1 month back but now it is not able to submit program in SAP.
Posted: 17 Nov 2013 6:41
by anirudhrh
Try a stop-start of the agent on which the job is running. that might work out for you . you can place all the jobs on hold . do a restart of the agent and release and run this job again .
PS - do check program name ,variant , and owner under SAP tab are correct/
Posted: 25 Nov 2013 9:03
by Manii
Hi Nick,
test SAP account using CCM test utility
also check in proclog directory cmsap* log file and see if any time out is occurring for the particluar SAP account or any other RFC error ...
Also from CCM for SAP module configuration increase the time out for SAP from 180 to 300
Make sure while you stop your agent u are killing all p_ctmag process on agent , old p_ctmag process can result in delay in job processing and malfunctioning.
then kill SAP process on server make sure to grep the correct SAP process by using
ps -ef | grep SAP | grep <controlm>
hope this will help you .
Regards,
Chandramani
