|
Accept the incoming data as a CLOB. Define as an SQL Data type in your RPG similar to:
d parm_xml_in s SQLTYPE(CLOB:1048576)
this will create a 1M CLOB to read into your program. The SQL pre-compiler will break the variable into two parts...the data itself and the actual length of the data (the number of bytes used of the CLOB).
In the example, you can access these variable as parm_xml_in _data and parm_xml_in _len. The SQL pre-compiler automatically created these variables. The variable with the '_data' suffix can be manipulated using all (so far!) of the typical character manipulation methods and can be parsed by the XML-INTO opcode.
XML-INTO(E) target_variable %xml(parm_xml_in_data: 'allowmissing=yes
allowextra=yes case=any');
Steve Needles
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Alan Shore
Sent: Tuesday, January 27, 2015 10:18 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Data string greater than 65k
Hi everyone
Before I forget - we are on V5r4
Here is my problem
We are attempting to utilize a new courier and their process is to send a data string that is ultimately a pdf, but the data string is greater than 65k - which I believe is the limitation on this release I have tried to google anything to see if anything is available to get the end result so that it can be printed - but have not succeeded Does anyone have any tricks up there sleeve?
As always - any and all responses gratefully accepted
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
________________________________
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.
TRVDiscDefault::1201
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
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.