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

Since it is the customer connection that appears to be the issue - a
hypothetical - what if the user profile they connect with specifies (in the
user profile) ccsid = 1208, and is unique to that customer.
James - I'm not set up for testing this but perhaps you are.

Jim Franz



On Mon, May 26, 2025 at 10:28 AM cesco via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I was hoping that there might be somebody here who'd encountered a

similar situation before, and recognized it.
I did encounter something similar, but using ODBC in PASE posting in the
local DB2 (i on i).
Solved forcing CCSID = 1208 in the connection descriptor.
YMMV obviously, the moving parts can be many.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.