× 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.



Hi Keith,

Write your XML to a stream file or user space. A user space has a 16mb limit. Stream files the limit depends on the file system, but they can be much larger than 16mb.

In either case you have to use doc=file. For a user space, the document name would be specified as /qsys.lib/xxxxxxxxxx.lib/yyyyyyyyyy.usrspc replace xxxxxxxxxxx with the library name, and yyyyyyyyyy with the user space name. For a stream file, just use the IFS path.

Good luck


Keith McCully wrote:
I see that at V6R1 the maximum character field length has increased to 16Mb.
Fantastic but that doesn't help me at V5R4.

Basically, I want to use the %XML BIF in conjunction with XML-SAX op code to
do some xml parsing on documents up to around 200K. I know I could drop the
document to disk but I want to keep in memory since I receive the data from
an MQ Queue into an array (200 elements of 1Kb). Loading from MQ at array
(not element) level works fine but the compiler complains if I attempt to
pass this array to %XML.

Is there a workaround to load more than the max of 65535 characters into
%XML?

I've looked at arrays and multi occuring data structures but didn't come up
with anything. Also, considered unnamed data structures as they have
sufficient length but unsure how to use without a handle?

Thanks

Keith


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.