|
Thanks for the update. I will have to remember this one. Never even dawned on me to check a system attribute. Chris Bipes Information Services Director CrossCheck, Inc. -----Original Message----- Folks: This problem has been resolved! Turns out the customer had change the "TCP closed timewait timeout (TCPCLOTIMO)" value to zero (in CHGTCPA). The default, I believe, is 120 (at least that's what it is on two of our systems here). My theory is that, since this value was 0, the close signal was getting to my application before the data was (although I'm not sure why). When we had the customer change this value to 120 ... the application worked perfectly.
As an Amazon Associate we earn from qualifying purchases.
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.