Re: Monitor for existing job.

["Dan Bale" <dbale@xxxxxxxxx>]

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