Hi, Richard. Well, I can't offer any help with the TPF users, but would running Rita in place of Pipe yield useful information for the large Rexx/Pipeline program. I would suspect that the majority of the CPU time consumed by the Rexx program is spent in the pipe commands.....
Good luck. DJ ----- Original Message ----- From: "Schuh, Richard" <[EMAIL PROTECTED]> To: [email protected] Subject: Re: Tracking Hot Spots Date: Wed, 1 Oct 2008 16:05:13 -0700 > 5 TPF users and 1 and CMS running a behemoth of a Rexx and > Pipelines program that drives the TPFs. > > Regards, > Richard Schuh > > > > > -----Original Message----- > > From: The IBM z/VM Operating System > > [mailto:[EMAIL PROTECTED] On Behalf Of Marcy > > Cortes Sent: Wednesday, October 01, 2008 3:54 PM > > To: [email protected] > > Subject: Re: Tracking Hot Spots > > > > What kind of virtual machine? > > For something like Websphere, you could use Introscope. > > Velocity will tell you percentage of time spent running > > / i/o wait / page wait if you want to know from a VM > > view. > > > > > > Marcy > > > > "This message may contain confidential and/or privileged > > information. If you are not the addressee or authorized > > to receive this for the addressee, you must not use, > > copy, disclose, or take any action based on this > > message or any information herein. If you have received > > this message in error, please advise the sender > > immediately by reply e-mail and delete this message. > > Thank you for your cooperation." > > > > > > ________________________________ > > > > From: The IBM z/VM Operating System > > [mailto:[EMAIL PROTECTED] On Behalf Of Schuh, > > Richard Sent: Wednesday, October 01, 2008 3:33 PM > > To: [email protected] > > Subject: [IBMVM] Tracking Hot Spots > > > > > > > > We have a situation where we need to discover what hot > > spots exist in specific virtual machines, where they > > are spending the most execution time, from outside the > > machines in question. Are there any tools that can do > > this type of monitoring? Turning on traces in the > > machines has been rejected because of the impact to the > > machines. > > Regards, > > Richard Schuh > >
