× 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.



John:

AFAIK OS/400 and IBM i has never supported "Unicode" in any object names in the QSYS.LIB file system. (Unicode is supported in the IFS in the root and QOpenSys directories.)

Names in the QSYS.LIB file system are (unfortunately) not "tagged" with an indication of what CCSID was used, so we can only assume that they are in the default QCCSID for that system on which the object was created. That "O" with dots over it could easily be an EBCDIC character in some European code page, such as that for German, etc. The rest of the characters are just normal EBCDIC.

Ask your client what is the system value QCCSID set to on their system.

One simple "work-around" would be to ask the customer if they can just rename that one library to contain only the normal EBCDIC characters, A-Z and 0-9, and the "national" characters (@, # and $ in the US). That way, you would not need to make any changes to your software, for now.

HTH,

Mark S. Waterbury

> On 2/22/2016 1:16 PM, John R. Smith, Jr. wrote:
One of my clients has an iSeries with Unicode object names such as a library
named XXXÖQRY. The software that they are working with is not designed to
handle Unicode object names and I have been asked to make modifications to
allow this. Unfortunately, I have never dealt with Unicode object names and
my development machine will not allow such names. Can someone point me in
the right direction on how to get my system to allow such names and also
provide any pros or cons to making the changes to my system to allow this?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 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.