ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SAP jobs running on specific instance stuck running / ready state


Article ID: 237407


Updated On:


CA Workload Automation AE CA Workload Automation DE CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation DE - Business Agents (dSeries) CA Workload Automation DE - System Agent (dSeries) CA Workload Automation DE - Scheduler (dSeries)


The job SAP starts and is submitted by manager to agent.  The job appears to have been submitted by WA agent to SAP.  

The user is able to verify that job completes in the SAP instance.  However, WA agent never sends the complete state to manager.  Also,  normal command jobs run on the agent send by same manager.


Following error may be seen in the agent logs.

XX/XX/2022 00:00:12.345-0400 1 main.Thread-8.CybSAPConfigAnalyzer.validateSapConfig[:1002] - Error: failed to connect to SAP. < (102) JCO_ERROR_COMMUNICATION: Connect to message server on host failed                    
Connection parameters: TYPE=B DEST=COR:800:EN:AUTOMATE R3NAME=COR GROUP=Automation_COR PCS=1 
ERROR       service '?' unknown                    
TIME        Thu Mar 7 00:00:00 2021                      
RELEASE     721                         
COMPONENT   NI (network interface)




Release : 11.x/R12.x

Component : Workload Automation System Agent for SAP


Add and entry for SAP instance in:


in Linux/UNIX:


If the SAP instance is called COR and port is 3600, then entry will be like below (pre-pend instance with sapms):

sapmsCOR 3600/tcp


If port and instance name is unknown, then consult SAP admin. After the entry has been added, restart WA agent.


Sample SAP instance used by agent (instance name used here is COR, change it accordingly): :