Re: Hold ALL jobq's

James / Tom -

I'm writing a UPS monitor program. If I can hold the job queues in the UPS
monitor program before I shutdown the system (because the UPS is dying), I
don' have to change our start up program. The current startup program is
used, more often than not, after a normal, intentional shutdown, so it does
start subsystems needed for normal work. If I had to shutdown the system
with the UPS monitor program, I might have serveral jobs in a job queue
(many of our job queues are single threaded) that shouldn't run because Job1
was running at the time of shutdown and those jobs depend on files created
by Job1. Therefore, I prefer to hold job queues rather than rework the
startup program.

Thanks,

Steve


"Tom Liotta" <qsrvbas@xxxxxxxxxxxx> wrote in message
news:mailman.18969.1248209299.23468.midrange-l@xxxxxxxxxxxxxxx

Salter, James wrote:

If the needed jobqs all are in a particular subsystem, then one option
would be to make sure that the subsystem isn't restarted.

Another thought would be to handle things in the startup program prior
to starting up the system. Do what needs to be done first in the
startup program, then bring the system up.

This seems to me to point to the real question -- Why start subsystems if
jobs shouldn't be running in them? If a subsystem hasn't been started,
there's no need to hold its jobqs. Only start subsystems that need to do
work and the problem doesn't exist.b

Tom Liotta

from: "Steve McKay" <steve.mckay@xxxxxxxxxxx>
subject: Hold ALL jobq's

I'm writing a UPS monitor program and would like to hold all job queues
before I shutdown the system so that jobs do not automatically start
running when the system is restarted. Does anyone know of a command or
program
that will hold all job queues without my having to create a list of job
queues and read through the list.

--
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone 253-872-7788 x313
253-479-1416
Fax 253-872-7904
http://www.powertech.com