Background to Debug mode

Hi Addepalli,

From dump analysis you can debug where dump has

triggered. Goto St22 transaction and check.

I think immediatly only we can check it.

best way is goto SM50 and locate your job and then in

the menu Program/Mode -> Program -> Debugging.

Hope this will help you.

Thanks&Regards,

Siri.

Message was edited by: Srilatha T

Hi,

In transaction SM50, you can choose the background process running this program and cleck the menu item Program/Mode --> Program --> Debugging...

If it is a Z-Program write an endless loop(at the start of the program) with an exit condition(which does not exit normally)...so that the background process will be stuck in this loop...Then choose debugging as mentioned...then change the exit condition correctly in debugging so that you are out of the endless loop...This is for making sure that the by the time you get to SM50 the execution is not over....

Thanks & Regards,

Renjith.

Hi,

According to my knowledge, if you put a hard break point in an ABAP program and execute it in BAck ground mode, it doesn't stop there.

It means that Break point doesn't work for background execution program.

Its better you run the same by putting a Break point in online mode.

Hi In SM50 select your Program and Go to Program Debugging.

regards

vijay

a variation on some of the other answers, from transaction SM37 you can go directly to debug via job->capture active job. Again you will need it to run for some time to be able to capture it so you'll probably need to put an infinite loop in. Use of Job Capture is sometimes restricted at certain sites so you may not be able to use it.

In SM37: Select the job, type JDBG in the OK-code and press enter. This can be used for both completed jobs and jobs to be processed (just make sure you have enough time to debug before the job actually starts). Breakpoints set in the job flow works.