We define a DeclareSoAndSoCursor procedure which may accept parameters that will be used as host variables in the Declare, and at the end of the procedure we perform the Open of the Cursor.
Generally this declare procedure is called just before the Fetch loop.
Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Birgitta Hauser
Sent: Wednesday, June 25, 2014 1:25 PM
To: 'RPG programming on the IBM i (AS/400 and iSeries)'
Subject: AW: SQL DECLARE CURSOR preference
The SET OPTION statement must be physically the first SQL Statement in your source code.
It is only used at compile time for retrieving compile and run options.
SET OPTION is never executed!
In other Programming languages include SQL itself, all DECLARE statement must be coded at the beginning of the source within the DECLARE SECTION.
In RPG there is only a single rule: The DECLARE Statement must be physically coded BEFORE the OPEN statement, independent in which sequence they are executed.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok) "What is worse than training your staff and losing them? Not training them and keeping them!"
-----Ursprüngliche Nachricht-----
Von: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im Auftrag von Gary Thompson
Gesendet: Wednesday, 25.6 2014 19:00
An: RPG programming on the IBM i (AS/400 and iSeries)
Betreff: RE: SQL DECLARE CURSOR preference
Thanks guys:
Charles and Vern, I'm thinking "SET OPTION has to be the first SQL statement" will be satisfied by either 1) first SQL in *Inzsr or 2) first SQL following D specs/Declares.
I'm leaning toward *Inzsr mainly because I think it "looks better" when using /Free.
Buck, I agree with all your points: I'm really talking about my "standards"
but I spend serious time trying to make my code easy to read and maintain so I took extra time this week to update my "standards" or perhaps "work habits".
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
midrange.com
