RE: Monitor for existing job.

Oooh - just had a thought - it DOES happen!

There is a job notification exit point - actually data queue - for job
start/stop events. You can setup the exit point so that an entry is place
on the queue every time a job is placed on any job queue. You'd have
another never-ending program that'd wait on this queue, then do something
appropriate for the first time this job name is used, something else if
it's used again, from wherever. You'd probably need to do a HOLD or
immediate END, with messages to the offending user, at least.

Whadya think, eh? Possibilities?

At 01:16 PM 4/9/02 -0500, you wrote:
>This is a multipart message in MIME format.
>--
>[ Picked text/plain from multipart/alternative ]
>You've received many excellent suggestions.  A simple one might be a
>single string job queue.
>
>Rob Berendt
>--
>"They that can give up essential liberty to obtain a little temporary
>safety deserve neither liberty nor safety."
>Benjamin Franklin
>
>
>
>
>"Wills, Mike N. (TC)" <MNWills@taylorcorp.com>
>Sent by: midrange-l-admin@midrange.com
>04/09/2002 11:52 AM
>Please respond to midrange-l
>
>
>         To:     "'midrange-l@midrange.com'" <midrange-l@midrange.com>
>         cc:
>         Fax to:
>         Subject:        RE: Monitor for existing job.
>
>
>This is a monitoring job that continuously runs. I want our start up
>program
>(which we run for backups) to automatically start it up if it is down, but
>I
>don't want many versions of it running at once.
>
>-----Original Message-----
>From: Hall, Philip [mailto:phall@spss.com]
>Sent: Tuesday, April 09, 2002 11:47 AM
>To: 'midrange-l@midrange.com'
>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 ]
>
>Leif,
>
> > what am I missing? jobs are UNIQUE on the system. The 26 character
>
>I think the poster was after a singleton job, i.e. there must be only one
>of
>these jobs running on the system at anytime, like inetd on Unix, because
>it's function (or resources) can not be shared or would cause a conflict.
>
>--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.
>_______________________________________________
>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.
>
>
>
>_______________________________________________
>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.