Re: XML-SAX *XML_EXCEPTION event and reported parsed length question -- 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 *XML_EXCEPTION event and reported parsed length question
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Thu, 13 Jul 2017 20:03:55 -0400
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>

On Thu, Jul 13, 2017 at 6:58 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Running the CPY command just prior to the XML-SAX opcode is quite trivial.

It is. But I was under the impression it wouldn't work. Maybe that
impression was mistaken? What happens to characters that are not
representable in the target CCSID?

John Y.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: XML-SAX *XML_EXCEPTION event and reported parsed length question , Nathan Andelin

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.