topic Re: Reason for no dump during debugging between SELECT & ENDSELECT in Application Development and Automation Discussions

Reason for no dump during debugging between SELECT & ENDSELECT

Former Member — Mon, 03 Dec 2007 09:29:16 GMT

Hi,

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

Re: Reason for no dump during debugging between SELECT & ENDSELECT

Former Member — Mon, 03 Dec 2007 09:42:59 GMT

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.

Re: Reason for no dump during debugging between SELECT & ENDSELECT

matt — Mon, 03 Dec 2007 10:55:39 GMT

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