Hi all,

I've a UNIX box which has a DB2 client (UDB v9.5) connecting to a
remote DB2 server(UDB v9.5) and some SAS applications running on top
of the DB2 client. The remote DB2 server is planning to convert from
non-unicode to unicode. I'm wondering what's the impacts on my client
side?

Thanks in advance!

On Jul 23, 9:38*am, Tony <tonyedr... (AT) gmail (DOT) com> wrote:
you should be OK with the same client.

Thanks for the reply!

So you mean I don't need to change the DB2 client configration, and
the SAS applications should be no change as well? Thanks.


On Jul 23, 2:24*pm, Hardy <wyh... (AT) gmail (DOT) com> wrote:

You don't have to change the client configuration. The conversion between
codepages is done automatically.

Let's say you are using a unicode database (codepage 1208) and your client on
AIX is using codepage 819. According to DRDA specification the conversion is
always done on the receiving side. If you use e.g. the DB2 CLP and send a
query to the database, the flow is as follows:

1) query or actually the bound values are converted at the server
2) server sends result in UTF8
3) client converts the data to codepage 819

The same is true for your SAS applications.

IMPORTANT: You might want to check the collating sequence for the unicode
database. You can choose the collating sequence only at the time you create
the database. By default the collating sequence is IDENTITY, which will most
likely result in a different sort order.

--
Helmut K. C. Tessarek
DB2 Performance and Development

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/