You are already having the value too high. Do not mess commtimeout with
idletimeout.
Commtimeout is for client-server conversation. In LAN environment default
value of 60 (seconds) ought to be more than enough. For WAN links it may
need to be increased but I will not go beyond 150-180 sec.
Idletimeout is for sessions doing nothing to be cancelled by the server.
For long running backups (several hours) the collector thread's session
might be cancelled by the server. Increase of this option's value to the
length of longest backup might be a workaround. But even for it the value
of 1500 (it is measured in minutes) is too high - more than 24 hours.

You are having some network problem and the best way ought to be
discussion with your network admin.

--> ... The most I have seen out here posted is the 1500 ...

Number 1500 gets too often in list postings but as default TSM server port
not as commtimeout option setting !?!

Zlatko Krastev
IT Consultant






"Anderson, Michael - HMIS" <Michael_Anderson AT HMIS DOT ORG>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
23.12.2002 21:33
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Comm timeout value


        As of right now the communications time out on my TSM server is
1500. I still get some time outs every so often, so
    I would like to increase it. The most I have seen out here posted is
the
1500, is there some formula for this, or is it hit and
   miss.  I am running TSM ver 4.2.3 on AIX 4.3.3. Any suggestions
appreciated

    Mike Anderson
    Michael_Anderson AT hmis DOT org


CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.