By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,686 Members | 1,558 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,686 IT Pros & Developers. It's quick & easy.

DB2 UDB V7 & V8 codepage difference - DB2 z/OS ?

P: n/a
Hi

Anyone know where I can look for problem with codepage conversion between
DB2 UDB Connect EE V8.2 (fixpak 3) and DB2 UDB z/OS V7.

With DB2 UDB Connect EE V7.2 (fixpak 7) i get Ebcdic X'5A' converted to
Ascii X'A4', but with V8 I get it converted to Ascii X'80'.
I use Ebcdic codepage/ccsid 277 and client codepage 1252.

It looks like a problem with Windows Latin-1 1252/5348 - the Euro codepage,
but I can't find anything that can explain the why I get an 5348 codepage
when I use 1252 at the client.

Any suggestion welcome.

/Kim
Nov 12 '05 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Hi Kim,

It is an expected behaviour in v8. Microsoft changed the 1252 definition by
the addition of Euro symbol in x80 without changing the definition name to
5348. If you see the definition of 1252 in Microsoft web page now, you will
see Euro at x80. Microsoft 1252 is 5348.

If you want to go back to v7 behaviour, you need to copy two conversion
files, 02771252.cnv and IBM0277.ucs. The information is documented in the
following link:
http://www-3.ibm.com/cgi-bin/db2www/...n=r0007951.htm

Download information and instruction is documented in the following link:
http://www-3.ibm.com/cgi-bin/db2www/...n=t0004584.htm
Sherman

"Kim Bundgaard" <kib at kmd.dk> wrote in message
news:3f***********************@dread15.news.tele.d k...
Hi

Anyone know where I can look for problem with codepage conversion between
DB2 UDB Connect EE V8.2 (fixpak 3) and DB2 UDB z/OS V7.

With DB2 UDB Connect EE V7.2 (fixpak 7) i get Ebcdic X'5A' converted to
Ascii X'A4', but with V8 I get it converted to Ascii X'80'.
I use Ebcdic codepage/ccsid 277 and client codepage 1252.

It looks like a problem with Windows Latin-1 1252/5348 - the Euro codepage, but I can't find anything that can explain the why I get an 5348 codepage
when I use 1252 at the client.

Any suggestion welcome.

/Kim

Nov 12 '05 #2

P: n/a
Hi

Thank you, but please explain why .....

The Windows client is the same (and so is the DB2 z/OS V7) - the only thing
I've changed is the DB2 UDB from V7 to V8.

As I understand the DRDA-session, it is the DRDA-Server that have to do the
translation of characteres from EBCDIC to Ascii - and from SYSSTRINGS
(277/1252) I can see that EBCDIC X'5A' translate to a X'A4' - and that is
what I get at the DB2 UDB V7.

But at V8 I get a X'80' (Euro-sign).

/Kim

"Sherman Lau" <sh***********@ca.ibm.com> wrote in message
news:bn**********@hanover.torolab.ibm.com...
Hi Kim,

It is an expected behaviour in v8. Microsoft changed the 1252 definition by the addition of Euro symbol in x80 without changing the definition name to
5348. If you see the definition of 1252 in Microsoft web page now, you will see Euro at x80. Microsoft 1252 is 5348.

If you want to go back to v7 behaviour, you need to copy two conversion
files, 02771252.cnv and IBM0277.ucs. The information is documented in the
following link:
http://www-3.ibm.com/cgi-bin/db2www/...pport/v8infoce
nter.d2w/report?target=mainFrame&fn=r0007951.htm
Download information and instruction is documented in the following link:
http://www-3.ibm.com/cgi-bin/db2www/...pport/v8infoce
nter.d2w/report?target=mainFrame&fn=t0004584.htm

Sherman

"Kim Bundgaard" <kib at kmd.dk> wrote in message
news:3f***********************@dread15.news.tele.d k...
Hi

Anyone know where I can look for problem with codepage conversion between DB2 UDB Connect EE V8.2 (fixpak 3) and DB2 UDB z/OS V7.

With DB2 UDB Connect EE V7.2 (fixpak 7) i get Ebcdic X'5A' converted to
Ascii X'A4', but with V8 I get it converted to Ascii X'80'.
I use Ebcdic codepage/ccsid 277 and client codepage 1252.

It looks like a problem with Windows Latin-1 1252/5348 - the Euro

codepage,
but I can't find anything that can explain the why I get an 5348 codepage when I use 1252 at the client.

Any suggestion welcome.

/Kim


Nov 12 '05 #3

