Hello folks,
I am here with another question today.
We are a large international company with a market presence in Japan.
We store our mainframe EBCDIC data for these markets in EBCDIC CodePage 930.
This CodePage has no support for lower case English letters.
If I were a distributed platform and I generated a UTF-8 encoded UUID
value, and sent this value to the mainframe, it would be then transformed
into EBCDIC CodePage 930.
If the UUID were to be generated with any lower case English values ("a",
"b", "c", "d", "e", or "f") I would expect to encounter some issue at
conversion/transformation time, since the underlying EBCDIC CodePage cannot
support the value.
However, if upper case values were sent instead ("A", "B", "C", "D", "E",
or "F"), everything would flow and transform politely.
So, my question is whether in the Japan world, mainframe application expect
Consumers to send only upper cased values, or if an intermediate step prior
to message transformation occurs close to the mainframe side of things to
force upper casing of the UUID.
Or some other technique?
Similarly, if a UUID were to be sent from the mainframe to the middle tier
somewhere, should I expect that the mainframe would only pas along upper
cased values in the UUID area?
I believe I can handle things on the mainframe side by transforming the
entire message to UTF-16BE, and then upper casing the UUID, and then
transforming this updated UTF-16BE message area to EBCDIC CodePage 930.
Not sure if this is a "good" way, but it would work.
Any thoughts?
Thanks
.......Cameron
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
