Re: Size Limits / know issues with XML-INTO?

On Mar 26, 2020, at 2:14 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

As mentioned...we are on 7.2

PTF Group Level
SF99776 12
SF99775 34
SF99769 1
SF99767 5
SF99766 3
SF99759 26
SF99747 17
SF99721 10
SF99720 19297
SF99719 162
SF99718 76
SF99717 9
SF99716 22

Charles

On Thu, Mar 26, 2020 at 11:45 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

Interesting - I do recall this coming up before ... have you checked your
PTF levels?

What release are you on?

On Mar 26, 2020, at 12:33 PM, Charles Wilt <charles.wilt@xxxxxxxxx>

wrote:

All,

Is there any kind of limits or known issues to the size of an XML doc

that

can be processed using the handler version of XML-INTO?

I've got some code...
XML-INTO %HANDLER(#PartMasterLine : allOk)
%XML(%TRIM(WpIfsFile) : %trim($OPTIONS));

The #PartMasterLine is a DIM(20) data structure...

I process about 600,000 elements (75-80% or so) successfully...

Then get a

RNX0353 - The XML document does not match the RPG variable; reason
code 5.

Cause . . . . . : While parsing an XML document, the parser found
that the XML document does not correspond to RPG variable "PARM" and
the options do not allow for this. The reason code is 5. The exact
subfield for which the error was detected is
"PARM(1).returnindicator". The options are "doc=file
path=ShowPartsMaster/ShowPartsMasterDataArea/PartMaster/PartMasterLine
case=any ns=remove datasubf=Data allowextra=yes allowmissing=yes".


5. The XML document contains extra XML attributes or elements that do
not match subfields.



Now, I've added some code and even changed the DIM(20) to a DIM(1) so
that I can better understand where the problem is..


Looking at the XML, starting from the last successfully processed
PartMasterLine, I don't see any problems...


And if I remove about half the data (from ~1.5GB to ~700MB) from the
beginning, the remaining data processes without issue...


I've tried "minifying" the XML and I get further into the doc, but
still get the error.


Also have tried new versions of the doc, same problem.


The one constant, the error gets thrown at approximately the 1GB mark
into whatever document.


I've got a case open with IBM, but I thought I'd through this out here
to see if anybody else has seen a similar issue.


We running 7.2 and are pretty up to date on PTFs.


Thanks!

Charles
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com