RE: Passing ownership of object locks?

[Bruce Guetzkow <bguetzkow@xxxxxxxxxxxxx>]

Stephen:

Perhaps placing the name of the job being submitted into the data area could 
add a second level of security.  In this way, not only does a program need to 
lock the data queue, but it must check a value in it to see if it is "allowed" 
to lock it.  If this value is "blank" or contains the name of the job trying to 
lock the data area, continue processing, then clear the job name from the data 
area.  If the value has the name of a different job, release the lock and 
terminate processing.

Just one of many possible solutions...hth,
Bruce Guetzkow
Team Coordinator, Applications Development
Highsmith Inc.
W5527 Highway 106 P.O. Box 800
Fort Atkinson, WI  53538-0800
Tel (920) 563-9571  Fax (920) 563-7395
EMAIL bguetzkow@highsmith.com


----------
From:   Stephen Hunt[SMTP:deptit@harvestime.co.uk]
Sent:   Wednesday, December 03, 1997 8:17 AM
To:     MIDRANGE-L@midrange.com
Subject:        Passing ownership of object locks?

Can I transfer the ownership of an object lock to another program ?

The program I am working on does the following :-

        1. Locks a data area (so no one elses can run this job).
        2. Performs some data validation.
        3. Submits another job to QBATCH to perform some processing.
        4. Releases the data area lock.

However, the lock on the data area needs to be maintained until the batch
job has finished.  Even though the submitted job re-locks the data area,
this action could be delayed if it gets queued up behind other jobs, and
someone else could obtain the lock on the data area.

Can anyone help or perhaps suggest a better method ?

TIA

Stephen Hunt
Technical Systems Manager
Harvestime Limited

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