Ike,

Perform a search on www.adsm.org for "errno = 73" and you will finds tons of
info about those types of messages. This normally occurs when the connection
is reset by peer and most of the time the TSM actlog shows more detailed
information about what really happened.

Regards,

Demetrius

-----Original Message-----
From: Hunley, Ike [mailto:Ike.Hunley AT BCBSFL DOT COM]
Sent: Thursday, August 29, 2002 8:16 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: sessRecvVerb: Error -50 from call to 'readRtn'.


Hi *SM-ers!


Has anyone seen this one?

I have a customer issuing the following command...

db2 backup database ngbuprd online use tsm open 4 sessions with 4
buffers buffer 2048 parallelism 12 without prompting;

Here's the environment...
                     Node Name: ROC08M80P011
                      Platform: DB2/6000
               Client OS Level: 4.3
                Client Version: Version 4, Release 1, Level 2.14
Session established with server ADSM: MVS
  Server Version 4, Release 2, Level 2.0

he gets the following...

08/29/02   05:41:39 sessRecvVerb: Error -50 from call to 'readRtn'.
08/29/02   05:41:39 TcpRead(): recv(): errno = 73
08/29/02   05:41:39 TcpRead(): recv(): errno = 73
08/29/02   05:41:39 sessRecvVerb: Error -50 from call to 'readRtn'.
08/29/02   05:41:39 sessRecvVerb: Error -50 from call to 'readRtn'.

I've logged into this server, and ping to it and from it.  I've also checked
with the IP folks and they see no problems.

Where can I look for more problem determination info?

I appreciate any assistance.


Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect the
views of Blue Cross Blue Shield of Florida, Inc.