Re: New TCP/IP error messages on V5R2

>I was wondering if there was a way to stop the message

chgtcpa  tcpcnnmsg(*none) will stop messages
to read the knowledgebase doc on this that explains what is going on (worth
reading)
http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037e/dc
e52e8dee822d1d86256d040064def4?OpenDocument&Highlight=0,tcp2617
jim

----- Original Message -----
From: <MWalter@xxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, July 16, 2003 3:02 PM
Subject: Re: New TCP/IP error messages on V5R2


>
> We got 'em too. I was wondering if there was a way to stop the message
from
> being sent. It's annoying to our operators.
>
> Thanks,
>
> Mark
>
> Mark D. Walter
> Senior Programmer/Analyst
> CCX, Inc.
> mwalter@xxxxxxxxxx
> http://www.ccxinc.com
>
>
>
>                     Jerome Draper
>                     <jdraper@xxxxxxxxxxxx        To:
midrange-l@xxxxxxxxxxxx
>                     m>                           cc:
>                     Sent by:                     Subject:     New TCP/IP
error messages on V5R2
>                     midrange-l-bounces@xx
>                     drange.com
>

>
>                     07/16/2003 02:57 PM
>                     Please respond to
>                     Midrange Systems
>                     Technical Discussion
>
>
>
>
>
>
> 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.
>
>
>
>
>
> _______________________________________________
> 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.
>
>