|
>We have a sockets application on the >AS/400 that is talking to a PC based >application running under Windows sockets. This is important because Windows is ASCII... >Our interface is working well, except for >one small problem. The SocketData field >that holds the data portion of the packet >is defined as a variable length field and >we specify the length (%len) of the data >string on the send function, but no matter >what we do, we can't get the program to >send the actual length of data down >the line. The customer is getting our data >string followed by a bunch of "@" (nulls) >out to the end of the transmission. Follow the data from birth to death and see where the corruption occurs. Especially check out the code that does the EBCDIC to ASCII translation. See if you are: a) clearing the target field before translating b) translating only %len bytes Buck Calabro CommSoft, Albany, NY
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.