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


  1.  Home
  2. MIDRANGE-L
  3. April 2002

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.