× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Make sure your switches/hubs the iSeries connects to are in the same 
UPS as the iSeries. That way you can remove power outages from the 
list of possible problems. The system hates when that first connection
from the system is lost. Have seen shops where the iSeries gets a big 
UPS plus generator & the netwotking hardware is plugged to the wall or
a $59 APC unit that lasts a couple minutes....
I also set the recovery limits on the ethernet line description by 
setting values to 99 times in 0 minutes (sort of an infinite retry). 
This is extremely resource intensive, but if no network connect then 
your 
users aren't doing anything but waiting for the fix. As soon as 
connection restored, 
will come back online. The default 2 times in 5 minutes gives you a 
halt
to answer if no connection within the 5 minutes. This way when the 
network guys
replace a switch the system reconnects without intervention.
jim franz

----- Original Message -----
From: "Rowe, Sheri" <srowe@xxxxxxxxx>
Date: Tuesday, January 9, 2007 11:37 am
Subject: TCP goes down
To: midrange-l@xxxxxxxxxxxx

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 
(allservices) 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

-- 
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.