And yes, sometimes the values might seem WAY out of line but here is what
I've had to set mine at to get things to work.  But remember the idletimeout
has more to do with the brain-child client node rather than anything to do
with the tsm server. I've had to set the 240 minute idletimeout because of a
30 processor (non-IBM) cpu that sometimes "he has'em a hard time figure'n
out what he's supposed to do... poor baby..."  :-O


Server Option     Option Setting       Server Option     Option Setting
----------------- -------------------- -----------------
--------------------
--------------------
CommTimeOut       1,800                IdleTimeOut       240
CommTimeOut       1,800                IdleTimeOut       240


> ----------
> From:         Richard Sims[SMTP:rbs AT BU DOT EDU]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Friday, August 11, 2000 8:16 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Schedule Error
>
> >08/11/00   05:31:26  ANR0482W Session 5628 for node IBMS3 (AIX)
> >                     terminated - idle for more than 15 minutes.
>
> Just follow the advice in the messages manual to boost your server
> IDLETimeout value.  Make it substantial, as many longstanding clients
> spend a lot of time rummaging around in the file system looking for
> something new to back up.
>   Richard Sims, BU
>