Planning for unplanned downtime for Redwood Jobs

[Former Member]

Hi Team,

How can we manage / plan for an unplanned downtime, so that the already scheduled SAP Jobs do not get triggered and when the system is made up, the jobs should not start running.

I also want the plan as to how to go ahead after the system is up again, ( what to do before we start the process servers again and queue is released ) .

Regards

Madhu

[Former Member]

Hello Madhu,

Si tus trabajos tienen una ventana de tiempo estos solo se ejecutaran en dicha ventana si tu necesidad es ejecutarlo una vez que el sistema este arriba puedes ejecutar en ese momento dicha cadena o job por separado y dejar la configuración de la ventana para que al dia siguiente se ejecute en automatico.

  Espero te sirva mi aportación

Moises Hamud

[former_member72868]

Hello Madhu,

If you have some jobs where it is important that the job runs during a specific time and if the system is unavailable during that time or the job is unable to run for whatever reason then the job should not run later - Then you should schedule the job with a "TIME WINDOW" that is only open during the time when you want the job to run.

Note that it is also possible to add a time window to a queue or a process server.

Rgds, David

[abhishek_singh29]

Hi,

Please follow the below procedure:

If you are planning to down the SAP system:

1. Hold the queue and down the process servers
2. Lock the RFC user in SAP (so RFC user will not able to communicate with CPS, when SAP system will up)
3. You can also hold the jobs in case you have less number of jobs.

If SAP system was down unexpected:

1. Hold the queue and process server (probably it will be down)
2. Hold the jobs in CPS.
3. When the system will be up, probably your jobs were failed. Re run the particular and restart the chain.
4. In some case, Jobs were in waiting status and don’t goes into any status (due to unexpected shutdown). Move the Particular the Job definition/Chain to unknown status (following the Job ID). Chain will be restart automatically.

If CPS down unexpectedly:

1. Lock the RFC user in SAP. And do the changes when system will be up.

What to do before we start the process servers again and queue is released - If you didn't locked the user, queue and process server will start automatically.

Others depend on your scheduling /functional module environment which you need to take care.

Regards,

Abhishek

[Former Member]

Hi Abhishek,

Thanks for the suggestions. As of now, Our system is down and it was an unplanned down so we could not take any precautions, like holding the queues. We have already locked the RFC user in the SAP systems so that the Jobs do not run as soon as the Redwood is up.

Now what else do we need to do so that the jobs those were scheduled during the time the system is down, would not run and the next schedule for all the jobs should be as per the normal schedule time. To make it clear, The daily Job that is scheduled for today( say @10AM )when the system get down, should not run when the system gets up @ 1PM. and the next schedule instance for this job should be @10Am the next day.

[abhishek_singh29]

Hi Madhu,

Yes, When the system will be up and you release the job..it will get running. In this case, you can choose the below 2 things:

1. Temp/Instant Solutions: If you have locked the RFC..go and hold the all jobs and release the RFC user. Go to edit to particular job and move to the next occurrence.

PS: You Sould select the "JOB GROUP" Instead of the particular job.

2. Per Soultion: While creating the Job Chain/Def.. please select teh OVERDUE option the job chain(it will be in JOB tab, when you go to the edit option of JC/JD). Give the status - Like Overdue/cancelling. (So when the job will fail the time window will be goes in OVERDUE/CANCELLING status and next job be schedule automatically and this is option is good as on daily basis you can get clear picture of Overdue job)

Please let me know if you required more further details. I looked it a bit late

Regards,

Abhishek