>I know I have seen similar reportings of this type of error, but I have not
>seen any comment on the reason for this type of error.
>
>Example:               (during scheduled nightly backup window we receive)
>     TcpFlush: Error 10054 sending data on Tcp/Ip socket 164.
>     sessSendVerb: Error sending Verb, rc: -50
>     TcpFlush: Error 10054 sending data on Tcp/Ip socket 164.
>     sessSendVerb: Error sending Verb, rc: -50
>     ANS1809E Session is lost;  initializing session reopen procedure
>     ANS1809E Session is lost;  initializing session reopen procedure
>     ANS1810E ADSM session has been reestablished.
>          (then this section of error messages will continue for a second
>socket number and so on until the
>          backup has completed or the backup window has expired......)
>
>This is happening on all our ADSM NT clients regardless of NT service pack
>installed.  The ADSM clients are at 3.1.0.1.  Our ADSM server is MVS at
>3.1.1.3.  Our network is an ATM backbone.
>
>To date we have decreased our COMMTIMEOUT to 30 minutes and this has reduce
>the number of clients failing because of timeout.
>
>Any help to identify the cause of this situation would be most
>appreciated......