468,242 Members | 1,474 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,242 developers. It's quick & easy.

Euro Symbol and ASCII-Tablespace

We are using ASCII-Tablespaces with the Codepage 819 on z/OS. We're now
having a problem with the EURO symbol. The data is inserted from a
Windows-Client, running Codepage 1252. The Euro symbol is not part of
the Codepage 819 which leads to a converting of the Euro Symbol to
hex(1A) in the Database. On the Client, hex(1A) is returned which is
different from the send hex(80).
Is there any other codepage which is similar to Codepage 819, but
includes the Euro Symbol which can be used for the tablespaces?

Nov 12 '05 #1
2 4186
tilmann wrote:
We are using ASCII-Tablespaces with the Codepage 819 on z/OS. We're now
having a problem with the EURO symbol. The data is inserted from a
Windows-Client, running Codepage 1252. The Euro symbol is not part of
the Codepage 819 which leads to a converting of the Euro Symbol to
hex(1A) in the Database. On the Client, hex(1A) is returned which is
different from the send hex(80).
Is there any other codepage which is similar to Codepage 819, but
includes the Euro Symbol which can be used for the tablespaces?


Not really sure here, but perhaps 2byte unicode?
Codepages among OSes and DB2 suck :/ (if your using 2 clients with
different codepages)
Isn't it possible on z/OS to define the tablespace as latin? thus using
the same codepage as windows does?

-R-
Nov 12 '05 #2
tilmann wrote:
We are using ASCII-Tablespaces with the Codepage 819 on z/OS. We're now
having a problem with the EURO symbol. The data is inserted from a
Windows-Client, running Codepage 1252. The Euro symbol is not part of
the Codepage 819 which leads to a converting of the Euro Symbol to
hex(1A) in the Database. On the Client, hex(1A) is returned which is
different from the send hex(80).
Is there any other codepage which is similar to Codepage 819, but
includes the Euro Symbol which can be used for the tablespaces?

I would go for UTF-8 (unicode).
Plain ASCII (below X'80') takes just 1 byte in UTF-8

--
Anton Versteeg
IBM Netherlands
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by VK | last post: by
4 posts views Thread by Robert Zierhofer | last post: by
1 post views Thread by Kevin | last post: by
7 posts views Thread by flm | last post: by
11 posts views Thread by MH | last post: by
18 posts views Thread by gabriel | last post: by
5 posts views Thread by SalamElias | last post: by
8 posts views Thread by Max | last post: by
4 posts views Thread by rphil | last post: by
7 posts views Thread by Robertu | last post: by
reply views Thread by kermitthefrogpy | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.