shared cursor with program name disp+work

[Former Member]

Hi All,

I am tracing performace issue with shared cursor.

I find there are many bad performance shared cursor entries with program name "disp+work.exe".

Does anyone know what situation cause it happen ?

As far as i know, RFC doesn't create this kind of entry.

The program name of shared cursored cache entry show function module name when RFC call.

BR

Sean

[markus_doehr2 · Accepted solution]

> I am tracing performace issue with shared cursor.

> I find there are many bad performance shared cursor entries with program name "disp+work.exe".

That's the SAP kernel and contains basically all the ABAP runtime.

How do you find out, that the "shared cursor" is the problem?

Markus

[Former Member · Accepted solution]

Hi Markus,

I find some "disp+work.exe" cost much time to run sql statement.

I want to trace back to find out the program which call "disp+work.exe" .

Then i can verify the program again, maybe chagne some code can solve the performance issue.

But first of all, i need know which program call disp+work.exe .

Best Regards,

Wu

[Former Member · Accepted solution]

Hi Wu,

Disp+work is not an ABAP program which means that the SQL statement has been called by kernel itself. It is an internal call. Because of this you are not able to see an ABAP program belong to the statements.

Best regards,

Orkun Gedik