RE: Magic Number

[<Rick.Chevalier@xxxxxxxxxxxxxxx>]

Zach,

I do a lot of multiple record fetching and the formula I use is (128 *
1024)/recordlength = number of rows to fetch, rounded down.

This is based on the buffer size for a SQL table read. The last I saw
the buffer is 128k. I divide that by the record length and round down.
So far I haven't run into any size issues.  I haven't tried Scott's
suggestion so it might be possible to fetch more rows than I normally
do.

HTH,

Rick

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Zachary Johnson
Sent: Thursday, June 26, 2008 2:25 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Magic Number

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.

Privileged and Confidential.  This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information.  If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail.  You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.