× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



It is impossible to completely prevent the submission of a job of a given
job name, if someone has authorized access to SBMJOB. As you suggest, the
control is really in a program.

But in most situations that are reasonably controlled - users restricted
from command line, good menu-base for applications, etc. (yeah, yeah, all
the IP leakage is still a problem), then you only need to worry about your
rogue developers and operations folk.

At 12:20 PM 4/9/02 -0500, you wrote:
>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.
> >
>
>_______________________________________________
>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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.