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



You have already received good advice on how to fix the incorrectly formed DBCS data (matching up SO/SI occurrences) and your ERP vendor needs to do the same type of work. In the vendors case however they could, rather than coding the proper truncation logic, use the Truncate Character Data API QLGTRDTA documented at http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/QLGTRDTA.htm
The API will provide for correct truncation of a variety of encoding schemes -- where the current discussion is specific to Mixed EBCDIC Data.

The API unfortunately won't do you any good in correcting the malformed character data after the fact -- it expects good input to start with.

Bruce Vining


jeffw@xxxxxxxxxxxxxxxx wrote:

Hi everybody.
Sorry for the wordy explanation but it is the only way I know how to convey
the problem. I have a field that is being filled by our ERP package that is
in DBCS (Chinese). The problem is one field is 20 but another field they are
putting the same data in is 15 (short of like a short desc of the first
field).
So when they fill the field with DBCS data if it is larger than the 15 then
I think it is losing the SHIFT-IN hex value. Our ERP vendor is working on
this, but I have a lot of data that is bad at the moment.
I want to write a cleanup to go into the file and fix the fields. If you try
and DFU the field it looks like garbage data in the field. I dont have much
experience with HEX, but what I have learned is this should work but it
doesnt.
EVAL CDESC=%trimr(CDESC)+x'0F'
I have a program that I wrote that has screen that will show both fields if
I copy and paste it manually into the new field it works. Any ideas?
Thanks
Jeff Williams

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.