-BALANAND- Session 2,763 is the Producer session which remains in an Idlewait state because it obtains a list of file information from the TSM server for the files that have previously been backed up for this client and places them in memory on the client machine. It places this list of files in memory for those items that need to be sent to the TSM server and for existing files, the include/exclude list is also checked. It remains in this state until it sends backup statistics to server letting the user know whether or not it was successful or a failure.
Session 2,764 is the Consumer session which fluctuates between each state that sends the files to the TSM server for backup or to be marked inactive if they no longer exist on the client machine. Regards, Demetrius Malbrough UNIX/TSM Administrator -----Original Message----- From: PINNI, BALANAND (SBCSI) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 02, 2002 10:39 AM To: [EMAIL PROTECTED] Subject: WHy Idle wait keeps incrementing? Hi Happy new year to u all. Can u pl help me with this question. I have seen sometimes Idlewait time keeps incrementing in spite of client getting backed up. Thanks in advance. tsm: TSM>query session Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method State Time Sent Recvd Type ------ ------ ------ ------ ------- ------- ----- -------- -------------------- 2,763 Tcp/Ip IdleW 42.1 M 10.5 M 1.1 K Node WinNT Client1 2,764 Tcp/Ip RecvW 0 S 1.7 K 106.9 M Node WinNT Client1 Balanand
