How to cancel batchjobs automatically

[Former Member]

Hello,

Is there a possibilty to cancel a batch-job automatically instead to do it manually with SM37 or SM50.

I know there there is a system parameter for dialog processes  (  rdisp/max_wprun_time ).

Some function in creating a job,  or maybre update TBT*** tables will help ?

Regards,

Reinhard Doeker

[AbhishekGupta1]

Hi Reinhard,

As per my understanding, you want to cancel jobs which are running but not doing any thing and has consumed all your work processes, so following suggestion for you:

a) you can not set time limit for background job.

b) yes, you can have few background jobs as class A so that those background jobs will be free

c) check if SAP_CHECK_ACTIVE_JOBS jobs is scheduled or not.

d) you can use sm61 to limit default background jobs to use all application servers by creating  a background group with the name "SAP_DEFAULT_BTC" & allocating 1 or 2 application servers to this group.

this will restrict your jobs (with no define server group) to run only on those application servers and you can use remaining app servers for other important jobs.

Regards,

Abhi

[Former Member]

Hello Reinhard Doeker

Run the below report

BTCTRNS1: Stops all batch processes.

BTCTRNS2: Restarts all batch processes.

check this:http://www.saptechies.com/standard-jobs-reorganization-jobs/

regards

alen

[Former Member]

Sure it's possible, see function modules BP_JOB_*.

[Former Member]

Hi,

If it is running on a particular time, and if it is the only job running, you can check if operation modes would help

But the best option is to check the source of the issue and disable it

[Former Member]

Hello Mudasir,

one time, a few weeks ago, no batch-processes were  free. A regular, scheduled (every 5 hours) job starts several time and didn't finished.

Monday morning all these jobs blocked the all batch-processes.

Seems they were in a loop  because they had runtime of 100.000 seconds or more.

So I cancelled all of them but didn't find any reason for this behavior.

It's not more a current problem but would be nice to know how can this be avoid.

Just have an idea......  maybe to use different job priorities.

A-B-C class.  This can help a little....

Thanks for all anwers,

Greating from Germany....   Reinhard

[Former Member]

Lock the step user

[Former Member]

Thanks for all answers.

But to lock the specific user could not be the solution because we are using one user-id

for all batch jobs. Also to reduce amount of background jobs to 0 will not help.

We want to have a function similar to dialog processes.

Here you can set the rdisp/max_wprun_time parameter. A process is canceled after reaching

this time. Afterwards the dialog-process is still available.

It seems there is no easy solution for batch-processes.

Reinhard Doeker

[Former Member]

Hi Reinhard,

Yes ,as  I said earlier ,you need to find out the from where these jobs are getting triggered .

Making background jobs to 0 and locking users is not the solution in a production environment.

Please try to investigate how and when this job is being triggered.Look at the start time and start condition of the job,try to find what actions in the system is creating this job.

That should be the right approach.

Thanks

Amit

[Former Member]

Hi Reinhard,

One of the basic reasons  behind using the background process is to run the reports  without getting cancelled  due to runtime limitations. If any report which does not qualifies in this criteria should be executed in dialog mode.

Can you tell us the reason you are trying to cancel the background processes automatically based on the run time ? May be we can suggest an alternate approach for it.

Regards,
Mudasir.

[Former Member]

Hi Reinhard,

  You can perform two options.

1. You have to deactivate the background work process by setting the instance parameter rdisp/wp_no_btc to 0  . This will deactivate all the background jobs..

If you want to disable only particular background job, then  please go with the second option.

2. You can lock the user under which the background jobs are running.

These are two ways to cancel the jobs automatically .

Thanks and Reards,

Vimal

[Former Member]

Hi Reinhard Doeker,

Program RSBTCDEL should be scheduled to run regularly to flush various database tables (TBTCO, TBTCS, BTCEVTJOB, TBTCP, etc.) to keep them from getting unnecessarily large.

see this link http://help.sap.com/saphelp_nw70/helpdata/en/c4/3a7ede505211d189550000e829fbbd/content.htm

Regards,

Prabaharan B

[Former Member]

Hi Reinhard,

I haven't come across anything yet which would kill a background job automatically(apart from a system issue,dumps ,errors ) ,and always a manual intervention is involved .

Please try to find out which is triggering these jobs .

Regards

Amit