×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
The are complaining about the x'41' character so I guess they want it
converted to x'40'.
I will have them look at the ccsid translation. I assumed they did when
they said the configs were identical but...
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Sam_L
Sent: Monday, February 8, 2021 1:55 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Weird ODBC results
Not sure from your description whether they want the x'40' or the x'41'.
But just at a guess, it might be something to do with ccsid 65537
translation, which you can set on one of the ODBC tabs. And/or what the
default ccsid is set to the IBM i.
Sam
On 2/8/2021 1:12 PM,
smith5646midrange@xxxxxxxxx wrote:
We have a vendor file on three different machines and all three
machines have a record with a x'41' character in the vendor name. The
problem is that on two of the three machines, the x'41' is converted
to x'40' when the data is retrieved via ODBC.
--
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.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
