on 08-31-2011 6:51 PM
Hi all, I would like to know if they are any ways to prevent a release job to run twice at the same time. For exemple, if I create a job to run every 5 minutes and the job did not finish after 5 minutes, the scheduler will start the same job agains. This situation causing us bad issues.
I double check the job start conditions in sm37 but I found nothing special.
Thanks for help
Hi Marc,
We use a workaround. We have asked our abap developpers to write a small utility report which checks if the job it is part of is already running and aborts the job if it is the case.
When we need a job which must absolutely run only once at the same time, we just add this utility as first step.
Regards,
Olivier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is not possbile using SM37 by default.
SAP Central process scheduling (Redwood CPS) has all these features.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the job is time triggered then I guess we cannot do anything. If the jos is taking more than 5 minutes, then simply change the periodicity. If it is event triggered then , check if we can control that event.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.