RE: TCP interface problem

As I knew in my heart, but was hoping to avoid for at least awhile yet.  Oh 
well.  The issue wasn't so much the recoding, but the fact that the program 
sending the message only sends delimiters on certain records.  

I think the reason it worked on the old machine so well was that the old 
machine was slow and far enough behind as to have buffers full of data before 
it got around to calling RECV.

On the new machine just for fun I did do a GETSOCKOPT on the SO_RCVBUF.  It 
came back plenty big (8K).

Thank you to everyone that replied.

Regards,
Rich

-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of Tim McCarthy
Sent: Saturday, August 07, 1999 1:38 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: TCP interface problem


If your sockets program is expecting to always receive complete
"records" on a read then you may be asking for trouble. There is no
guarantee that a packet sent always equals a packet received. You really
need to recode the read and treat it as a stream of data rather than a
fixed length entity - and if the records are delimited by say CR/LF's
then you need to parse it out - otherwise changes to your network
hardware/topology may eventually get you.

> -----Original Message-----
> From: Rich Duzenbury [SMTP:rduz@aros.net]
> Sent: Friday, August 06, 1999 5:09 PM
> To:   midrange-l@midrange.com
> Subject:      TCP interface problem
> 
> Hello midrangers,
> 
> I have a TCP socket interface giving me fits today.  We are trying to
> move it from a V3R2 machine to a V4R3 machine with little success.
> 
> Records longer than 536 appear to be truncated.  I notice that when I
> check the TCP connection status on the new machine (Netstat, option
> 3), it happens to report 'Maximum segment size: 536'.
> 
> The old machine reports 'Maximum segment size: 1452'.
> 
> How can I convince the new system to allow the larger segment size
> (Assuming this is the real problem).
> 
> This program does not appear to use any type of SETSOCKOPT calls, btw.
> 
> Thank you.
> 
> Regards,
> Rich
> 
> +---
> | 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:
> david@midrange.com
> +---
+---
| 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: david@midrange.com
+---

+---
| 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: david@midrange.com
+---