P: n/a
The receiver is doing the conversion in DRDA. When you select EBCDIC X'5A',
the DB2 UDB v8 client is converting EBCDCI X'5A' to 1252 X'80' using its
internal conversion table, not SYSIBM.SYSSTRINGS in DB2/zOS. If you replace
the UDB conversion table from the ftp site, UDB will read in the replaced
conversion table and convert the data to 1252 X'A4' for you.

Sherman

"Kim Bundgaard" <kib at kmd.dk> wrote in message
news:3f***********************@dread15.news.tele.d k...
Hi

Thank you, but please explain why .....

The Windows client is the same (and so is the DB2 z/OS V7) - the only thing I've changed is the DB2 UDB from V7 to V8.

As I understand the DRDA-session, it is the DRDA-Server that have to do the translation of characteres from EBCDIC to Ascii - and from SYSSTRINGS
(277/1252) I can see that EBCDIC X'5A' translate to a X'A4' - and that is
what I get at the DB2 UDB V7.

But at V8 I get a X'80' (Euro-sign).

/Kim

"Sherman Lau" <sh***********@ca.ibm.com> wrote in message
news:bn**********@hanover.torolab.ibm.com...
Hi Kim,

It is an expected behaviour in v8. Microsoft changed the 1252 definition by
the addition of Euro symbol in x80 without changing the definition name to
5348. If you see the definition of 1252 in Microsoft web page now, you

will
see Euro at x80. Microsoft 1252 is 5348.

If you want to go back to v7 behaviour, you need to copy two conversion
files, 02771252.cnv and IBM0277.ucs. The information is documented in the following link:

http://www-3.ibm.com/cgi-bin/db2www/...pport/v8infoce nter.d2w/report?target=mainFrame&fn=r0007951.htm

Download information and instruction is documented in the following link:

http://www-3.ibm.com/cgi-bin/db2www/...pport/v8infoce nter.d2w/report?target=mainFrame&fn=t0004584.htm


Sherman

"Kim Bundgaard" <kib at kmd.dk> wrote in message
news:3f***********************@dread15.news.tele.d k...
Hi

Anyone know where I can look for problem with codepage conversion

between DB2 UDB Connect EE V8.2 (fixpak 3) and DB2 UDB z/OS V7.

With DB2 UDB Connect EE V7.2 (fixpak 7) i get Ebcdic X'5A' converted to Ascii X'A4', but with V8 I get it converted to Ascii X'80'.
I use Ebcdic codepage/ccsid 277 and client codepage 1252.

It looks like a problem with Windows Latin-1 1252/5348 - the Euro

codepage,
but I can't find anything that can explain the why I get an 5348 codepage when I use 1252 at the client.

Any suggestion welcome.

/Kim



Nov 12 '05 #4

P: n/a
Hi Sherman

I'm a little confused.
Where is the translation actually happend ?

I always believe that the translation is occuring at the DRDA-Server - which
in my world is the DB2 z/OS. Because of all the SYSSTRINGS entries, and
problems not having the correct to/from CCSID in SYSSTRINGS.

In my example/world i have the following :

a) DRDA-Server : DB2 z/OS V7 (EBCDIC/CCSID 277)
b) DB2 Connect EE V7 as gateway
c) DB2 Runtime/Appl.Dev. Client (Ascii/codepage 1252)

When I at c) select data from a) - where is the translation from EBCDIC to
Ascii going on ?
At a), b) or c) ?
Is it both a) and 3), or b), or c) ?

/Kim
"Sherman Lau" <sh***********@ca.ibm.com> wrote in message
news:bn**********@hanover.torolab.ibm.com...
The receiver is doing the conversion in DRDA. When you select EBCDIC X'5A', the DB2 UDB v8 client is converting EBCDCI X'5A' to 1252 X'80' using its
internal conversion table, not SYSIBM.SYSSTRINGS in DB2/zOS. If you replace the UDB conversion table from the ftp site, UDB will read in the replaced
conversion table and convert the data to 1252 X'A4' for you.

Sherman

"Kim Bundgaard" <kib at kmd.dk> wrote in message
news:3f***********************@dread15.news.tele.d k...
Hi

Thank you, but please explain why .....

The Windows client is the same (and so is the DB2 z/OS V7) - the only thing
I've changed is the DB2 UDB from V7 to V8.

As I understand the DRDA-session, it is the DRDA-Server that have to do

the
translation of characteres from EBCDIC to Ascii - and from SYSSTRINGS
(277/1252) I can see that EBCDIC X'5A' translate to a X'A4' - and that is
what I get at the DB2 UDB V7.

But at V8 I get a X'80' (Euro-sign).

/Kim

"Sherman Lau" <sh***********@ca.ibm.com> wrote in message
news:bn**********@hanover.torolab.ibm.com...
Hi Kim,

