RE: XML-SAX parsing issue -- RPG400-L

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

Subject: RE: XML-SAX parsing issue
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Tue, 2 Dec 2014 13:26:41 -0600
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

I ended up doing this:
stringLen /= 2;
chars = %subst(charsUCS2: 1 :stringLen);

Otherwise, I got twice the number of characters I actually needed. The problem XML document now parses perfectly. I can't guarantee it, but making chars VARYING seems to have sped things up as well.

Thanks

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: XML-SAX parsing issue , Jon Paris
Re: XML-SAX parsing issue , Vernon Hamberg

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.