Re: Data string greater than 65k -- MIDRANGE-L

Appreciate the response

----- Original Message -----
From: Jon Paris [mailto:jon.paris@xxxxxxxxxxxxxx]
Sent: Friday, January 30, 2015 04:22 PM
To: Midrange-L Midrange-l <midrange-l@xxxxxxxxxxxx>
Subject: Re: Data string greater than 65k

Sorry can’t help a lot with that then as I am not familiar with the internals of XML Suite.

However, if Krengel do not place a limit on the size of an element then you should be able to define the receiver element as a DS - optionally based using dynamically allocated memory. Then use the same storage to write the “field” to the IFS if you need to do that to print it.

If all of Krengle’s underlying code is RPG then they may limit the element size to 64K - if they wrote in C or Java then who knows what the size is.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jan 30, 2015, at 3:12 PM, Alan Shore <ashore@xxxxxxxx> wrote:

Thanks Jon
It is received by XML, we are using the RPG XML suite software by Krengel Technology
It is suppose to be a pdf data string that we have to print to a local printer

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

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Friday, January 30, 2015 3:02 PM
To: Midrange-L Midrange-l
Subject: Re: Data string greater than 65k

64K is _a_ limit in V5R4 but it may not affect you - depends how you structure the data.

For example a stand-alone field defined as 100,000 long is too big as a single field. But an array of 100 elements each 1,000 long is fine.

Same kind of thing for a DS. Maximum size for a single element in a DS is 64K but you can define a DS array with as many 64K elements as will fit in 16Mb.

If you could tell us exactly how you will receive the data and what you want to do with it then we could offer practical solutions.

The response below talks about using XML-INTO but I don't see anything about XML in your original question so I'm a bit confused about that.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jan 30, 2015, at 1:44 PM, Needles,Stephen J <SNEEDLES@xxxxxxxxxxxxxxxx> wrote:

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.

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