Background jobs behaviour after a stopsap/startsap

[benoit-schmid]

Hello,

I am wondering how background jobs behave in case of long stopsap period.

I have checked in sm37, my colleagues do not set "No Start after" time.

I will stop sap on Friday night and restart it on Saturday morning.

Will all the jobs that were released for this inactive time window

be started just after starting sap?

Thanks in advance for your answer.

[Former Member · Accepted solution]

Hi  ,

If you do not suspend the jobs ,they will get queued for running once the SAP system is up .

Please always follow the suspend /start the jobs before you stop/start SAP.

BTCTRNS1 : tempararoly suspends all the released jobs in SAP.

BTCTRNS2 : It will release all the jobs which are suspended by the earlier report.

Regards,

Srini Chapa

[benoit-schmid · Accepted solution]

Hello,

For support packages, do you deactivate your background jobs?

Thanks in advance for your answers.

[Former Member · Accepted solution]

Hi,

Yes I deactivate the b/g jobs before upgrade.

For more info,

Please refer note Note 37425 - Cancel job during
upgrade

It says:-

Any scheduled RDDIMPDPs (also triggered by an event) are not affected.

These are the main jobs which runs in the SP upgrade.

Cheers,

Vishal

[benoit-schmid · Accepted solution]

Hello,

But a Support Package is not an upgrade.

This is why I specified SPS.

Thanks in advance for your answers.

[Former Member · Accepted solution]

Hi Benoit,

It is used in SP upgrade also.

Please go through following note:-

Note 744343 - Tips for importing
Support Packages with minimized downtime

Cheers,

Vishal

[Former Member · Accepted solution]

Hi Benoit,

Upgrade shouldn't be taken in the literal sense of the word. Other SP application is like an upgrade.

Anyways you need to suspend any released jobs because they would have standard reports/programs which could be changed by Support Packs and you want to avoid the conflict of report getting changed while getting executed. Why only report other data dictionary objects being probably used by those reports could get changed.

Gurbir said earlier load is a factor. While I don't agree but it is certain no other program running on App server can improve performance of SP application.So in that sense it is a useful suggestion though not the prime reason IMO. Infact jobs for non-standard reports should also be suspended since these reports though not directly changed by SP can be using some standard SAP objects which could be affected by SPs.

Regards.

Ruchit.

[benoit-schmid · Accepted solution]

Hello Ruchit,

Ruchit Khushu wrote:. 
Anyways you need to suspend any released jobs because they would have standard reports/programs which could be changed by Support Packs and you want to avoid the conflict of report getting changed while getting executed. Why only report other data dictionary objects being probably used by those reports could get changed. 

Ok, this means that I would get short dumps in case of problems.

What about changes in SAP table structures?

Is there a SAP mechanism to avoid "wrong" update in the modified tables?

Thanks in advance for your answers.

[benoit-schmid · Accepted solution]

Hello Vishal,

Vishal Basis wrote:
Hi Benoit,
It is used in SP upgrade also.
Please go through following note:-
Note 744343 - Tips for importing 
Support Packages with minimized downtime
Cheers,
Vishal

Thanks for the Note.

It says that we CAN disable the jobs but not that we MUST.

See you,

[Former Member · Accepted solution]

Hi Benoit,

When I used other data dictionary structures I covered "SAP table structures" as well.

Further there is no mechanism to avoid wrong update of modified tables other than stopping any updates to these tables !!

So all users should be locked (of course except a select few but including all RFC users which might update from external RFC calls) and all background processsing ought to be suspended. No transports should happen.

To say you can and not must suspend background processing is what the given OSS note says (as per a comment by you in the earlier post) is perceptive but a fallacy as far as I see.

You should suspend background processing and lock all users.  We all do it.

Support packages can throw up a lot of issues on their while getting applied.. The least you can do is avoid other sources doing things cause more of these errors.

Regards.

Ruchit.

[Former Member · Accepted solution]

Dear,

I would interpret it as either you can use this Report to disable the jobs automatically or you have option  of manually disable the same (changing from release to scheduled in SM37).

Regards,

Vishal

[chandan_praharaj]

Hi All,

Can you please help me understanding the use of

BTCTRNS1 and BTCTRNS2 in process chain scheduling and de-scheduling. As if we say the

BTCTRNS1 will suspend all the job which are released then what about the job which are still not released. Is that means that those job will run as usual. If no shall we good to use these TWO program in our production system for de-scheduling and scheduling of Process chain. As scheduling and de-scheduling huge number of PC is really time taking.

Any quick answer on this will be appreciated.

Thank you in advance.

Kind Regards,

Chandan Praharaj.

[benoit-schmid]

Hello,

Jobs that are not released won't execute.

Therefore after BTCTRNS1 executed, no job should start.

Why are you speaking about scheduling PC?

You are descheduling jobs not PCs.

Regards,

[Former Member]

Hello Benoît,

This is my personal experience that all jobs which are active at the time of system shut down gets canceled and the b/g jobs which are scheduled during the maintenance window will be queued and gets started as soon as the SAP system starts according to availability of b/g work processes.

So its better to set "No Start after or suspend the B/G jobs for the maintenance widow.

Thanks,

Vishal

[gurbirbhatia]

HI

I agree with Vishal, apart from this, you need to monitor what kind of jobs are running in the background, if all are default i.e administrative jobs than there is no harm but if these are heavy SAP functional reports and multiple b/g reports run at same time( immediately when SAP got started) then it may hamper the performance of SAP.

better to set No Start After

Study BTCTRNS2 before executing

Gurbir

[Former Member]

Hi Gurbir,

To think this is load specific is incorrect! Support packs can change the reports used by administration jobs. So you should suspend them as well. BTCTRNS1 would suspend everything except RDDIMPDP which is used to trigger import and subsequent jobs used for method execution,conversion etc.

Regards.

Ruchit.

[Former Member]

Hi,

May be you can suspend all the background jobs before stopping SAP using BTCTRNS1 and again release all the jobs after starting SAP using BTCTRNS2.

Thanks,

Ravi

[benoit-schmid]

Hello Ravindra,

Thanks for the report.

Would you also know the answer to my original question?

Thanks in advance for your answers.