- Is this is scheduled from Redwood? or is intercepted from SAP?
- Did some one schedule it with submit frame (frequency) of 20 seconds? or
- is the restart behavior set on the job that is causing it?
You don't need to script anything.
- First recommendation is to hold the queue in which this job is running. This will put the next run of the job into Queue held status.
- If your answer for Q2. above is yes, then right click and select "cancel" option
- If your answer for Q3 above is yes, then run the System_ForceJobStatusUnknown and provide the job id of the job in Queue held status. This will force the job to unknown status.
- Edit the job definition and modify the restart behaviour to default behviour.
thanks
Nanda