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



Hello Zach,

I haven't tried what you're attempting, so please take everything I say in this message as an "educated guess".

I remember a similar discussion in this forum in the past, so I did a quick search and found this message:
http://archive.midrange.com/rpg400-l/200307/msg00108.html

That message states that the maximum allocation is 16mb minus 64k (16711680). You state that you have 1958x8566 = 16772228 bytes, which is, therefore, too big. Thus the problem!

I would suggest that you try allocating 8535 rows (16711680 / 1958) and see if that works. If it does not, then perhaps SQL has a smaller maximum than the ILE environment does? In any case, let us know what you discover.



Zachary Johnson wrote:
Hello all...



I'm doing a multiple row fetch.
I have a table with a row length of 1958 bytes. I'm fetching it to an
array that has 8566 elements defined as an external data structure over
that table. So the math says I have 15.9952431 Mb in the array. I'm
getting MCH0601 (space offset error) followed by CPF5257 then SQL0904
type 13 reason code 423 which is "Resource Limit Exceeded". So it tells
me to reduce the number of rows in the fetch. So I do that, I reduce it
to give me 15.8 Mb. It still errors. So I am just reducing the number
till it works. But my question is, is there some sort of magic number I
need to use for the number of rows to fetch to get right up against the
maximum records I can return? I am doing all of this under the
assumption that there is a max of 16Mb on a multiple row fetch.


~Zach

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.