The note Andy refers to (ie search "idle wait 100") recommends using
accounting log records to get accurate information.
I agree fully.  In building Servergraph, we tried many different ways to get
session information, and the only one that was consistently accurate was the
accounting log.

--------------------
Lindsay Morris
CEO, TSMworks
Tel. 1-859-539-9900
lind...@tsmworks.com


On Wed, Jan 13, 2010 at 8:13 AM, Andrew Raibeck <stor...@us.ibm.com> wrote:

> Hi Keith,
>
> Go to the link in sig and do a search on
>
>   idle wait 100
>
> and you should get a hit relevant to the issue you describe.
>
> Best regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Product Development
> Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Hartford/i...@ibmus
> Internet e-mail: stor...@us.ibm.com
>
> IBM Tivoli Storage Manager support web page:
>
> http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
>
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 01/12/2010
> 10:44:46 AM:
>
> > [image removed]
> >
> > pct idle wait > 100
> >
> > Keith Arbogast
> >
> > to:
> >
> > ADSM-L
> >
> > 01/12/2010 10:46 AM
> >
> > Sent by:
> >
> > "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
> >
> > Please respond to "ADSM: Dist Stor Manager"
> >
> > What does it mean when Pct. Idle Wait and Pct. Comm Wait are large
> > numbers greater than 100 as in the node below?  The TSM server is at
> > version 5.5.2.1, running on RHEL.
> > Thank you,
> > Keith Arbogast
> >
> > tsm: TSMIN01>q node bl-sdd-internal f=d
> > Node Name: BL-SDD-INTERNAL
> >                        Platform: WinNT
> >                 Client OS Level: 6.00
> >                  Client Version: Version 5, release 5, level 2.0
> >       .............................................
> >                            Compression: Client
> >        ..........................................
> > Last Communication Method Used: Tcp/Ip
> >     Bytes Received Last Session: 55,104.51 M
> >         Bytes Sent Last Session: 150.61 M
> >        Duration of Last Session: 0.05
> >     Pct. Idle Wait Last Session: 8,565,047.92
> >    Pct. Comm. Wait Last Session: 67,277,175.00
> >    Pct. Media Wait Last Session: 0.00
>

Reply via email to