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



I believe there is a similar issue with an XML-SAX parser error, which gives a position where the error occurs - or how much of the XML has been processed before the error - one or the other.

It reports the position or offset by byte, not by character. I don't know if this is a general standard, I searched for parser error codes and looked at a couple, such as for a product called LabView at ni.com (not an IBM i product that I could see) - it had a list of 179 codes, and not exactly the same as those reported in RNX0351 - thoughts on my admittedly-brief search?

Regards
Vern

On 8/6/2020 1:24 AM, Joep Beckeringh via RPG400-L wrote:
Thank you, Barbara.

RFE has been submitted: <https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=144464 <https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=144464>>

(And thanks for the helpful instructions on RPG Cafe).

Joep Beckeringh


Op 5-8-2020 om 18:44 schreef Barbara Morris:
On 2020-08-05 4:55 a.m., Joep Beckeringh via RPG400-L wrote:
OK, but then the documentation is, let's say, not very precise :-)

The reference says for %len:
- 'For character, graphic, or UCS-2 expressions the value returned is the number of characters in the value
of the expression.'
- 'For all other data types, the value returned is the number of bytes of the value.'


Thanks Joep. We'll look into clarifying the documentation.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.