It is an expected behaviour in v8. Microsoft changed the 1252 definition
by
the addition of Euro symbol in x80 without changing the definition
name to 5348. If you see the definition of 1252 in Microsoft web page now, you

will
see Euro at x80. Microsoft 1252 is 5348.

If you want to go back to v7 behaviour, you need to copy two
conversion files, 02771252.cnv and IBM0277.ucs. The information is documented in

the following link:

http://www-3.ibm.com/cgi-bin/db2www/...pport/v8infoce nter.d2w/report?target=mainFrame&fn=r0007951.htm

Download information and instruction is documented in the following link:

http://www-3.ibm.com/cgi-bin/db2www/...pport/v8infoce
nter.d2w/report?target=mainFrame&fn=t0004584.htm


Sherman

"Kim Bundgaard" <kib at kmd.dk> wrote in message
news:3f***********************@dread15.news.tele.d k...
> Hi
>
> Anyone know where I can look for problem with codepage conversion

between
> DB2 UDB Connect EE V8.2 (fixpak 3) and DB2 UDB z/OS V7.
>
> With DB2 UDB Connect EE V7.2 (fixpak 7) i get Ebcdic X'5A' converted to > Ascii X'A4', but with V8 I get it converted to Ascii X'80'.
> I use Ebcdic codepage/ccsid 277 and client codepage 1252.
>
> It looks like a problem with Windows Latin-1 1252/5348 - the Euro
codepage,
> but I can't find anything that can explain the why I get an 5348

codepage
> when I use 1252 at the client.
>
> Any suggestion welcome.
>
> /Kim
>
>



Nov 12 '05 #5

P: n/a
DB2 always translates at the receiving end.

Regards Rolf
Nov 12 '05 #6

P: n/a
Kim,

Rolf is correct. Let me show you an example.

Windows 1252 client. zOS 227 server.

If you insert a record from the client to the server, the server will do the
data conversion from 1252 to 227.

If you select a record from the server to the client, the client will do the
data conversion from 227 to 1252.

In your case, you are doing a select, your client is doing the conversion
for you.

Sherman
"Rolf Loeben" <ro*********@online.de> wrote in message
news:bn************@ID-207325.news.uni-berlin.de...
DB2 always translates at the receiving end.

Regards Rolf

Nov 12 '05 #7

P: n/a
Hi Sherman (and Rolf)

Okay - I understand. I have to change my understanding of codepage
translation bewteen DB2 z/OS and DB2 UDB Runtime Client.

I can be a little insecure about IBM changing the translation without doing
a BIG ALARM in the "News for DB2 UDB V8".
It's a little inconvenient to distribute an alternative .cnv file to all my
clients because of the change.

Thank you for your comments to my misleading understanding.

Regards
Kim

"Sherman Lau" <sh***********@ca.ibm.com> wrote in message
news:bn**********@hanover.torolab.ibm.com...
Kim,

Rolf is correct. Let me show you an example.

Windows 1252 client. zOS 227 server.

If you insert a record from the client to the server, the server will do the data conversion from 1252 to 227.

If you select a record from the server to the client, the client will do the data conversion from 227 to 1252.

In your case, you are doing a select, your client is doing the conversion
for you.

Sherman
"Rolf Loeben" <ro*********@online.de> wrote in message
news:bn************@ID-207325.news.uni-berlin.de...
DB2 always translates at the receiving end.

Regards Rolf


Nov 12 '05 #8

P: n/a
Hi

When i download the 02771252.cnv file to x:\sqllib\conv, my application
crashes/abend (there where no 02771252.cnv to replcae).
I've done a binary download.

By the way - when I use the default DB2 UDB V8 to insert/select data to/from
DB2 z/OS i get the "general currency symbol" and the "Euro sign" converted.
When I insert the Ascii hex is X'A4' for "general currency sign" and X'80"
for Euro sign.
In DB2 z/OS it become EBCDIC X'20' and X'5A'
When I select the row again, I get EBCDIC X'20' returned as Ascii X'A4' and
EBCDIC X'5A' as Ascii X'80' - the sign changed ...

/Kim
"Sherman Lau" <sh***********@ca.ibm.com> wrote in message
news:bn**********@hanover.torolab.ibm.com...
Kim,

Rolf is correct. Let me show you an example.

Windows 1252 client. zOS 227 server.

If you insert a record from the client to the server, the server will do the data conversion from 1252 to 227.

If you select a record from the server to the client, the client will do the data conversion from 227 to 1252.

In your case, you are doing a select, your client is doing the conversion
for you.

Sherman
"Rolf Loeben" <ro*********@online.de> wrote in message
news:bn************@ID-207325.news.uni-berlin.de...
DB2 always translates at the receiving end.

Regards Rolf


Nov 12 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.