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





On Thu, 15 Mar 2001, Patrick Conner wrote:
> 
> Does this technique get passed the 65535A limitation? If so,
> can I define the character field as 1A so I don't have to
> keep up with size limitations? Also, if that is the case,
> can I define the variable tracking the size of allocated
> memory differently? (The limitation to a 10I 0 is 65535,
> right?)

Not sure what you mean by the limitation to a "10I 0 is 65536"?
You mean the highest value it can hold?

Here are the max values for the integer types (if memory serves):
      3I 0   127
      3U 0   255
      5I 0   32767
      5U 0   65535
     10I 0   2147483647
     10U 0   4294967295

 
> This is important to me because I currently working on a
> project where I'm receiving a XML document through sockets
> programming. I append each sockets read (packet) to a
> character hold variable. I'm told that once we start testing
> production responses the XML document may be very large,
> more than 65535A. If this technique gets passed that
> limitation I code it that way now. If not, I'm open to
> ideas.
> 
> > For that parameter, you might want to switch back to
> > passing a pointer
> > by value.  Instead of declaring a field for the buffer,
> > use ALLOC to
> > allocate data large enough for the buffer.
> > 
> > To handle the buffer data, you would use a based 65535A
> > field and
> > gradually walk its basing pointer through the data.

The limit for the length of an alphanumeric field with ALLOC
should be 16776704.   I suppose this might vary depending on
how much memory/disk space you have available on your system.
(Or how practical it is to load 1.5mb into a single variable)

I can't say that I've had a chance to try to push the limits
and see what happens :)




+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.