OMEGAMON XE has a client for Linux which is included in the OMEGAMON XE for z/VM and Linux product, or can be purchased separately. It includes process level data.
The CPU Timer based accounting is an improvement regardless of whether you use normalization or not. The old method not only had the potential for inflated values, but also was exposed to skews in different directions. Normalizing the old values was a clever way of dealing with the problem in the interim, but it did not solve all the problems. Hence, the need for the CPU timer approach. Thank you Martin. :-) It is true that looking at both the VM and Linux data is helpful. Two heads are better than one. Kevin, I believe you have the VM part working already. There's been discussion here about various VM based solutions for looking inside the guest. For your needs, particularly in short term, a lot of the Linux tools out there will work on z, and with the new CPU timer are accurate. Stay away from things like TOP that are noisy and just add overhead. I should also mention that I don't see Performance Toolkit's requirement to indicate which virtual machines you want detailed data on for historic reasons as a hinderance to the solution. Inconvenient perhaps, but not a show stopper. It might be the confusion that in the old RTM product you could only benchmark one virtual machine, where Performance Toolkit allows you to benchmark any number. Also, I believe with different uses of OMEGAMON XE you can set up historical collection as well. Unfortunately I don't know the details. I hope that helps. Bill Bitner ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
