Re: Monitor for existing job.

I guess my confusion is related to the word "job".
You are really just talking about a command or a
program. Not a job as such.

----- Original Message -----
From: Hall, Philip <phall@spss.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, April 09, 2002 12:08 PM
Subject: RE: Monitor for existing job.


> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> --
> [ Picked text/plain from multipart/alternative ]
> > And how would you prevent another
> > one with the same simple name but
> > using completely different resources
> > to run or maybe it would be ok to run
> > this as there is no conflict.
>
> This brings us back full circle to what Mike wanted, a way to ensure that
if
> the job was already running that a duplicate couldn't be run at the same
> time.
>
> The various answers all described that the code in the job create some kind
> of semaphore/mutex/flag that is only live while the job runs - if a second
> copy tries to run, it will see the 'in-use' and quit.
>
> Lots of jobs do this kind of thing (sometimes explicitly, sometimes not),
on
> many OS's.
>
> --phil
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>