Re: TCP2617 message

There is an APAR #SE07603 for this message, but there doesn't seem to be a PTF.

rob@xxxxxxxxx wrote:

> http://archive.midrange.com/midrange-l/index.htm
>
> search for TCP2617
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
> Dennis Munro <DMunro@xxxxxxxxxxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 09/29/2003 03:43 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
> To
> "Midrange List (E-mail)" <MIDRANGE-L@xxxxxxxxxxxx>
> cc
>
> Subject
> TCP2617 message
>
> This is from the QSYSOPR message queue for today on my laptop running CA
> dated 20021218 on an 820 running V5R2M0 - one cum behind.  When it occurs,
> my green screen session blanks out & I revert back to the sign on screen.
>
> This has been happening for some time but never like today & I can't
> relate
> if it has to do with the last cum install or group ptf install????
>
> TCP/IP connection to remote system 172.20.1.81 closed, reason code 2.
> TCP/IP connection to remote system 172.20.1.81 closed, reason code 3.
> TCP/IP connection to remote system 172.20.1.81 closed, reason code 2.
> TCP/IP connection to remote system 172.20.1.81 closed, reason code 3.
> TCP/IP connection to remote system 172.20.1.81 closed, reason code 2.
> TCP/IP connection to remote system 172.20.1.81 closed, reason code 3.
> TCP/IP connection to remote system 172.20.1.81 closed, reason code 2.
> TCP/IP connection to remote system 172.20.1.81 closed, reason code 3.
> TCP/IP connection to remote system 172.20.1.81 closed, reason code 2.
> TCP/IP connection to remote system 172.20.1.81 closed, reason code 3.
> TCP/IP connection to remote system 172.20.1.81 closed, reason code 2.
>
> Message ID . . . . . . :   TCP2617       Severity . . . . . . . :   20
>
> Message type . . . . . :   Diagnostic
>
> Date sent  . . . . . . :   09/29/03      Time sent  . . . . . . : 15:07:18
>
> Message . . . . :   TCP/IP connection to remote system 172.20.1.81 closed,
>
>    reason code 2.
>
>  Cause . . . . . :   The TCP/IP connection to remote system 172.20.1.81
> has
>
>    been closed. The connection was closed for reason code 2.  Full
> connection
>    details for the closed connection include:
>
>      - local IP address is 172.20.1.30
>
>      - local port is 23
>
>      - remote IP address is 172.20.1.81
>
>      - remote port is 1263
>
>  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.
>
> Looked at my TCP settings they refer to & they are set at the default
> settings.
>
> Anything else I should look at?
>
> Thanks - Dennis.
>
> Dennis Munro
>
> "I love deadlines.  I especially like the whooshing sound they make as
> they
> go flying by."  Dilbert's Words Of Wisdom:
>
> Badger Mining Corporation
> www.badgerminingcorp.com
> dmunro@xxxxxxxxxxxxxxxxxxxx
> (920) 361-2388
>
> The information contained in this e-mail message is confidential
> information
> intended only for the use of the individual or entity named above. If the
> reader of this message is not the intended recipient, or the employee or
> agent responsible to deliver it to the intended recipient, you are hereby
> notified that any dissemination, distribution or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, please immediately notify us by telephone, and
> return the original message to us at the below address via the U.S. Postal
> Service, and delete it from your computer.  Badger Mining Corporation P.O.
> Box 328  Berlin, WI 54923  920-361-2388
> _______________________________________________
> 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.
>
> _______________________________________________
> 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.