On 10/31/2011 10:10 AM, Mark Jacobs wrote:
We just started using the zOS Runtime Diagnostics under zOS 1.12 and while I understand most of what it's telling us, I don't fully understand what it's trying to tell me, or what I can do about it when it reports on a HIGH LOCAL LOCK SUSPENSION RATE.
Local lock suspension occurs when some executing code attempts to get the local lock (which is required for many services e.g., STORAGE) and another unit of work already has it. The requester is suspended until the lock is released by the other unit of work.
If the rate is high (above average), it usually means some code is doing significant processing with the local lock held. It's not necessarily 'wrong'. Such statistics are a 'heads up' for the programmer(s). Is it your code that's executing? Or someone elses?
Do you have 'Vsm UseZosV1R9Rules' coded in DIAGxx? Using the new rules can make STORAGE run faster, thus reducing local lock contention. YMMV.
-- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 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
