09-26-2008 7:13 AM
Hi Friends,
My Z program has a bug when run it in Quality System.
If I run this program in foreground to debug, its giving TIME OUT dump.
If i try to run it in Background and started DEBUG mode using JDBG.
Still one of the table fetch gives TIME OUT dump.
Is there any possibility to DEBUG the already executed job?
Regards,
VIJI
09-26-2008 7:25 AM
Hi,
If the job is running go to SM50..
Select the process:
In the menu..Program/session -> program -> debugging..
OR
Fix the break points.
2) Create job.
3) Go SM37
4) Select the job and write "jdbg" in command line.
1) Use Transaction SM50. This would give you a view of all the background
processes running in the server.
2) Choose your background process from the list and got to
MENU "Program/Mode"->"Program"->"Debugging".
Regards,
Suresh Kumar
09-26-2008 7:25 AM
Hi,
If the job is running go to SM50..
Select the process:
In the menu..Program/session -> program -> debugging..
OR
Fix the break points.
2) Create job.
3) Go SM37
4) Select the job and write "jdbg" in command line.
1) Use Transaction SM50. This would give you a view of all the background
processes running in the server.
2) Choose your background process from the list and got to
MENU "Program/Mode"->"Program"->"Debugging".
Regards,
Suresh Kumar
09-26-2008 7:30 AM
Hi Suresh,
Thanks for your reply.
I have tried this using the JDBG transaction too.
While doing the same one of my SELECT statement takes up long time to fetch the data from DB table.
So its giving TIME OUT dump.
Can u gimme some other way to do the debugging.
Or is it possible to debug a Job which already executed in the Background?
Regards,
Viji
09-26-2008 7:31 AM