What the subject wants to drive, is into a discussion about all the issues
that are related to the conversion between EBCDIC and the rest of the
world's most used non-EBCDIC encoding.
I say "non-EBCDIC" just to say perfectly well anything that is not EBCDIC
so clearly. IBM's success on their IBM i systems is so good and I share
the happiness to have made it into this world. However, one has to face
this very particular problem when it comes to the CCSID world. It's so
annoying. There should now be only one standard.
Yeah, yeah, yeah, many of you would come up and say "you can do it and
nothing stops you". There will always be a conflict. While Big Blue keeps
with EBCDIC, conversion between something different from EBCDIC and EBCDIC
Creating databases from CCISD 037 to something else than that, is a pain in
the heart. You will always get to run and fix that.
Why not, at all, finally, IBM turns into Unicode for all stuff?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.