RE: [MI400] Sharing *EXCL locks (Was: Displaying objects in other job's QTEMP library)

["jt" <jt@xxxxxx>]

| -----Original Message-----
| Behalf Of Steve Richter

|
| Win32 does not think the idea of multiple threads sharing a lock is a far
| fetched idea.  It provides a series of locking and syncronizing
| primitives,
| the variable count semaphore being one of them.
|
| http://msdn.microsoft.com/library/en-us/dllproc/base/createsemapho
| re.asp?fra
| me=true
|
| The iSeries could improve on this even further by providing permanent,
| library resident, variable count semaphore objects.

Didn't get to scan article, but I never learned the difference between a
semaphore and a mutex...  So I'm not able to comment intelligently on that
aspect.

But on the iSeries *EXCL means COMPLETELY exclusive, and there are other
lock-states available for sharing.  (Not commenting on whether these could
or should be improved, either way.)

I was looking for *EXCL but WITH specific exceptions allowed, but gather
only Rochester could accomplish this.