|
Hi Mike, > I am having problems converting ASCII to EBCDIC. I am using the rexec API > to process a program and receive parameters back from the program. When I > receive the parameters back (from the stdin stream), the results are in > ASCII. I am using the QDCXLATE call to convert ASCII to EBCDIC. The table > I am using is QEBCDIC. I prefer QTCPEBC, and QTCPASC, but the "correct" table will probably depend on your country/language. > The translations are not occurring correctly. For example.... the data to > be translated is "test 1". The data is translated into "TEST". Another > line of data "TEST 2" is translated into "TEST". I'm not clear on what you're saying here. Are you saying that it's converting "test" into "TEST"? (in order words, converting the word to all-uppercase?) If so, I know that's not the normal behavior of QEBCDIC, so I'm a bit confused. Or, are you saying that it's stripping off the number? Like converting "TEST 1" to "TEST"? If so, that again isn't the behavior ot QDCXLATE. It's more likely that you're reading the data faster than the network can transport it, and therefore you're getting partial data returned. > I was going to use the API IConv, but the examples are not quite clear. Have you checked the archives for examples of iconv()? I know that it has been posted before. If not, let me know and I'll post a new example. But, if the problem is that the data is getting chopped off, iconv() isn't going to solve the problem.
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.