Page 1 of 1
odbc from ds on lnux to as400/db2
Posted: Tue Jun 07, 2005 7:17 am
by roy
Hi yall,
I'm trying to get a data direct odbc working with as400/db2.
when trying to bind20 the odbc name I get 1213 error
(same when running the odbcdemo supplied by data direct)
Does anyone have any idea as to requirements for establishing a working connection in the mentioned configuration?
both on the as400 side and the linux side.
Any info would be apreciated (including what I already know ;:)
Thanks in advance,
Posted: Wed Jun 08, 2005 4:35 am
by roy
Forgot to mention as400 is V5R3.
I know docs and branded_odbc states V5R2 latest supported.
I'll try to find out if I can find a newer version or use the iSeries client access driver.
Posted: Thu Jun 09, 2005 12:35 am
by roy
Well,
After failing I asked to try it on the prod system (V5R2 till this week end) to make a support call... (using the data direct drivers)
I was amazed to see it working
.
7.5.1a release notes mention a bind20 that needs to be done (never successfully did it)
So tried again on the V5R3 using again an existing working login account and it is working
I guess having more privilages then you need might actually not be to ones advantage in some cases.
so current issue is handling NLS that still shows ???.??? data, despite trying several NLS maps that should have worked.
p.s.
we configured the iSeries ODBC driver and had it working using isql, was able to see NLS chars correctly,but using it failed to supply DS any characters belonging to the NLS locale, so we reverted back to the data direct drivers.
Posted: Tue Jun 21, 2005 4:52 am
by roy
update:
Well after having support online for 1 hour (not by me) I gather they added an entry in the .odbc.ini configuration for that connection and it shows the NLS, with some issues, but its working.
I've yet to get the exact details.
Posted: Sun Jun 26, 2005 4:54 am
by roy
update:
adding this line:
IANAAppCodePage=<number>
to the .odbc.ini with <number> being 11 in the case mentioned got it working.
IHTH,