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


  1.  Home
  2. RPG400-L
  3. February 2024

Re: Loading Variable Array From SQL Caveat

That 16M limit has shown up a few places in more recent releases. It's the size of a segment on desk, as I recall.

The 7.4 (and up) doc still says the number to fetch is an integer (internally, I surmise) or a 0-decimal numeric that gets converted to an integer. Signed integer goes up to 2meg, so it seems the limit is solely by size, not by count. Divide 16Meg by the length of the returned row, that's your max


Cheers
Vern


On Fri, 16 Feb, 2024 at 5:21 AM, Chris McNierney via RPG400-L <rpg400-l@xxxxxxxxxxxxxxxxxx> wrote:


To: rpg programming on ibm i
Cc: Chris.McNierney@xxxxxxxx
This is the 7.3 text for multiple-row-fetch:

“The value must be in the range of 1 to 32767 and the total size of the rows, excluding LOBs, must be less than 16M.”

It was changed to this for 7.4+:

“The total size of the rows, excluding LOBs, must be less than 16M.”

My guess is that the limit was removed in a TR for 7.4+.

Chris

From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx>> on behalf of Alan Campin <alan0307d@xxxxxxxxx<mailto:alan0307d@xxxxxxxxx>>
Date: Friday, February 16, 2024 at 2:38 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx<mailto:rpg400-l@xxxxxxxxxxxxxxxxxx>>
Subject: Re: Loading Variable Array From SQL Caveat
Boy, that is wild. Why didn't they do that years ago? SQLERRD is an integer
so that means it is just an internal value of some kind. There is no
difference in the compile code.

I couldn't find anything in the release announcement announcing this.

On Thu, Feb 15, 2024 at 3:45 PM Marco Facchinetti <
marco.facchinetti@xxxxxxxxx<mailto:marco.facchinetti@xxxxxxxxx>> wrote:

Not at V7R5, take a look at my previous post.

The last fetch in the loop loads 53736 elements.

HTH
--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


Il giorno ven 16 feb 2024 alle ore 00:34 Alan Campin <alan0307d@xxxxxxxxx<mailto:alan0307d@xxxxxxxxx>>
ha scritto:

He has more than 32767 records. SQL max.

On Thu, Feb 15, 2024, 3:16 PM Robert Rogerson <rogersonra@xxxxxxxxx<mailto:rogersonra@xxxxxxxxx>>
wrote:

Sam, I agree with Marco. After exec sql fetch from csz_cur for
:cszCount
rows into :csz_a; you should be looping through the array not the
cursor.

Rob

On Thu, Feb 15, 2024 at 4:55 PM Marco Facchinetti <
marco.facchinetti@xxxxxxxxx<mailto:marco.facchinetti@xxxxxxxxx>> wrote:

Hi Sam, sorry maybe it's late but I don't understand why you need a
fetch
inside a loop.

HTH
--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


Il giorno gio 15 feb 2024 alle ore 22:13 Sam_L <
lennon_s_j@xxxxxxxxxxx<mailto:lennon_s_j@xxxxxxxxxxx>

ha
scritto:

What am I doing wrong in the code below? Each subsequent fetch from
the
cursor seems to load into element 1 of the array.

