----------------------<snip>------------------------
Thank you Birger for the link to the new z/OS Hot Topics newsletter.
I have a question concerning the byte range lock manager article.
After reading about the various evolutions of the BRLM (single
environment, shared, recovery considerations within a sysplex), I was
wondering why the locking mechanism was redeveloped! It seems to me that
GRS is the perfect server (or manager - if we can call it that) to
maintain any locks that the z/OS UNIX environment needs to serialize its
resources.
Could someone maybe fill me in on what I am obviously missing!
Thanks
-----------------------------<unsnip>---------------------------
One of the overriding considerations of using a LOCK, as opposed to
using GRS, is pure raw speed. For something that may need to be "LOCK"ed
for a short period but perhaps thousands of times, like the storage
management blocks within a particular address space, GRS would be
woefully inadequate. Similarly, for something that needs to be
serialized only within a single image, again, GRS can be very
slooooooow. Consequently, developing a LOCK protocol for a well-defined
set of one image-only resources can save a great deal of time and
contribute to overall efficiency.
----------------------------------------------------------------------
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
