If you look up the Error -50, and Error 32, all it means is "Tcp/ip
communications failed".
There is nothing in these errors that explains why.

Check your server activity log.
At exactly the time these errors occurred on the client, there will be an
error in the server log.

Look up the error number for the server end.

One of the most common errors is that the server terminated the session with
the client because the client has not responded in a long time.  If that is
the case, increase the COMMTIMEOUT parm on the server end to at least 300
instead of the default.

Hope this helps.
***************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
***************************************************************




> -----Original Message-----
> From: Stefan Wolf [SMTP:s.wolf AT HZD.HESSEN DOT DE]
> Sent: Monday, February 22, 1999 5:11 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      TcpFlush: Error 32
>
> Hi,
> does anybody know what these errors mean:
>
> 20.02.1999 05:21:52 TcpFlush: Error 32 sending data on Tcp/Ip socket 5.
> 20.02.1999 05:21:52 sessRecvVerb: Error -50 from call to 'readRtn'.
> 20.02.1999 05:21:52 TcpFlush: Error 32 sending data on Tcp/Ip socket 5.
>
> (Server: Version 2 on MVS, Client: Version 3 on HP-UX)
> These errors always occur at the end of a backup session.
> S. Wolf
>
> +++++++++++++++++++++++++++++++++++++++++
> EMail:  [mailto:S.Wolf AT hzd.hessen DOT de]
> +++++++++++++++++++++++++++++++++++++++++