Application Development and Automation 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: 
Read only

background job?

Former Member
0 Likes
647

hi all,

I ran one scenario in background and batch job is still running

from yesterday in development server. Job name is ZSSS_KDAS.

Where can I check this job.

How to debug this.

Can any one help me plz.

Gavas.

1 ACCEPTED SOLUTION
Read only

former_member404244
Active Contributor
0 Likes
611

Hi,

u can chek this in SM37....

Regards,

Nagaraj

4 REPLIES 4
Read only

former_member404244
Active Contributor
0 Likes
612

Hi,

u can chek this in SM37....

Regards,

Nagaraj

Read only

Former Member
0 Likes
611

1. Execute SM36 Transaction

2. Enter Job Name & Click START CONDITION

3. Click Period Values & type 12 in Months

4. CLick SAVE

5. Enter Schedule Start Date & Time

6. Click Save

7. Click on STEP

8. ABAP Program Name

9. enter program name & Variant if any

10. CLick on SAVE.

hope these r the steps u have done.

go to transaction sm36

press job selection

enter the jobname.

and then execute it.

it will show u the status of ur job.

there is no way to debug it.

Please reward if helpful.

Read only

former_member404244
Active Contributor
0 Likes
611

Hi,

Try like this

You can debug batch jobs by going to 'SM37', type in 'JDBG' in the

command line ( no '/' ), put the cursor on the job and press enter - will

take you to the job in debug mode.

You can do this only after the job has finished execution. This will simulate the exact background scenario with the same selection screen values as used in the job also sy-batch will set to 'X'.

So type in the transaction code 'JDBG' and place your cursor on the job after It has finished. It will take you to a SAP program in debug mode. Step through this program which is about 10 lines, after this your program will be executed in the debug mode.

Steps

1. Create variant called BACKGROUND for program to be debugged.

2. Execute ZDEBUGBG (pgm code below) in background for immediate processing.

3. Execute transaction SM50.

4. Select process that runs ZDEBUGBG.

5. Goto 'Program/Session' 'Program' 'Debugging'.

A se80 debug session will open.

6. Change variable W_EXIT to 'E'.

7. Step thru (F6) until ZWBTEST comes up.

1. Go to Transaction SM66 and find your work porocess.

Select the line work process is on and click on the Debugging button.

If this is a custom program, you can put a wait statement in the code to buy yourself sometime.

2. Go to Transaction SM50. From the tool bar "Program/session"->Program->Debugging.

goto SM37 and from Program menu(not sure.. try other menu's)

-->Catchjob . it will goto the active job in debugging mode.

Regards,

Nagaraj

Read only

Former Member
0 Likes
611

If ur job is still running, follow the following steps to debug ur job

1.goto SM51

2.double click on the relevant App Server name

3.select the relevant dialog process(BGD) of ur background job and now follow the menu path Program/Mode -> Program -> Debugging.

Message was edited by:

Rajesh