You could  try to set  the parameter "COMMTIMEOUT"
     to a number greater than 600 seconds. The "COMMTIMEOUT" is located
in
     the file "dsmserv.opt". That is located on the ADSM Server.

     You can try to increase this parameter to 1500 seconds and if it
still
     doesn't help, please try 3000 seconds and so on. The commtimeout
     parameter can go as high as 7200 seconds or even higher if
required.




> ----------
> From:         Madhu Gandhi[SMTP:madhug AT PRODIGY DOT NET]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Thursday, October 01, 1998 12:32 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      why tcp/ip failure - need help!!!
>
> Hi,
>  We use tcp/ip connection for  adsm backups.
>  We received a 'SEVERED connection' error today.
>  What could be causing this?
>  Last night's backup was 90% done when the failure happened.
>
> The following message was in dsmerror.log:
> TcpFlush: Error 32 sending data on Tcp/Ip socket 3
> sessSendVerb: Error sending Verb, rc:-50
> TcpFlush: Error 32 sending data onTcp/IP socket 3
> TcpFlush: Error 9 sending data on Tcp/IP socket 4294967295
> SessSend: Error sending verb, rc:-50
> ANS4017E Session Rejected: TCP/IP connection failure
>
> Any help will be appreciated
> Madhu Gandhi
> Prodigy Services, Inc
> Unix Systems Administrator
> madhug AT prodigy DOT net
> (o)914-448-1748
> pager: 914-972-7417
>