Re: Passing ownership of object locks?

Stephen Hunt wrote:

> <snip>
>
> It still think it would have been nice if IBM had provided a native
> IF-ACTIVE function such as is available on the S/36 and in the
> S/36-Environment.
>

I've always wondered why they didn't also.  I think it has something to do with
the timing of the test and a job could slip through.  If you wanted to take your
chances, you could write a callable program which executed a STRS36PRC to a
procedure which performed a IF ACTIVE and set a return code.

Although if I recall right, your situation had JOBA which held a lock, did a
SBMJOB and that job held a lock, but an IF ACTIVE still wouldn't keep anyone out
while the second job sat on the queue.  Which I think you also needed. Even if 
it
ran immediatly you would still have a time gap between SBMJOB and the second job
grabbing the lock.

Setting data areas is a pretty common way of job conflict control.  We've used 
it
with the added feature of tracking completed steps for restart capability.  If
the value should be blank at initial start the previous execution completed
normally. If not, like SEU, a screen can come up to ask if you want to recover
where you left off or start over again.

+---
| 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
+---