RE: TCP goes down

It should be very very rare that TCP goes down by itself.  I'd lean more
towards a network type of problem.

When you said it was went down last Friday did you check the status of
the QTCPIP job?  Or check it's job log?  

Assuming decent software currency I would look at outside influences but
perhaps the QTCPIP job could give you some information.

Michael Crump
 
Manager, Computing Services
Saint-Gobain Containers, Inc.
1509 S. Macedonia Ave.
Muncie, IN  47302
765.741.7696
765.741.7012 f 

Cluelessness
There are no stupid questions, but there are a LOT of inquisitive
idiots. 
This email and its attachments may be confidential and are intended
solely for the use of the individual to whom it is addressed. Any views
or opinions expressed are solely those of the author and do not
necessarily represent those of Saint-Gobain.  If it did it would be
folded, mutilated, watered down, politically corrected, and would show
up a week later if at all.  If you are not the intended recipient of
this email and its attachments, you must take no action based upon them,
nor must you copy or show them to anyone.
Please contact the sender if you believe you have received this email in
error.
 
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rowe, Sheri
Sent: Tuesday, January 09, 2007 11:36 AM
To: midrange-l@xxxxxxxxxxxx
Subject: TCP goes down

Has anyone had a problem with their TCP connection 'dropping'?  About 8
months ago, our overnight failed as the TCP on one of our iSeries went
'down'.  The system was up and I could sign on to the console fine but
not from a Client Access session.  Tried stopping and starting TCP (all
services) and varying off and on the line, but only an IPL could get the
communication between the iSeries and my network up.  

I contacted IBM who couldn't really help.  No entries in WRKPRB either.
I couldn't ping anything.

The history log had a bunch of entries to indicate the interactive
sessions and the connection to our other iSeries had terminated
TCP2617 TCP/IP connection to remote system 169.1.1.25 closed, reason
code 2. TCP2617 TCP/IP connection to remote system 169.1.1.25 closed,
reason code 3. CPF590A Session to device WT221S2 ended normally.   

It happened again this past Friday.  Does anyone know what is causing
this?  And/or how I can correct it once it does happen without an IPL?

Thanks for any words of wisdom.

Sheri Rowe
Timex Canada
Markham, Ontario