How to stop jobs after a system copy

[Former Member]

Hi All,

After doing a system copy from the Production system to some test system, all the jobs that are supposed to be triggered in the production server will also trigger in the test system which is not good.

For example, If we have a payroll running every month. After i do a system copy the same payroll will also be triggered in the test server which is un acceptable.

How do we go about it and what are all the steps that we need to follow after a system copy?

Points will be rewarded.

Thanks

Vijay

[Former Member · Accepted solution]

Hi,

I beleive that there should be atleast one background work processes in an SAP system.

I see some background work processes running while starting an instance before their status change to WAIT. If I set the number of work processes to 0, then how will all these background processes run to start the server?

Thanks

Vijay

[MichaelTe · Accepted solution]

Hello Vijay,

you surely need background processes in a running system.

But you can start a SAP system without any background processes.

When the system is up you go to sm37 and delete (or de-release) all the jobs you don't need in the target system. Then set the number of batch processes to the amount you want and restart the system.

Alternatively you can prepare your source system accordingly with the SAP System Copy Guide - Section 3.2 Technical Preparations:

"Set all released jobs from Released to Scheduled:

Tools -> CCMS -> Background Processing -> Jobs - Overview and Administration (transaction SM37)

You also need to do this for jobs that must run periodically (see SAP Note 16083).

Select all jobs (include start after event) as follows:

Job -> Released -> Scheduled"

I think the best way for you is to read this guide!

Everything is explained very well there.

Goto:

https://service.sap.com/systemcopy

In the left tree select:

-> SAP Netweaver

-> SAP Netweaver in Detail

-> Software Life-Cycle Management

-> System Copy & Migration

-> Media Library

There are all the Guides for the current releases.

Regards, Michael

Message was edited by:

Michael Teubner

[Former Member]

hi ,

just run this report in se 38 btctrans it will stop all btc jobs .

[MichaelTe]

Hello,

I think this note could also help:

<a href="https://service.sap.com/sap/support/notes/37425">Note 37425 - Cancel job during upgrade</a>

Regards, Michael

[MichaelTe]

Hello Vijay,

I think the simpliest way is to assign no batch processes in the iinstance profile of the copied system.

Before the first start set the parameter:

rdisp/wp_no_btc = 0

in the instance profile.

Also have a look at the documentation for System Copy:

https://service.sap.com/operationsnw70

Goto the

--> Installation section on the left

--> Expand 2 - Installation - SAP NetWeaver Systems in the main frame

Regards, Michael

Message was edited by:

Michael Teubner