We have A LOT of jobs scheduled through the Advanced Job Scheduler (wrkjobjs). We have to do some system maintenance and need to prevent the scheduled jobs from starting while we perform the maintenance. In the past, the operator has gone through the entire list of jobs on the scheduler and put all the jobs on hold individually that might start during that time frame. In addition to being time consuming it is also subject to human error (missed holds or releases).
I beleive there is a command that can hold the entire job scheduler, but am unsure of the specifics. Does anyone know of such a command and how it works?
And if there is a command to hold the job scheduler, how is it restarted? When it is restarted, do the jobs that were scheduled to run while it was on hold start automatically, or must they be submitted manually?
November 12, 2009 3:32 PM
November 13, 2009 6:50 AM