Re: Launch Run SQL Scripts

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Hi Brian

I was told at a meeting with IBM that ACS is bundled with RDi as of 
version 9.5 - certainly, at least, the Run SQL Scripts feature - this 
was to ensure that the feature is available.

Printed output in RDi is also delivered using that feature of ACS.

I have tried the Run SQL Scripts feature - nice to select a statement, 
then take a menu option and be able to analyze it.

I've not tried to change the system it's connected to in Run SQL Scripts 
- it's in the plugin for the Windows client, I would assume it's in this 
one. But maybe it's tied to the connection you come from.

We're both making assumptions - I'm not at a connection to our system, 
nor on my work laptop, so can't verify any of this. Hope someone does.

Might be an opportunity for a COMMON requirement or RFE.

Vern

On 8/14/2016 4:22 AM, Brian Parkins wrote:
> Stuart, at this point in time you will get better results if you 
> download the IBM i Access Client Solutions (ACS) tool and install 
> separately. (It is effectively free and the latest version 1.1.6.0 has 
> some _very_ nice enhancements - including Visual Explain.)
>
> Within ACS, use System Configuration to define a (single) connection 
> to each server. (Shame we still cannot define multiple system 
> connections as per RDi.) When you invoke the Launch Run SQL Scripts 
> function within RDi it should pick up all the available ACS 
> connections; you can then select with the CONNECTION > CONNECT TO 
> DATABASE menu bar item.
>
> ACS is growing on me; a work-in-progress, but it is being improved 
> through a frequent update cycle.
>
> HTH.
> Brian.
>
> -----Original Message----- From: Stuart Rowe
> Sent: Friday, August 12, 2016 3:28 PM
> To: Rational Developer for IBM i / Websphere Development Studio Client 
> forSystem i & iSeries
> Subject: [WDSCI-L] Launch Run SQL Scripts
>
> I finally got around to trying to use this SQL script thing that only
> appears if you open a SQLRPGLE member.  I guess the way it is linked 
> to the
> source you are working on, that's valid.
>
> Anyway I searched the RDi help text and the web to no avail to find 
> out why
> I can only connect to ONE system but found nothing specific to any
> limitations.  When I need to test a statement, it is *never* to my
> development box, it's always targeting a test box where some valid data
> exists so I can see if the statement works or not.
>
> Anyone know how to get it to let me connect to other systems?  I have a
> connection defined (and connected) to another system but that one does 
> not
> appear in the list of systems available in the Run SQL Scripts tool.  I
> think it is not related to the RDi list of connections.
>
> For now I use the old ugly one embedded in iSeries Navigator.  It won't
> even remember my font selections (sigh).