Accessing DB2 for OS/390 through DB2-Connect

Review Appendix C of the DB2 Connect User's Guide.
CCSIDs are listed in Appendix J of the Administration Guide.

"SW" wrote in message
news:9dc53b22.0307220032.63bc485a@posting.google.com...
> Hello!
>
> I am trying to access a DB2 OS/390 7.1.1 using DB2-Connect
> from a Linux or Windows system. After cataloging the "tcpip node"
> the "database" and the "dcs database" I can connect to the db.
>
> When I select data from the db tables this seemed to work correctly
> at first. But then I realized that some characters are not converted
> correctly from EBCDIC to ISO-8859-1. The data contains german special
> characters "äöüÖÄÜ" and these are all mixed up. I found that the
> character "ä" gets translated to "{".
>
> After playing around with the "DB2CODEPAGE" variable on the client
> I realized that the problem seems to come from the fact that there are
> different EBCDIC codesets on the mainframe.
>
> There is a codepage EBCDIC-273-German and a codepage EBCDIC-37-US.
> The characters "ä" and "{" trade places between those to codepages.
>
> Seems like DB2-Connect is converting "EBCDIC-37" to "ISO-8859-1",
> instead of doing the correct conversion from "EBCDIC-273" to "ISO-8859-1".
>
> From reading the manuals I have learned that this has to do with the
> CCSID of the database.
>
> Can anyone tell me where to find a list of the possible CCSIDs and
> how to configure the database or DB2-Connect to assume the correct CCSID.
>
> Thanks!
>
> Bye,
> Stefan

Review Appendix C of the DB2 Connect User's Guide.
CCSIDs are listed in Appendix J of the Administration Guide.

"SW" wrote in message
news:9dc53b22.0307220032.63bc485a@posting.google.com...
> Hello!
>
> I am trying to access a DB2 OS/390 7.1.1 using DB2-Connect
> from a Linux or Windows system. After cataloging the "tcpip node"
> the "database" and the "dcs database" I can connect to the db.
>
> When I select data from the db tables this seemed to work correctly
> at first. But then I realized that some characters are not converted
> correctly from EBCDIC to ISO-8859-1. The data contains german special
> characters "äöüÖÄÜ" and these are all mixed up. I found that the
> character "ä" gets translated to "{".
>
> After playing around with the "DB2CODEPAGE" variable on the client
> I realized that the problem seems to come from the fact that there are
> different EBCDIC codesets on the mainframe.
>
> There is a codepage EBCDIC-273-German and a codepage EBCDIC-37-US.
> The characters "ä" and "{" trade places between those to codepages.
>
> Seems like DB2-Connect is converting "EBCDIC-37" to "ISO-8859-1",
> instead of doing the correct conversion from "EBCDIC-273" to "ISO-8859-1".
>
> From reading the manuals I have learned that this has to do with the
> CCSID of the database.
>
> Can anyone tell me where to find a list of the possible CCSIDs and
> how to configure the database or DB2-Connect to assume the correct CCSID.
>
> Thanks!
>
> Bye,
> Stefan