Troubleshooting: Tasks Stuck in Running Status
Jobs can get stuck in a Running status if the server specified in the Server Name field for the Agent is not correct. The RA JD Edwards Agent uses the server name specified there to query for task statuses. If the server name does not match JCEXEHOST in the Master Job Table (F986110), tasks will not complete in the Automation Engine.
If Agent TRACE is on, the log will include entries like the following:
2010-09-10 09:20:26 Entry getJobStatuses
2010-09-10 09:20:26 Get connection
2010-09-10 09:20:26 Define SQL
2010-09-10 09:20:26 Execute SQL:Select JCJOBNBR, JCJOBSTS from F986110 where JCEXEHOST='vwadev08' and JCJOBNBR IN ('915')
In the SQL above, vwdev08 is defined in the Server Name field and must match what's in the JCEXEHOST field of the master Job table (F986110).