RE: XML-INTO & path

I consulted the article but I missed the part about filling the array (the developer's flaw, I scanned the text and read the code). The samples in your article are much simpler than what I've got.

I agree about allowmissing. I'd rather not use it.

Your PS sound like what the production code is doing. It loads Products (and each of the structures at that level) directly. I thought that was a bad idea, but it's 50% faster than my test code loading the top-level structure all at once.

I'll probably just leave the production code as-is. I guess this is why we do benchtests. Thanks again for all you help. :)



-----Original Message-----
From: Jon Paris [mailto:jon.paris@xxxxxxxxxxxxxx]
Sent: Tuesday, August 28, 2018 10:46 AM
To: Rpg400 Rpg400-L <rpg400-l@xxxxxxxxxxxx>
Subject: Re: XML-INTO & path

As the article I referenced would have told you, without count fields items will be considered "missing" if the array is not filled. So, for example, if Products is defined with Dim(99) then f the XML contained less than 99 elements then the others would be "missing". The addition of the count allows RPG to tell you how many there actually are and so they are not considered to be missing.

Using allowmissing=yes is REALY REALY dangerous. Fro example - the file could basically be "empty" and RPG would not signal an error. By using count fields with all arrays and with any optional items you can always be sure that it will error out if the file is bad.

P.S. Your current DS can probably lose the outer DS (gOutputDs) and just start with Products but you may need a path. If you load directly into Products array then the count for this level will be in the PSDS.

If you would like to email me your completed D specs I'll show you how to adjust them.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com