Re: CPYFRMSTMF & character conversion

On Wed, Feb 14, 2018 at 1:49 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

" It is entirely possible that the bytes that are in the PF are "correct" even if they do NOT display in the desired fashion.

The converse could also be true: The application you are using to display the data could be doing some "helpful" automatic conversions for you to make it appear readable, yet the bytes in the PF are actually not in the desired encoding."

Those sound like CCSID errors to me (ie. data and/or table have the wrong CCSID).

Well, that is precisely what we were trying to establish. By some shop
standards, the very existence of a PF defined as CCSID 65535... *is
itself a CCSID error*.

I cannot tell you how many times someone has asked for help with an
encoding-related issue, and they keep insisting that they "see" data
which is not what it's supposed to be, but after many rounds of
back-and-forth, it turns out that the tool that they were using to
"look" at the data is performing a conversion that they didn't expect,
or wasn't performing a conversion that they did expect. All the more
so if you have to work with CCSID 65535.

So don't dismiss it lightly. It is something that needs to be
explicitly ruled out.

John Y.