|
rob wrote:
I think you're right. I just didn't want to mess with that program. So I used the list jobs api.
Rob:Mark's general thought is the good direction. For thoughts on how it might someday be done, I might go for an additional refinement.
1. Receiver attempts *EXCL lock first. 2. If fails, then exit (or some other action). 3. Receiver then also does *SHRUPD. 4. Receiver DLCOBJs the initial *EXCL. 5. Receiver does normal work. 6. Receiver DLCOBJs *SHRUPD. 7. Exit or whatever.The point of doing *EXCL first could be to determine if another receiver job is already running or if some other job is trying trying to tell it to hold off or not start. And by doing the *SHRUPD before releasing the *EXCL, your receiver slips a second lock in place without opening a window for some other job.
Once your receiver is in its running state, any other job may attempt a *EXCL. It should fail, but no harm if it doesn't. A DLCOBJ can be done immediately after.
Tom Liotta
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
