debug background job program

[Former Member]

Hi,

i am debugging the program in background mode,

first time i was successful in capturing the job,

second time it is giving error, capture job is failed.

sm37 , jdbg also not working, its given error like bebuggin is not possible in active mode.

in sm50 transaction, it is giving some information message like user reached maxium debugging modes. some error.

please help me, it is very urgent

thanks in advance

points will be rewarded

[former_member435013]

Hi,

change source code in a way like this:

DATA:

stop_for_capture.

DO.

IF sy-uname NE 'HABICH'. "change to your account

EXIT.

ENDIF.

IF NOT stop_for_capture IS INITIAL.

EXIT.

ENDIF.

ENDDO.

So you have enough time to capture.

proceed by changing value stop_for_capture.

regards

Walter Habich

Edited by: Walter Habich on May 23, 2008 9:56 AM

[Former Member]

I have done the same thing but it is not working, it is displaying the error message like capture job is failed

[former_member435013]

Hi,

that sounds strange. What is your environment.

Is debugging possible in general?

Do you have &SAP_ALL ?

Is BDC involved?

Perhaps You may use ST01 System Trace.

An ugly option is coding some file output in the test program.

Start Debugging before capturing and set a break-point for ABAP message command.

I hope my comments are useful.

regards

Walter Habich

[Former Member]

As I was searching for an answer for the same thing, I also found here on the forums that you can add an extra step in your job with program BTCLOOP. This program already exists, then it comes also in an infinite loop and you can go into debugging from SM50.

Hope this helps.

[Former Member]

hi

if the job is in scheduled or released state then only it is possible to debug the job in jdbg

if the job is in acive sae then only u can debug it though sm50

[former_member182371]

Hi,

have a look at this:

http://www.saptechnical.com/Tips/ABAP/ActiveJobs/Debug.htm

Best regards.