× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Perhaps you could look closer to my RFE/IDEA that is actually delivered in

That is like UTF-8 but for EBCDIC - namely UTF-E - the new CCSID 1210.


Thumbs up for your quote Scott - Not setting the system value QCCSID is the
mother of all ccsid issues ... And I spend a LOT of time solving CCSID
issues for clients hench my RFE/IDEA ...

On Mon, Feb 27, 2023 at 3:04 AM Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>

As far as everything on the system being Unicode -- probably not, as
it'd break virtually everything.

But the system does fully support Unicode... you can write your
applications in Unicode, set up your databases in Unicode, etc. It's
really only 5250 emulation where you need to use EBCDIC. (And even that
allows Unicode within display files.) And in many/most cases it'll
automatically convert between Unicode and EBCDIC as needed.

The biggest problem is getting everyone to change their applications to
use Unicode, IMHO. It's not really an IBM problem, every progammer in
the world in every shop needs to write their applications in Unicode.
It's hard enough to get IBM i shops to set their friggin' QCCSID system
value (which involves almost no work or problems, yet it's like pulling
teeth to get them to do it). Getting them to rewrite their programs and
databases to use Unicode is a million times more work... the ability is
there... getting people to do it is hard.


On 2/26/2023 5:04 PM, Javier Sanchez wrote:
What the subject wants to drive, is into a discussion about all the
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
with EBCDIC, conversion between something different from EBCDIC and
will prevail.

Creating databases from CCISD 037 to something else than that, is a pain
the heart. You will always get to run and fix that.

Why not, at all, finally, IBM turns into Unicode for all stuff?


Javier Sanchez
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,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.