CA Workload Automation DE - Business Agents (dSeries)CA Workload Automation DEDSERIES- SERVERCA Workload Automation DE - System Agent (dSeries)CA Workload Automation DE - Scheduler (dSeries)
An issue on SAP server caused the SAP jobs to remain stuck in READY state. Why did the jobs stay in READY? Can they be force completed?
The WA Agents for SAP uses JCo or JavaConnector (provided by SAP) to connect to SAP and submit jobs. If for some reason the JCo is unable to connect to SAP the jobs may show in READY state in the manager side.
Check if the job(s) have ran and completed in SAP. Then, the job(s) may be force completed on manager / DE side.
Release : 11.3/11.4/11.5
Component : CA Workload Automation Agent for SAP
Check to make sure that the SAP server is accepting connections. Users can login via SAP GUI and may submit a test job.
It is likely that JCo may get stuck and is unable to retry the connection. Restart the WA Agent as JCo may need to reconnect again to the SAP.
Note: Jobs that have already come to the agent (submit by manager) will not get removed on restart of the agent.
If on restart the agent logs show errors like these then again make sure that there is no network or connectivity issue with SAP server. --- X/XX/20XX 00:00:01.234 +0100 1 main.Thread-16.CybSAPConfigAnalyzer.validateSapConfig[:1002] - Error: failed to connect to SAP. <com.sap.conn.jco.JCoException: (102) JCO_ERROR_COMMUNICATION: Connect to SAP gateway failed Connection parameters: TYPE=A DEST=TEST_CCS01:100:EN:CAPROD ASHOST=saptest01 SYSNR=95 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.20.30.40:1234' not reached TIME Sun JAN XX XX:XX:XX 20XX RELEASE 721 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 2902 DETAIL NiPConnect: 10.20.30.40:1234 SYSTEM CALL connect ERRNO 79 ERRNO TEXT Connection refused COUNTER 3> X/XX/20XX 00:00:01.234 +0100 1 main.Thread-16.CybSAPConfigAnalyzer.validateSapConfig[:1005] - FAILED: SAP config validation.