SEO

Hi All,
I am trying to connect the Database which is installed in AS400
using DB2 Client Version 8 in Windows box.


First i created the Catalog,



then when i selected the connection type as ODBC, then i am getting
following error, could any one please help in solving this issue?

ODBC connection failed.
[IBM][CLI Driver] SQL0332N There is no available conversion for the
source code page "1252" to the target code page "0". Reason Code "1".
SQLSTATE=57017






Thanks & Regards
Nanjayan

nan wrote:
> Hi All,
> I am trying to connect the Database which is installed in AS400
> using DB2 Client Version 8 in Windows box.
>
> First i created the Catalog,
>
> then when i selected the connection type as ODBC, then i am getting
> following error, could any one please help in solving this issue?
>
> ODBC connection failed.
> [IBM][CLI Driver] SQL0332N There is no available conversion for the
> source code page "1252" to the target code page "0". Reason Code "1".
> SQLSTATE=57017
>

Nit: DB2 UDB for iSeries (AS/400) is part of the operating system
(OS/400). It is not "installed".

Below the text for iSeries message SQL0332 is shown. You might check
into the CCSID value assigned to the (iSeries) user profile you are
using to CONNECT. It may need to be changed if it is currently set to
0. Or if it is set to *SYSVAL use this command to check the value of
QCCSID system value:
> wrksysval qccsid

Just some things to look into...

> wrkmsgd sql0332 qsqlmsg
Message ID . . . . . . . . . : SQL0332

Message file . . . . . . . . : QSQLMSG

Library . . . . . . . . . : QSYS



Message . . . . : Character conversion between CCSID &1 and CCSID &2
not valid.

Cause . . . . . : Character or graphic conversion has been attempted
for data that is not compatible. There is no conversion defined between
CCSID &1 and CCSID &2.

If one CCSID is 65535, the other CCSID is a graphic CCSID. Conversion is
not defined between 65535 and a graphic CCSID. If this is a CONNECT
statement, conversion is not defined between the default application
requester SBCS CCSID and the application server SBCS CCSID. If the
second CCSID is 0, the application server did not return its default
SBCS CCSID. An application server other than an iSeries may not support
a CCSID of 65535.
Recovery . . . : Ensure that all character or graphic comparisons,
concatenation, or assignments are between columns or host variables with
compatible CCSID values.
If this is a CONNECT statement, change either the SBCS CCSID of the
application requester or the application server, so conversion between
the CCSID values is defined.

--
Karl Hanson

Karl Hanson wrote:

> Nit: DB2 UDB for iSeries (AS/400) is part of the operating system
> (OS/400). It is not "installed".

If operating system on AS/400 was installed (in manufacturing or by customer; it
doesn't matter how) - then any part of it (for example DB2/400) was also
installed, right?

Jan M. Nelken

Jan M. Nelken wrote:
> Karl Hanson wrote:
>
>> Nit: DB2 UDB for iSeries (AS/400) is part of the operating system
>> (OS/400). It is not "installed".
>
>
> If operating system on AS/400 was installed (in manufacturing or by
> customer; it doesn't matter how) - then any part of it (for example
> DB2/400) was also installed, right?
>

Correct. There is no separate product to install for SQL etc. There
are some separate products such as 5722ST1 (Query Mgr & DevKit) that
provide for example an interactive SQL interface.

http://www.ibm.com/servers/eserver/i...b2/db2faq.html

Note: There are some optionally installable parts of OS/400, such as
Option 1 : Extended Base Support. However DB2 is not one of those.

--
Karl Hanson