Re: Monitor for existing job.

["Carsten Flensburg" <flensburg@xxxxxxxxxx>]

Dan,

The lock as such does not prevent the program being called directly.

The idea is to always call the program through the CL-program that will
perform the check for an existing lock against the program.  Similar to the
"lock data area" approach - but instead of using yet another object I
decided that the program object itself would be just as good a lock target.
And the CL-program provides a generic solution - if there are no parameters
involved in the call.

Best regards,
Carsten Flensburg

----- Original Message -----
From: "Dan Bale" <dbale@samsa.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, April 09, 2002 8:20 PM
Subject: Re: Monitor for existing job.


Carsten, I just tried ALCOBJ *EXCL on an program object in one job and was
able to call it in another job.  Which was the gist of what your code in the
archive post was getting at.  Did I miss something else that your code was
doing?

In fact, when I do a WRKOBJLCK on that program, I see the job where I did
the ALCOBJ, but not the job that currently is running it.  I have never
understood this mystery.

I think that locking the data area is the easiest and most reliable way to
go.

- Dan Bale
offsite today
---------- Original Message ----------------------------------
From: "Carsten Flensburg" <flensburg@novasol.dk>
Reply-To: midrange-l@midrange.com
Date:  Tue, 9 Apr 2002 19:27:30 +0200

>And here's something along the same lines - using the program itself as
lock
>object - from the archives:
>http://archive.midrange.com/midrange-l/199911/msg01701.html
>
>Best regards,
>Carsten Flensburg
_______________________________________________
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.