What does totally free format code have to do with *INZSR? You can program *INZSR in free format.
If some code needs to be run first I place the code there. If I have to initialize a field at runtime, it also goes there. If I can initialize the field at compile time it happens when declared.
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Clay
Sent: Wednesday, June 25, 2014 12:50 PM
To: rpg400-l@xxxxxxxxxxxx; rpg400-l@xxxxxxxxxxxx
Subject: Re: SQL DECLARE CURSOR preference
Does anyone still use *INZSR? We got rid of that early in this century
(which seems like so very long ago). Now, with the advent of totally
free format code, it really seems illogical (to me, anyway) to continue with it.
If you're using SET OPTION, then it has to be the first SQL statement
--physically-- in your code so it wouldn't belong in *INZSR anyway.
Just my $0.02.
Robert
"Contrariwise, if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic."--Tweedledee
On 06/25/2014 12:59 PM, Gary Thompson wrote:
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.
--
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
