How to Debug in CALL FUNCTION Starting new Task

[Former Member]

Hi,

i create a lot of parallel Function Calls during my code:

DO 50 Times.

CALL FUNCTION 'Z_DO_SOMETHING'

STARTING NEW TASK lv_task_name

DESTINATION IN GROUP p_group

PERFORMING get_results ON END OF TASK

...

If i now go into debugger and press F5 before Call Function, a new window opens, where i then see the Function Z_DO_SOMETHING and i can debug it there. Fine.

Now if i set a Breakpoint somewhere (does not depend if i do it directly in the coding or if i create it in the "Breakpoint"-tab of the debugger, internal and external breakpoints) and click save in the debugger (to save the Breakpooints) and i press F8, the debugger never stopps at the points.

The reason for this is, if i then debug again in this Function Z_DO_SOMETHING (for example in the second loop round), i can see that the breakpoint tab is completely empty. So why are my breakpoints deleted? Why i have to create them in each session which is triggered by the coding above seperately? How can i set a break-point which works in such cases?

Thanks & Kind Regards,

John

[Former Member]

Me personally would code an infinite loop into the FM, just dont forget to add a ending condition.

Then you can capture the mode in SM50 and jump into debugging it.

Then change your variable assigned to the ending condition of your infinite loop, so that it stops looping, and now proceed to debug the rest of coding.

[SuhaSaha]

Hey Florian,

That's a crude but very effective way of debugging aRFC

PS: If i remember you're not a hard-core ABAPer !!

[Former Member]

aye you´re right i´m more into FORM-Printing, but well i tend to get SD and MM jobs more and more, so yeah expierience is growing

[Former Member]

Hi Keshav.T ,

sorry, i don't understand your post. I have read the link you posted, but how can i inflience now the ABAP Debugger to debug these cases?

Thanks

[Maciej_DomagaBa]

See notes: 573128, 444078

regards