cancel
Showing results for 
Search instead for 
Did you mean: 

Background jobs don't start

Former Member
0 Kudos

Hello,

i have a problem. Whenever a background job should start e.g. EU_REORG or own background jobs, the jobs last in status released for hours and never start. So I have many similar jobs, which have not started and a continuous increasing delay.

What could that be? I'm using a R/3 4.7 110 with 620 Kernel.

Thanks

Frank

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Frank,

OK, something has happened in the past to cause this build up of jobs in the queue but I'm not sure what.

If the majority of the waiting jobs have a particular name, I would filter the released ones for these particular jobs in the SM37 display, select all, and delete all but one of them from the system. This should leave the newest released one to execute.

Regards,

Gary

Former Member
0 Kudos

Hi Gary,

i will try it thanks for your help. I have found the one "bad job". It was a SWEQSRV Job.

Regards,

Frank

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Frank,

Do you have a large number of jobs prefixed ARFC ?

Regards,

Gary

Former Member
0 Kudos

Hi Gary,

no just a large number of EU_REORG and PUT, RDDIMPDP (i think the most) and some others.

Regards,

Frank

Former Member
0 Kudos

Hi Frank,

Some things that you could check;

1) SM65 to see if the server is configured correctly

2) There are BGD processes available

3) SM61 to see that the time-driven scheduler is active

4) SM37 to see if there is a large queue of released jobs

Let me know the outcome of the above checks.

Regards,

Gary

Former Member
0 Kudos

Hi Gary,

check 1, 2 and 3 are correctly. But the queue of released jobs is very large. Does it mean i have to cancel all of them and reschedule them? Mmmmhh it's quite a work, but when it helps to solve the problem.

Thanks