Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Reason for no dump during debugging between SELECT & ENDSELECT

Former Member

‎2007 Dec 03 9:29 AM

0 Likes
427

Hi,

Could anyone let me know the reasons for why there is no dump when debugging SELECT & ENDSELECT in versions ECC6.0?

SS

2 REPLIES 2
Read only

Former Member

‎2007 Dec 03 9:42 AM

0 Likes
397

HI

it won't show dump

ENDSELECT.

The ENDSELECT statement closes a loop started with SELECT.

A SELECT command for which the INTO|APPENDING [CORRESPONDING FIELDS OF] TABLE itab is inserted into an internal table, must be followed by ENDSELECT if the addition PACKAGE SIZE is used.

For all other SELECT commands, ENDSELECT must be used unless a single line above the addition SINGLE is read after SELECT and unless the columns of the result set are statically specified and contain only aggregate functions without the specification of the addition GROUP BY.

Read only

matt
Active Contributor

‎2007 Dec 03 10:55 AM

0 Likes
397

The old debugger would, from time to time, do a COMMIT on the database. If this happened in a SELECT... ENDSELECT loop, then the database cursor behind the loop would be destroyed, and you'd get a dump.

The new debugger works differently, and does not have this problem. Hence, no more dumps.

matt