RE: Monitor for existing job.

This would cause a problem if the job ends abnormally.

If I understand correctly, the purpose is to really check for an active
process rather than an active job per se.

I use the procedure of locking a data area. This has worked well for me for
years.

I put all of the data areas in one library, which does no need to be backed
up, since the data areas are created as needed.

Albert York



        -----Original Message-----
        From:   Wills, Mike N. (TC) [SMTP:MNWills@taylorcorp.com]
        Sent:   Tuesday, April 09, 2002 10:03 AM
        To:     'midrange-l@midrange.com'
        Subject:        RE: Monitor for existing job.

        Leif, What I am doing (forgot who suggested it) is to create a data
area. If
        there is a '1' in the data area, it is running, if there is a '0',
it isn't
        running.

        -----Original Message-----
        From: Leif Svalgaard [mailto:leif@attglobal.net]
        Sent: Tuesday, April 09, 2002 11:53 AM
        To: midrange-l@midrange.com
        Subject: Re: Monitor for existing job.


        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.
        _______________________________________________
        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.