Re: Passing ownership of object locks?

[peteh@xxxxxxxxxxxxxxxx (Pete Hall)]

In message <3486DB05.1AA3218D@midas-kapiti.com>, From Lo 
<raikovl1@midas-kapiti.com>, the following was written:
> Don't think it will work. If somebody has been sitting queued for this
> dtaara lock all along, then whatever you do with messaging, this
> someobody will be the first to get the lock when the holder releases 
> it.

Maybe you could use a variation on RTS/CTS logic:

Interactive tries to lock object a with no wait
    if unsuccessful, issues a message quits
Interactive tries to lock object b with no wait
    if unsuccessful, unlocks a, issues a message and quits
Interactive submits batch job and unlocks b
batch attempts to lock object b and waits until successful
interactive attempts to lock object b with no wait
    if successful, unlocks b, does a short wait and retries
    if unsuccessful, unlocks object a and quits - this is normal exit
batch attempts to lock object a and waits until successful
    batch runs
    at completion, unlocks b then a and quits

Any way you do it, the interactive job must remain active until the
batch job has instantiated itself.

hth
Pete


--
 - Pete Hall peteh@earth.inwave.com
http://www.inwave.com/~peteh/

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---