|
Alan,
Doing all the memory allocation and making a "manual array" (i.e. not
using DIM() but using BASED() and manually setting elements via pointer
math) may seem simple to you (and it does to me as well) but it is not
within the skill set of most RPG programmers.
If RPG can support a large enough array with the standard DIM() keyword,
then I don't see why you'd want to do it this way??
Also, when you say 'RPG can only address 16MB of storage', I hope you
actually meant that a single variable can only use 16MB of storage, and not
that you really think RPG can only address that much storage?!?!
Also, the OP said he needed 50 records of 400 bytes in size... so all of
this is purely us chatting... nothing anywhere near 16mb is called for
here.
On 12/30/2014 4:53 PM, Alan Campin wrote:
Unless I am highly mistaken, RPG can only address 16MB of storage but itThis is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
is
so easy to circumvent that it really means nothing.
1. *TERASPACE the program.
2. Create a data structure based on a pointer.
3. Dynamically extend the array. (A new lines of code).
4. Use QSORT to sort it.
5. Read it back out via pointer.
It would be easy enough to make my XVSRTQ a teraspaced program instead of
using a user space for storage but as far as I know no one as every used
my
Dynamic Sort API. Only issues I have seen there is mixing models.
On Tue, Dec 30, 2014 at 3:38 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:
Good point Scott. I’m fairly certain that the 16Mb still applies. I’ll
do
some checking.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Dec 30, 2014, at 5:35 PM, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
wrote:
Jon,array
Is this true even if you use STGMDL(*TERASPACE)?
-SK
On 12/30/2014 4:28 PM, Jon Paris wrote:
Arrays are now only limited by the 16Mb single item storage limit (asof V6). That also means that dynamic arrays can’t get you a bigger
unless you use terraspace.
list
Size limit is 16Mb / %Size(arratElement) - no hard limit.This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
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.
--
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.