Re: Monitor for existing job.

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
One problem I've had with many of these techniques is the following
scenario:

I have a job running which does an activity, sleeps for a set amount of
time, checks a data area or something to see if it should shut itself
down, if not it repeats the loop, otherwise - endpgm.

Sounds nice and orderly.  Backup starts and sets the dataarea to shutdown
the other program, waits until it ends, and then continues.  Don't want to
do an endjob because it might be in a critical update.  Problem arises
when, somehow or another, there is a job waiting on the job queue.  First
one ends, second one kicks in, and then the backup is waiting again.
Probably what I should do is have the backup update the dataarea again
with the shutdown command every time it loops.  And after x loops, notify
someone.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin