Re: XML-INTO %HANDLER PATH

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Dave

This is definitely a situation where I suggest using SQL's XML support - 
XMLTABLE, which lets you pretty easily flatten selected XML elements 
into table rows - only the elements you are interested in.

Here's a link to an example - 
https://www.rpgpgm.com/2018/07/getting-data-from-xml-file-using-sql.html

I know, Jon P, this isn't your favorite solution!

I find that XMLTABLE can look a lot like CREATE TABLE, with columns 
defined with regular SQL data types, plus "path" specs for where each 
element is located in the XML.

See if that article helps - if you need more, I can probably help, I 
give a case study presentation about this.

Cheers
Vern

On 1/19/2025 7:12 PM, Charles Wilt wrote:
> Actually, that "process in chunks" idea is not quite right...
>
> Even with %handler and path being used, XML-INTO pukes at 1GB; with the
> default UCS processing.
>
> You can double that limit to 2GB by telling it to process the file as SBCS.
>
> https://www.ibm.com/docs/en/i/7.5?topic=documents-limitations-xml-parser
>
> There's been an idea out there for a while for IBM to increase the limit.
> https://ibm-power-systems.ideas.ibm.com/ideas/IBMI-I-1826
>
> Charles
>
>
> On Sun, Jan 19, 2025 at 3:50 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
>
> > Are you sure Dave?
> >
> > If you are using %handler you are processing the xml in chunks of the size
> > you define - surely the size of parts within any given object is not going
> > to exceed 16mb is it?
> >
> >
> > Jon Paris
> > Jon.Paris@xxxxxxxxxxxxxx