Re: Monitor for existing job.

[Vernon Hamberg <vhamberg@xxxxxxxxx>]

In the API you can specify onlya part of the job spec - e.g., name only.
It'll return all the jobs of that name. Similar to WRKJOB JOBNAME, which
will give you a select list.

Preventing another job with same name could be a problem, if you allow
users to submit jobs. This is a security issue to manage.

At 11:53 AM 4/9/02 -0500, you wrote:
>From: Hall, Philip <phall@spss.com>
> > > 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.
> >
>
>How would you specify such a job? 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.
>I guess I may be taking too broad a view of what a job is. Maybe
>people running a production system manage things by naming
>convention: they would never dream about submitting jobs with
>the same name doing different things...
>
>
>_______________________________________________
>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.