Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Purpose

This document is intended to provide an alternative for the analysis of KBA "2180934 - Analysis of Workprocess in "On Hold" RFC, or Stopped CPIC status" in case the system is not accessible through SAP GUI.
In this situation it could be possible to check the remote RFC side of the communication through OS tools and developer traces.

Getting the conversation ID

If a snapshot was written over the dispatcher trace file (dev_disp) at that time, we can check the information of theWork processandRFC-ConnectionTable.

If this snapshot is not available, this information can be triggered at run-time:

  • 1st option - write a snapshot on the dispatcher trace file with dpmon tool:

dpmon pf=<path to profile/profile name of the instance>

-->m       ( m - menue )
-->p       ( p - work-process-admin-table )

-->e       ( e - create snapshot )

  • 2nd option - Display the information from those tables

dpmon pf=<path to profile/profile name of the instance>

-->m        ( m - menue )
-->l         ( l - work-process-admin-table (long) )

-->c         ( c - RFC connections / Comm adm blocks)

The information from the session table could also be useful in some cases:

dpmon pf=<path to profile/profile name of the instance>

-->m        ( m - menue )
-->v        ( v - session table )

 

The important point for the analysis of this problem, is to link the request holding the WP being analyzed with its conversation ID:


Getting the information from the partner of the communication

Once we have the conversation ID, the remote RFC side of the communication can be checked:

Start gwmon tool on the application server affected by the problem and take the information of following options.

  • Connection table

gwmon pf=<path to profile/profile name of the instance>

-->m        ( m - menue )
-->1           ( 1 : display connection table )

In this example, we can see the conversation ID 10819513 is linked to connection number 0

  • Connection attributes
    With the conversation ID, we can check the details of the RFC server partner

-->5          ( 5 : connection attribute )
      ->6               (6: display partner attr )  -> enter the conversation ID


With the connection number , we could display more information of the connection if needed:

-->5          ( 5 : connection attribute )     
--> 1              (1: display connection )  -> enter number of connection

 



Each RFC connection is identified with the unique number (8 digits), called convID. This conversation ID is the same on the RFC client and the RFC server.

Now that we have the details of the RFC server partner, we can continue with the analysis as explained as of point 5 of KBA 2180934 - Analysis of Workprocess in "On Hold" RFC, or Stopped CPIC status

 

  • No labels