× 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.



From what I can find, EBCDIC x'41' does not have an equivalent ASCII
character. I see ASCII x'41' is an A. Where did you find EBCDIC x'41' =
'A'?

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Nathan
Andelin
Sent: Monday, February 8, 2021 1:50 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Weird ODBC results

Assuming that the ODBC interface is extracting data to a PC, the x'41'
EBCDIC would be converted to "A" ASCII. Is that what they're seeing?

On Mon, Feb 8, 2021 at 11:12 AM <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.



I don't have access to what they are doing but I have been told they
are using ODBC driver "IBM i Access ODBC Driver 13.00.21.00" to
connect to all three machines and that all three ODBC configurations
are identical. I have confirmed with our tech team that all three
machines are identical for OS and PTF levels.



They are trying to convince me that the DB2 is configured differently
on two of the machines so the x'41' character is not returned in the
ODBC request on them and I'm not buying it. They did say that they
are receiving the x'41' when they connect via DB2Connect v. 11.1.4.5.



Can anyone tell me where to have them look in their ODBC config to
figure out why they are receiving different results across the machines?

--
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

--
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.