FYI:
" A round-trip conversion works only in a two-tier homogenous environment
where the data makes the complete round trip. For example, if you pass data
from DB2 for Linux, UNIX, and Windows to DB2 for z/OS and then back to DB2
for Linux, UNIX, and Windows with a round-trip conversion, no data is lost.
The data was converted back to its original format. However, if you have a
more complicated environment, a round-trip conversion does not necessarily
preserve data integrity. For example, if you pass data from DB2 for z/OS to
DB2 for Linux, UNIX, and Windows and then to Linux on a Java client, two
conversions have potentially occurred. Because the data was not converted
back to its original format before the second conversion, data might have
been lost even if round-trip conversions are used.
Example: In ASCII CCSID 1252, the trademark symbol T is code point X'99'. In
EBCDIC CCSID 37, this code point does not exist. During character conversion
from ASCII CCSID 1252 to EBCDIC CCSID 37, the trademark symbol is converted
to a control character, X'39'. If you use SPUFI to select the data, the data
displays as the unprintable character that you specified in your emulator,
which is generally a quotation mark (") or a period (.). If you issue a
SELECT HEX(column) statement, the data displays as X'39', which is the DEL
control character. When the client uses a round-trip conversion to convert
this character back to ASCII CCSID 1252, the trademark symbol is preserved
as code point X'99'. Notice that this conversion is not lossless unless it
is converted back to the original format."
--
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=%2Fco
m.ibm.db2z9.doc.char%2Fsrc%2Ftpc%2Fdb2z_roundtripconversion.htm
Charles
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
