Re: Character set problem with data being sent through SQL(?)

On Fri, May 23, 2025 at 11:56 AM James H. H. Lampert via MIDRANGE-L
<midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

But it's acting as if their connection THINKS they're sending 8859 Latin
1. With the result that "lowercase e with acute accent," which is hex
"C3 A9" in UTF-8, ends up in the file as hex "23 62 B4," which is
<highlight reverse>, "Capital A with tilde," "copyright symbol."

OK. First of all, x'C3A9' is indeed small-e-with-acute in UTF-8. So
those are the two raw bytes they would see on their end, looking at
their own data.

Those two bytes, when interpreted as Latin-1, are capital-A-with-tilde
and copyright-sign. Just two characters. So presumably, if their
connection thinks their source data is Latin-1, then it would have
just sent over those two characters.

Now, I'm guessing you've got a typo, and it should be x'2366B4' that
are the bytes you are seeing on your end. (x'62' is
capital-A-with-circumflex in CCSID 37).

I'm a bit lost on how the x'23' got there.

Can you get any more specifics on what they're doing on their end to
set up the connection? Most if not all of the issue, given your
description, seems to be on their end.

John Y.