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



The line recovery is driven by the CMNRCYLMT configured for the line. If
those recovery limits are exceeded, recovery of the system objects waits
for a response to an operator message without regard to the physical
link status.

Something like this should do what you want: CHGLINETH CMNRCYLMT(14 1)

If I remember correctly this will tell the LIND to retry the connection
every 5 seconds for 14 tries, but since the time limit is 1 minute it
will reset the count after 12 tries, thus making it retry continously.

You should not have to restart TCPIP, but some application connections
may not reconnect even if the line does. Those may need to be stopped
and restarted on both the client and the host sides.

Regards,

Scott Ingvaldson
Senior IBM Support Specialist
Fiserv Midwest


-----Original Message-----
From: Gerald [mailto:gmagnuson@xxxxxxxxxxxxx]
Sent: Wednesday, April 09, 2008 9:58 AM
To: midrange-l@xxxxxxxxxxxx
Subject: TCP/IP how do you recover?


Is it "normal" that when a cable is unplugged, or switch has a problem,
or what ever..... when we get a TCP2613 (TCP/IP interface
192.168.xxx.xxx recovery pending) we have to ENDTCP. even if the
recovery at the line level is successful.
My goal is that when a "burp" happens, the auto-recovery process will
"re-try" the TCPIP servers, so I don't have to restart them......


Is there a TCP/IP setting to recover?


Thanks,
Gerald


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.