Re: Monitor for existing job.

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Dan,

If you were to use the data area method, could you call a program that
accessed that data area, while it was locked by another job?  Yes.  You
would only have problems when the new program tried to lock the data area.

Same thing as the .dtaara object, is the .pgm object.  The lock would only
be checked on the .pgm object when you tried to allocate it in the new
program.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Dan Bale" <dbale@samsa.com>
Sent by: midrange-l-admin@midrange.com
04/09/2002 01:20 PM
Please respond to midrange-l


        To:     <midrange-l@midrange.com>
        cc:
        Fax to:
        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.