Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Need to know about where the background job got strucked

former_member194747
Participant
0 Kudos

Hi all,

Can anyone tell how to find, where a particular program getting strucked while it is running in background. Also onemore thing is that, i need to find this in active status of that job.

1 ACCEPTED SOLUTION

hymavathi_oruganti
Active Contributor
0 Kudos

in sm36 u can see in job log.

6 REPLIES 6

hymavathi_oruganti
Active Contributor
0 Kudos

in sm36 u can see in job log.

Former Member
0 Kudos

Hi,

In transaction SM37 you can see the Status of the job.

1. Go to SM 37 and Enter the Date and press F8.

2. Select your Job and press CTRL + SHIFT + F11 For Job Log.

Thanks,

Reward If Helpful.

Former Member
0 Kudos

In your code always throw type E messages in case of errors so that these messages get captured in Job log. Later

in SM37 select the job and goto job log to see at what message it is stopped.

former_member194747
Participant
0 Kudos

Hi all,

Thanks for your answers.

I will tell you the scenario little bit clear so that i can get exact answer what i need.

I have scheduled a job in background, which is having only one step(Program) to run. That program fetches data from different tables and puts in single table.

i want to know, where that program gets struked, that is at which table, is that problem with fetching the data, or is that problem with putting inside the another table, or is there any problem with data in that table, or problem with that program itself.

Former Member
0 Kudos

Hi,

U can always debug a back ground job.

Put an infinite loop in your code. and run it.

then goto sm66 identify your work process and goto debugging.

Search in SDN " debugging background Jobs" for more info

former_member194747
Participant
0 Kudos

Closing Thread.