Tony, Something else comes to mind. I recall measuring these some monitors and seeing CPU consumption affective. The REFRESH RATE may also force some sorting, XMS and other stuff to occur on every 20 seconds. Measure the delta changes on CPU TIME when you adjust the refresh rates. CPU consumption will should down within the address space with longer refresh rates.
Kevin -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Clark, Kevin Sent: Friday, April 27, 2007 9:28 AM To: [email protected] Subject: Re: Monitor refresh rates Tony, By REFRESH RATE, if you mean screen display updates than that would depend if you expected some significant changes to have occurred. I like to handle refresh rates as they relate to the sampling of the monitor. If the monitor is only collecting 2 to 5 samples during that 20 second period then many indicators may not have changed. Check those sampling (collection) rates. More samples on busy PROD LPARS, less on non busy TEST LPARS. Aligning these REFRESH RATES with a few WLM sampling periods would also be more informative and I would raise REFRESH RATE from 20 on test LPARS for sure. Kevin >>>>>>>> You Wrote I have 14 LPARs each with an Omegamon for MVS monitor running with a refresh rate of 20 seconds. Does anyone think that a bit quick? I was thinking a rate of 65 seconds would be more appropriate. >>>>>>>>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
