Re: Translating EBCDIC to ASCII

Alan

Those tables are probably the worst things to use for conversion. The recommended method is to use the iconv() api. QDCXLATE is essentially deprecated - still usable but nothing updated in centuries with it.

http://www.mcpressonline.com/index2.php?option=com_content&do_pdf=1&id=1552 is an article that discusses this. A quote from that article -

"A problem occurs when using QDCXLATE, however. When the IBM-supplied conversion tables QASCII, QEBCDIC, and QTCPASC are used, the API produces invalid results."

That article shows you how to use iconv().

HTH
Vern

Alan Shore wrote:

Good day all
I am using Scott Klements excellent RPGIV Socket tutorial and am having
some success

I am trying to connect to a Windows server 2008 standard definition 32 bit
(or so I am told)

I can definitely prove that I am connecting and that something is being
sent, but it looks like the api/program on the server has a problem reading
the data

I am translation the EBCDIC to ASCII using the table QTCPASC using the
QDCXLATE api, however my instinct is that this is probably wrong
I am waiting for the provider of the api to call me, but my question I need
answering is
If that table is not the correct one to use, how do I find out what table I
should be using?

My googling resulted in the following web page

http://www.mcpressonline.com/programming/rpg/determining-and-providing-the-appropriate-ccsid-for-an-api-external-system-or-language.html

Determining and Providing the Appropriate CCSID for an API, External System, or Language



My question is
What question do I ask ti discover what I should be using to translate?

Hopefully my e-mail makes sense

As always, any and all responses are MUCH appreciated



Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill