Ralph -

I take it, then, that this problem is being manifested by several/all
your clients? Try to narrow down.

What we're obviously missing is info from the server Activity Log -
the session peer. The errno 70 is "Connection reset by peer", where
we need to know why. If the server actually did it, then there should
be a reason, which could be something as simple as a too-small
timeout value. If the server didn't do it, then it's the networking
in between the two, which returns us to your changed server OS settings.

  Richard Sims

On May 2, 2006, at 9:14 AM, Levi, Ralph wrote:

Hi Richard,

We are running one 4.x client and all the others at 5.x.

Sorry I sent the "4" output.  Here is the 5.1.6 client output

04/27/06   23:49:39 ANS1810E TSM session has been reestablished.
04/28/06   02:37:24 sessSendVerb: Error sending Verb, rc: -50
04/28/06   02:37:24 ANS1809W Session is lost; initializing session
reopen procedure.
04/28/06   02:37:24 ANS1809W Session is lost; initializing session
reopen procedure.
04/28/06   02:37:39 ANS1810E TSM session has been reestablished.
04/28/06   02:38:31 ANS1005E TCP/IP read error on socket = 6, errno =
73, reason
 : 'A connection with a remote socket was reset by that socket.'.
04/28/06   02:38:31 ANS1809W Session is lost; initializing session
reopen procedure.