We see that all the time, and I don't think it's necessarily a problem...
The "idle wait" you see from Q session is the state of things from the
SERVERS point of view.

It just means the client hasn't started another transaction yet.

The client may be noodling through the filesystem looking for things to back
up (remember it collects a bunch of small files into aggregates), or the
client machine may be doing something else altogether, like application
processing.
Compression mike also make it take a bit longer.

I wouldn't worry about it unless you are timing the sending of a big DB from
one of the TDP's -



-----Original Message-----
From: Andy Carlson [mailto:andyc AT ANDYC.CARENET DOT ORG]
Sent: Wednesday, January 21, 2004 11:10 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Idle Waits


What are some of the more common Idle Wait problems?  We have a few
(about 5) nodes that back up into the daytime.  Either they have long
idle wait times, or they have numerous short idle waits (like say 10
seconds or so).  I am told the NIC cards have been checked.  Thanks for
any information.  Oh, the clients are Windows 2000, clients are 5.2.0.3.
The TSM server si 5.2.1.1.


Andy Carlson                                    |\      _,,,---,,_
Senior Technical Specialist               ZZZzz /,`.-'`'    -.  ;-;;,_
BJC Health Care                                |,4-  ) )-,_. ,\ (  `'-'
St. Louis, Missouri                           '---''(_/--'  `-'\_)
Cat Pics: http://andyc.dyndns.org/animal.html