×
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.
I'm calling a stored procedure that is processing
parameter values as XML documents. My issue is that one of the
documents passed in needs to allow for a great deal of data. While
testing in the interactive environment, I could pass it as a native
varying length value. From SQL, however, the maximum length is too
large for varchar, so I had to change the underlying RPGLE program to
accept CLOB values. Herein lays the problem.
When I pass the values as CLOB to the xml parser via xml-into, I'm
receiving xml parser errors. If I convert the CLOB values to native
varying length strings, the strings include extra characters at the
beginning which also cause parser problems.
Besides removing functionality by reducing the maximum length of the
data passed, does anyone have any suggestions on how to successfully
parse the CLOB data?
Tom Armbruster
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
