"Barbara Nitz" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > Hi Tom, > > thanks for your explanation. That was basically what I already knew and what WLM development told me in 5000 words or more. > > That product not only sets several timers per address space, they also pop all at the same time. (I looked at a system trace table of 1.5s length, and for this product there were about 450 timer pops in 0.010s, as indicated be the timer SRBs that got scheduled. There were also way too many EXT/CLKC interrupts in MVS storage management indicating that the default LE options the product comes with are a long way away from ideal. The list goes on. > > Fact is that I am stuck with a very bad PI (and I cannot really do anything about it in WLM), and when the fines are due to be paid (because we didn't deliver on time) or the customer complaints come in, it's my head that will roll (because I am responsible for the wlm policy). > > So there are definitely tasks that don't play by WLMs rules..... >
I see the problem and the consequences, but I think your conclusion and originally already the title are not and cannot be correct: it shouldn't matter to WLM whether tasks want to play by WLM's rules or not. WLM should manage the tasks, whether they want to play along or not. Where is the rule that I should not issue more van x timer pops in 10 msecs? The problem here is, that WLM is not capable of managing its children when they are a little more exotic than the usual kids in class. or at least, it is not capable of reporting meaningfully about them. E.g. if I organize 100 TSO users to repeatedly enter a transaction at the same time, I bet WLM will fully panic and report PI's in the 100's, although performance might be good. Kees. ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ********************************************************************** ---------------------------------------------------------------------- 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
