Michael, > I have a vendor that is suggesting I change the TCPIP keepalive value from 120 > to 2 minutes so that their application can discover and recover from a > comm./server failure better. It is a TCPIP connection to an NT system and the > software does not recover gracefully whenever the NT system is rebooted (oh that > never happens)..... Some times this works OK, but if you have real slow comms links to the 400, these can be dropped if the 2mins timeout is reached. The vendor should be able to override the keep alive value from within their code using the setsockopt() function, leaving the 120min default how it is for everything else, but having 2mins just for their application on the AS/400. One of the things we've found with NT (and is probably why they are suggesting this) is that in some situations, even when the NT box is turned off, the AS/400 side of the connection is not informed (i.e. the socket functions don't return SOCKET_ERROR) and the AS/400 server code has to wait for the keepalive to kick in and then the functions return SOCKET_ERROR. --phil +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.