Job remain in status "released" with delay time increasingly.
These jobs are triggered by Third-party software(e.g. JP1, Control-M).
Besides, you can observe similar dev_disp trace like:
Thu Dec 18 10:29:46 2017
DpRTmPrepareReq: network error of client <T60_U22222>, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=DP_LOGGED_IN
Thu Dec 18 10:30:03 2017
*** ERROR => NiHLGetHostName: NiPGetHostByAddr failed (rc=-1) [nixxhl.cpp 503]
*** WARNING => NiAddrToHost took 17 seconds [dpTerminal.c 1702]
*** WARNING => DpAddrToHost: Disabling reverse name lookup [dpTerminal.c 1704]
DpRTmPrepareReq: client address of <T46_U11111> is 0.0.0.0(0.0.0.0)
***LOG Q04=> DpRTmPrep, NiBufReceive (<11111><RFC-JOB> <60> <saptermi01> ) [dpTerminal.c 706]
|SYNC_RFC |<T60_U11111_M0> |100|<RFC-JOB> |JP1host |10:30:00|12 |SAPMSSY1
DpHdlSoftCancel: cancel request for <T60_U11111_M0> received from DISP (reason=DP_SOFTCANCEL_NO_REASON)
Due to the network error of client <T60_U22222>, the session <T60_U22222_<Mode>> is supposed to be closed by dispatcher.
However, the dispatcher close the unexpected RFC session <T60_U11111_M0>.
Actually, the user <11111> (<RFC-JOB> ) is not a Gui-logon user.
It just looks like a GUI user coming from terminal <60>.
Meanwhile, you can see the incorrect session information in system log.
12/18/2017 10:30:03 <saptesthost_QSD_00> DP 0 Q04 Connection to user <11111> (<RFC-JOB> ), terminal <60> (<sapterminal01> ) lost
12/18/2017 10:30:03 <saptesthost_QSD_00> DIA 12 100 <RFC-JOB> R47 Deletes session <T60_U11111_M0> after error Execution was canceled (Softcancel) [Warning/Session]
Job delay,Q04,R47 , KBA , BC-CCM-BTC , Background Processing , BC-CST-DP , Dispatcher, Task Handler , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.