Bill Fairchild wrote: >The behavior of your systems that you described sounds as if you have a global >enqueue that is systems-wide rather than an enqueue that should only affect >one system. The source code snippet you posted shows what looks correct for a >local enqueue (within one system) rather than a global enqueue. You might >also investigate whether your source code matches the load module that is >executing.
Thanks. This is the same what my IBM rep told me. I will do dumps and check it. >The issuance of multiple START PENDING messages does not automatically mean >that there are performance problems anywhere. START PENDING means that some >shared DASD data set is either being very heavily used or is RESERVEd on one >system while another system is trying to do some kind of I/O to the same >device, and the second system might even be trying to access a different data >set from the one that the first system is using heavily or has reserved. I will have a second nice talk with my storage admin... I have moved my SMF dataset to a group volumes which are NOT duplicated at a remote site. That helped eliminate a lot of START PENDING during my SMF dumps. >There are many other messages or indicators that can be used to diagnose a >performance problem, but they do not automatically mean there is a problem. I really wish there are other messages/indicators... > There is no performance problem anywhere unless someone is complaining. Well, more than one complained... enough complaints so I can't ignore them at will... ;-D Thanks Bill, for your nice comments. It was very helpful! Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
