|
Mitch,
There is one method that would be a short cut. GET DIAGNOSTICs can provide the total number of records in the data set after the open. That can control the number of records fetched in the FETCH INTO statement.
After the open you can code:
/exec sql
GET DIAGNOSTICS :row_count = DB2_NUMER_ROWS;
/end
Marvin
------------------------------
message: 8
date: Mon, 14 Sep 2015 18:17:00 +0000 (UTC)
from: Mitch Gallman <qtemp@xxxxxxx>
subject: Re: Loading arrayDS from sql select into statement?
I've used the following article several times as a reference: http://www.itjungle.com/fhg/fhg052009-story01.html
I've never had to do a select count prior to doing the fetch.
Mitch
On Monday, September 14, 2015 1:58 PM, "Koester, Michael" <mkoester@xxxxxxxxxxxxx> wrote:
Charles,
Would be nice if you could use SELECT INTO along with FETCH FIRST XXAfter getting the count (select count(*) into :resultCount from...), and declaring and opening a cursor, I can successfully use
ROWS...
? ? exec sql
? ? fetch MyCursor for :resultCount rows
? ? ? into :ArrayDS;
? ? ? ? ? ? ? ? ? ? ? ?
But there apparently are no shorter shortcuts.
Michael Koester
Notice: This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. This message may also contain Protected Health Information (PHI) and must be treated confidentially and handled in accordance with HIPAA and other federal and state privacy laws. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately and delete this e-mail (and any accompanying attachments).
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.