(There are 42,654 rows to be loaded. Granted, this is an unusually
large
number to load, but I'm accessing it by index to build random test
data
and loading rows one at a time works great, so I'm not stuck. But I
am
curious about this and why I can't get this to work.)

Incidentally, snd-msg is a great replacement for dsply in these
situations--thanks Marco.

After a run of the code below, these are the results:

Allocated default: 100
Allocated after *alloc: 42755
"fetch for 'n' rows" : 42654
Elements before fetch: 0
After First Fetch. Elements: 42654. SQLSTATE: 00000. Allocated:
42755
After Loop Fetch. Elements: 0. SQLSTATE: 02000. Allocated: 42755
Final Elements: 0. Allocated: 42755

If I set rows to fetch to 25,000 these are the results:

Allocated default: 100
Allocated after *alloc: 42755
"fetch for 'n' rows" : 25000
Elements before fetch: 0
After First Fetch. Elements: 25000. SQLSTATE: 00000. Allocated:
42755
After Loop Fetch. Elements: 17654. SQLSTATE: 00000. Allocated:
42755
After Loop Fetch. Elements: 0. SQLSTATE: 02000. Allocated: 42755
Final Elements: 0. Allocated: 42755

This is the demo code:
**free
ctl-opt Option(*nounref: *nodebugio: *srcstmt);
dcl-c SQLSUCCESS '00000';
dcl-c SQLNOMOREDATA '02000';
dcl-ds csz_a dim(*auto : 50000) qualified;
zip int(10);
end-ds;
dcl-s cszCount int(10);
exec sql set option closqlcsr=*endmod;
exec sql declare csz_cur cursor for
select zip
from lennons1.csz where length(trim(city)) <= 20;

// Allocate enough memory/elements
exec sql select count(*) into :cszCount
from lennons1.csz where length(trim(city)) <= 20;
snd-msg ('Allocated default: ' + %char(%elem(csz_a : *alloc)));
%elem(csz_a : *alloc) = cszCount + 1;
snd-msg ('Allocated after *alloc: ' + %char(%elem(csz_a :
*alloc)));
// cszCount = 25000; // pick a number, e.g. 25,000
snd-msg ('"fetch for ''n'' rows" : ' + %char(cszCount));
snd-msg ('Elements before fetch: ' + %char(%elem(csz_a)));
exec sql open csz_cur;
exec sql fetch from csz_cur for :cszCount rows into :csz_a;
snd-msg ('After First Fetch. Elements: ' + %char(%elem(csz_a))
+ '. SQLSTATE: ' +SQLSTATE+ '. Allocated: '
+%char(%elem(csz_a : *alloc)));
dow sqlstate <> SQLNOMOREDATA;
exec sql fetch next from csz_cur for :cszCount rows into
:csz_a;
Snd-msg ('After Loop Fetch. Elements: ' +
%char(%elem(csz_a))
+ '. SQLSTATE: ' +SQLSTATE
+ '. Allocated: ' + %char(%elem(csz_a : *alloc)));
enddo;
snd-msg ('Final Elements: ' + %char(%elem(csz_a)) + '. Allocated: '
+%char(%elem(csz_a : *alloc)));
return;


On 2/14/2024 1:41 PM, Marco Facchinetti wrote:
V7R5:

Dcl-Ds wIn qualified dim(*auto:60000);
Code char(6);
State char(1);
End-Ds;

Dcl-s Limits date dim(3);
Dcl-s wD date;
Dcl-s i int(10) inz(0);
Dcl-s MaxRec int(10) inz(0);
Dcl-s MaxEle int(10) inz(0);

EXEC SQL SET OPTION COMMIT = *NONE;

Limits(1) = d'2000-01-01';
Limits(2) = d'2005-01-01';
Limits(3) = d'2010-01-01';
MaxEle = %elem(wIn:*max);

for i = 1 to %elem(Limits);
wD = Limits(i);
EXEC SQL DECLARE C1 INSENSITIVE SCROLL CURSOR FOR
Select usrcode, userstate
From myfile
Where activesince < :wD;
EXEC SQL OPEN C1;
EXEC SQL GET DIAGNOSTICS :MaxRec = DB2_NUMBER_ROWS;
EXEC SQL FETCH C1 FOR :MaxEle ROWS INTO :wIn;
snd-msg 'Sqlcod: ' + %char(sqlcod)
+ ' Elem: ' + %char(%elem(wIn))
+ ' Rec: ' + %char(MaxRec)
%target(*caller:1);
EXEC SQL CLOSE C1;
EndFor;

*inlr = *on;
return;

Returns:
Sqlcod: 0 Elem: 27818 Rec: 27818
Sqlcod: 0 Elem: 39214 Rec: 39214
Sqlcod: 0 Elem: 53736 Rec: 53736

And it's correct.

HTH
--
Marco Facchinetti


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l<https<https://lists.midrange.com/mailman/listinfo/rpg400-l<https>://lists.midrange.com/mailman/listinfo/rpg400-l><http://lists.midrange.com/mailman/listinfo/rpg400-l>>
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l<https<https://archive.midrange.com/rpg400-l<https>://archive.midrange.com/rpg400-l>.<http://archive.midrange.com/rpg400-l>.>

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription
related
questions.


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l<https<https://lists.midrange.com/mailman/listinfo/rpg400-l<https>://lists.midrange.com/mailman/listinfo/rpg400-l><http://lists.midrange.com/mailman/listinfo/rpg400-l>>
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l<https<https://archive.midrange.com/rpg400-l<https>://archive.midrange.com/rpg400-l>.<http://archive.midrange.com/rpg400-l>.>

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription
related
questions.


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l<https<https://lists.midrange.com/mailman/listinfo/rpg400-l<https>://lists.midrange.com/mailman/listinfo/rpg400-l><http://lists.midrange.com/mailman/listinfo/rpg400-l>>
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l<https<https://archive.midrange.com/rpg400-l<https>://archive.midrange.com/rpg400-l>.<http://archive.midrange.com/rpg400-l>.>

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription
related
questions.


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l<https<https://lists.midrange.com/mailman/listinfo/rpg400-l<https>://lists.midrange.com/mailman/listinfo/rpg400-l><http://lists.midrange.com/mailman/listinfo/rpg400-l>>
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l<https<https://archive.midrange.com/rpg400-l<https>://archive.midrange.com/rpg400-l>.<http://archive.midrange.com/rpg400-l>.>

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
questions.


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l<https<https://lists.midrange.com/mailman/listinfo/rpg400-l<https>://lists.midrange.com/mailman/listinfo/rpg400-l><http://lists.midrange.com/mailman/listinfo/rpg400-l>>
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l<https<https://archive.midrange.com/rpg400-l<https>://archive.midrange.com/rpg400-l>.<http://archive.midrange.com/rpg400-l>.>

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
questions.


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l<https<https://lists.midrange.com/mailman/listinfo/rpg400-l<https>://lists.midrange.com/mailman/listinfo/rpg400-l><http://lists.midrange.com/mailman/listinfo/rpg400-l>>
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l<https<https://archive.midrange.com/rpg400-l<https>://archive.midrange.com/rpg400-l>.<http://archive.midrange.com/rpg400-l>.>

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

As an Amazon Associate we earn from qualifying purchases.

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