467,882 Members | 1,229 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

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

The HighValues plague returns....

.... been on the phone and e-mailing both WebSphere and DB2 support, but
so far, no answer. So I turn to c.d.db2.

the situation:
a COBOL74-370 app, compiled by MicroFocus to linux (RH/ES3). WS6 runs
on the linux box. The app is applet/servlet. Due to the COBOL legacy,
there are lots of columns (char) with x'FF' (various lengths). DB2 is
V8.[1|2]. There are two DB2 databases, also on the linux box. In the
first world, one database was win2K, the other z/OS; generally one
version lower on z/OS. Data from both are merged in the applet for
display. We found through experimentation that the z/OS x'FF' would
match a x'9F' on UDB. The applet needs to reconcile the two data
sources, in order for the rest of the legacy COBOL to do its
COBOL-thing. The browser is IE 6, and the jre 1.4.2_X/1.5.0_06. I
doubt these matter.

In development going back some time now, using tomcat from 3.x to 5.5.12
and WS 3.5 to 5.1.1 (though always windows) this shenanigans worked out.
Still does, in fact, using tomcat on my win2k machine. Treating
HighValues natively (x'FF') works like a charm.

Now we are compelled to run both databases and WS6 on linux. And
treating the HighValues natively *doesn't* work when using WS on linux.
By not work I mean, when matching such column data from the Work Table
(what in the first world was the UDB database) in one database with the
equivalent column data in the Main Table (what was the z/OS database in
the first world) in the other database fails. Yet the data shows in the
jre console as the same whether I'm connected to my tomcat server on
win2k or WS on linux (a lower case y, umlaut; the expected 1252 x'FF').

Setting clitrace yields 1252 codepage for all databases. The only
difference I've found so far, and don't trust my fingers to try to
change, is that LOCALE on linux is UTF-8. I haven't found a codepage
setting in WS yet. My reading of UTF-8 is that x'FF' doesn't map to a

So. Has anyone navigated this sort of Legacy Hell and survived? Is
there a magic bullet?


Apr 14 '06 #1
  • viewed: 1052

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by dan glenn | last post: by
5 posts views Thread by lkrubner | last post: by
5 posts views Thread by Susan Geller | last post: by
17 posts views Thread by nergal | last post: by
reply views Thread by MrMoon | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.