OR you can store your SQL in a compile time array (if you code dynamic SQL) high light the statement and then run the Launch Run SQL Scripts.
You don't need the selected text to be linked to a EXEC SQL statement.
Thanks, Matt
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Tuesday, April 26, 2016 7:11 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.5.0.3 fixpack is now available! (ACS integration explained)
Aaron,
Good Points!
I only want to mention that you can use Rectangle selection Alt+R. Use alt+U to unselect.
That way, you can avoid the "Exec sql" and the antiquate Punch-Card-Sequence.
-Ken Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Aaron Price
3. Run SQL Scripts doesn t ignore the EXEC SQL statement, so the
fact that that is copied and requires removal is another minor annoyance. Since this statement is not valid SQL, can it be removed when copying to Run SQL scripts?
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
midrange.com
