RE: New TCP/IP error messages on V5R2

This knowledgebase document may help:

http://www-1.ibm.com/support/docview.wss?uid=nas1dce52e8dee822d1d86256d04006
4def4&rs=110

Hope this helps.  I just searched the knowledgebase with TCP2617.  We had
the same symptoms are the upgrade.

Thanks,
Bob Dobrowolski
Programmer/Analyst
Star Stainless Screw Co.
(973) 256-2300  x224
r.dobrowolski@xxxxxxxxxxxxxxxxx
USS Cole - Never Forgotten 12 OCT 2000


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Draper, Dale
Sent: Wednesday, July 16, 2003 15:07
To: 'Midrange Systems Technical Discussion'
Subject: RE: New TCP/IP error messages on V5R2



Yep, see these a lot now. Disconcerting, aren't they? They are always from
within our domain, so I assume most of them are C/A sessions that are closed
improperly.
We also lost contact with a printer because of rewiring, that one filled
many many screens with this message.

Copied message from 12:02:01 today in the qsysopr msgq that was cleared this
morning:

"TCP/IP connection to remote system 205.123.85.111 closed, reason code 3."


-----Original Message-----
From: Jerome Draper [mailto:jdraper@xxxxxxxxxxxxx]
Sent: Wednesday, July 16, 2003 11:58 AM
To: midrange-l@xxxxxxxxxxxx
Subject: New TCP/IP error messages on V5R2


Since going from V5R1 to V5R2 we have been getting these TCP/IP messages in
our
qsysopr msgq.  Anyone seen this before?  New tweak in V5R2?

Jerry

TCP/IP connection to remote system 172.16.16.28 closed, reason code 1.
TCP/IP connection to remote system 172.16.1.14 closed, reason code 2.
TCP/IP connection to remote system 172.16.1.31  closed, reason code 3.

                         Additional Message Information



 Message ID . . . . . . :   TCP2617       Severity . . . . . . . :   20

 Message type . . . . . :   Diagnostic

 Date sent  . . . . . . :   07/16/03      Time sent  . . . . . . :
10:44:53


 Message . . . . :   TCP/IP connection to remote system 172.16.1.31 closed,

   reason code 2.

 Cause . . . . . :   The TCP/IP connection to remote system 172.16.1.31 has

   been closed. The connection was closed for reason code 2.  Full
connection
   details for the closed connection include:

     - local IP address is 172.16.1.10

     - local port is 491

     - remote IP address is 172.16.1.31

     - remote port is 515

 Reason codes and their meanings follow:

     1 = TCP connection closed due to expiration of 10 minute Close Wait
timer.
     2 = TCP connection closed due to R2 retry threshold being run.

     3 = TCP connection closed due to keepalive timeout.

If TCPCNNMSG(*THRESHOLD) is defined for the Change TCP/IP Attributes
(CHGTCPA)
  command then there could be additional connections that have closed within

  the threshold window. The number of additional TCP connections that have

  closed is 0.

Recovery  . . . :   Informational message.



Jerome Draper, Trilobyte Software Systems
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.