Thanks Justin, please do.

The original worked because you were targeting an array directly - so RPG puts the count into the PSDS. Since there is a count available therefore there is nothing missing because it has already told you how many there are. In the "all-in-one" approach the counts are needed because you're not targeting an array at the top level.

Jon Paris

On Aug 29, 2018, at 1:31 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I'm sure my single XML-INTO was still not quite right, which may be causing the slowdown. The five individual XML-INTO commands get by without allowmissing, but the single XML-INTO can't. The single XML-INTO loaded the data structure and all my tests passed, but it still showed something missing.

I'll check the vendor docs and see if they have any sample XML files. If so, I'll send you a copy off-list.

-----Original Message-----
From: Jon Paris []
Sent: Tuesday, August 28, 2018 12:35 PM
To: Rpg400 Rpg400-L <rpg400-l@xxxxxxxxxxxx>
Subject: Re: XML-INTO & path

I am really surprised that it is slower to do all of it at once rather than in pieces - can't think of a logical reason why that would be. You'd think a single parse would always have to be faster than multiples.

You can still use the count option to avoid allowmissing even if processing it in pieces.

If you have a test XML file you can send me I'd love to see it - might be the next article!

Jon Paris

This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support by shopping at with our affiliate link:

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by 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].