Robert A. Rosenberg wrote:
My error. I remembered that the ENQ had the ability to change the ENQ type but forgot that it was from SHARED to EXCLUSIVE (which is not as useful as from EXCLUSIVE to SHARED - if there is some purpose in allowing S->E, it should be in addition to not in lieu of E->S). In fact, I can not think of any situation where you'd want to be able to gain EXCLUSIVE access after having SHARED Access ...
Huh? You have this completely reveresed in your mind. Upgrading your ENQ from shared to exclusive is the common case and is a *required* function in order to maintain the integrity of the data. Going the other way would be far less common ... so uncommon, in fact, that OS/MVT/MVS never bothered to create a service for it! There's just no need. If you want to downgrade from exclusive to shared, you simply DEQ and re-ENQ with shared scope.
-- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
