Debugging

Former Member — Sat, 14 Apr 2007 10:09:06 GMT

is debugging possible with in select....endselect ? give me the reasons plz..

Re: Debugging

uwe_schieferstein — Sat, 14 Apr 2007 10:25:58 GMT

Hello Mohammed

It is possible to debug within a SELECT - ENDSELECT loop. However, sometimes this will result in a dump due to some interference of the debugging with selecting the data from the DB tables.

Regards

Uwe

Re: Debugging

Former Member — Sat, 14 Apr 2007 10:29:27 GMT

Hi,

Debugging is not possible between select and end select.

may the reason is SELECT is not a part of abap. it comes in native sql.

Regards

Ramesh

Re: Debugging

Former Member — Sat, 14 Apr 2007 11:07:25 GMT

Thank you for the reply, could you explain me the exact cause for the dump over here....(select..endselect)

Re: Debugging

Former Member — Sat, 14 Apr 2007 16:47:50 GMT

Hi Younus

If you are debugging in between a select-endselect statement, it may lead to Dump due to the explicit commit work that is done by the debugger.

Refer this link for more info:

<b>

debugging a SELECT...ENDSELECT statements brings to a LUW commit work if no other work processes are available for debug.

See OSS notes 675, 2104.

From OSS note 675 **********************************

Cause and prerequisites

Chain of causes:

1. There is a statement in one of the Select loops, that leads to a database Commit (or Rollback).

2. A database Commit causes the database to lose the cursor.

3. The system cannot automatically continue within Select loop after loss of cursor.

Following statements lead to a database Commit:

All statements that cause a change of screen (CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT, I/W-Message)

BREAK-POINT/ Debugging

. if no debug process free

. always after regeneration (in order to release generation lock).

WAIT Here a work process is released and a Commit is executed.

COMMIT WORK/ROLLBACK WORK

From OSS note 2104 **********************************

Solution

The "COMMITWORK" message appears in the ABAP debugger when programs

orscreensrequireregeneration,or when not enough free capacity

is available inthesystem (or else the debugger blocks a system

process).

Normallyonly one work process is released for debugging. This

isgenerally insufficient ina developmentsystem, as processes

can be blocked for other reasonstoo(background processing,

CPI-C connections,andso on).

The number of work processes made available for debugging can

be configured using the profileparameter

rdisp/wpdbug_max_no

Forexample:

rdisp/wpdbug_max_no = 10

setsthe maximum number of work processes made available for

debuggingto 10. It may be necessary to generally increase the

numberofwork processesatthis time (parameter rdisp/wp_no_dia).

In all other known cases, an error in the application program is

involved.

if it heps reward with points

Regards,

Message was edited by:

Rk Pasupuleti

topic Re: Debugging in Application Development and Automation Discussions

Debugging

Re: Debugging

Re: Debugging

Re: Debugging

Re: Debugging