|
Barbara Morris <bmorris@xxxxxxxxxx> wrote:
The fancy %TRIM isn'tavailable then, but you could trim the blanks and nulls using a loop (ah, I see you already did that).Regarding the C module, I guess I misunderstood this statement in one of your posts. I thought that yourC server comm module might know the length of data it was passing, and could build your varying length unicode string for you.
Yes, I did end up using a loop; I improved on Joe's idea by just testing for anything with less than or equal to a Unicode space.
As to the other, I was probably a bit over-optimistic about what could be done from C: it knows the length of what it's passing, and it knows something about where it needs to be sent (or whether it's something it can handle on its own, i.e., a non-database request), but beyond that, it's just bytes, and for all it knows (or cares), those bytes could be any combination of EBCDIC text, EBCDIC Zoned Decimal, or Unicode. The RPG program understands what it's being passed; that's what matters.
Thanks again, to all who offered suggestions, even suggestions that weren't applicable. That's how we all learn.
-- JHHL
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
