On Thursday, 03/13/2008 at 05:54 EDT, barton <[EMAIL PROTECTED]> wrote: > Wait a minute here, hold your horses or whatever. MONWRITE is NOT an ibm
> product, it's a "Free" tool just like CMS COPY, or DDR. MONWRITE is a utility documented in the Chapter 3 of the CP Commands and Utilities reference. MONWRITE's [documented] One True Purpose is to store monitor records on disk. All of them. Every record that gets generated is saved by MONWRITE. > So this is nothing personal, Alan did say he doesn't know > enough about the issue to agree or disagree. Personally, I don't > post from that position (really, nothing personal Alan). If your REAL concern is that some of the data generated by the monitor (and, hence, written by MONWRITE) is not needed to manage performance, I will not dispute it. Your experience with the content of the monitor obviously exceeds mine. It is *this* underlying issue that I don't know enough about. Maybe it is important to know that I/O is NOT being done to certain devices in the configuration? So that you know they were not accidentally excluded from data collection? But I *am* certain about the *purpose* of MONWRITE. (I don't want MONWRITE to get a bad rap because of something the monitor is doing.) > But they are not state of the art and people do pay real money to > replace these "freebies". I would like to take this opportunity to reinforce Barton's point that MONWRITE is not a performance management tool (product or not). It is a program to movesthe monitor data to disk. If you are looking for a way to manage the performance of the system, including keeping histories of past performance, consider investing in a performance management product. Such products have more sophisticated ways of collecting and managing monitor data. Alan Altmark z/VM Development IBM Endicott
