any suggestions on this:
can i turn off scheduling temporarely for all schedules?
say there is a prob with some server or the wrong data has been loaded in the dwh…
dvh 
(BOB member since 2005-09-29)
You could just disable the Job Server in the CCM. This will stop them from accepting any further job request, Jobs will just queue up untill the Job Server is enabled again.
blair 
(BOB member since 2006-11-17)
i was hoping for a more ‘sophisticated’ way to solve this. what really would be handy is an active switch per schedule, like Data Integrator has.
anyway, thanks for the suggestion.
dvh (BOB member since 2005-09-29)
There is nothing unspohistacted about this - dont forget blair mentioned to disable the job server (which can be done in the CMC or CCM), he didnt say stop the job server. The latter would be unsophisticated as this would simply kill all jobs.
In other words - this is the active switch you are looking for in my opinion.
Orange (BOB member since 2006-09-18)
I am switching from XIR2 to XIR31 following QA testing, so I have a similar question. Essentially how do I avoid schedules coming from both systems. If I understand from this post, I would stop the job server on my live 2.1 system. I would run the import, including instances, to bring across the schedules, to the 3.1 system. The 3.1 system would then be immediately ready to start scheduling reports. I can then close off the 2.1 system.
If for any reason I needed to revert, how do I stop the reports in the 3.1 system? 3.1 doesn’t have an identifiable job server in the CMC.
twofivepie 
(BOB member since 2008-10-16)
Sounds like a fine plan. And in the CMC you should definitely see proper Job Servers which you can disable. But even better, in 3.1 you also have the Instance Manager (is what it’s called I believe) in the top right of the home screen in the CMC where you can pause all running/scheduled instances.
Orange (BOB member since 2006-09-18)