Re: Connection in RDi Run Scripts...

Thanks Buck and Matt. I installed ACS but it requires PTFs in order to be fully usable. I am able to use Run SQL Scripts from RDi so I'll try that when needed.

Unfortunately I have to wait for the PTFs to get the rest of the functionality for iNav.

Thanks for your information,

Rob

On 4/26/2016 3:17 PM, Buck Calabro wrote:

On 4/26/2016 3:01 PM, Robert Rogerson wrote:

The Launch Run SQL Scripts in RDi seems useful. What I found
interesting was that the connection defaulted to (I assume) the
connection (and therefore the database) for the source which is active.

I have a short cut pinned to my task bar to start a Run SQL Scripts
(cwbundbs.exe) session but I couldn't see how specify the connection
(database). But now that I see this done in RDi I'm thinking there must
be a way.

Does anyone know how I can specify the database when calling cwbundbs.exe.

cwbundbs.exe is part of IBM i Access for Windows, which is at end of
life and not getting enhancements. The replacement for the Windows
client is Access Client Solutions (ACS), and RDi 9.5.0.3 fires the SQL
Scripts part of ACS.

So you can't easily connect the Windows SQL script to RDi via this newly
delivered function.

As I understand it, lighting off ACS SQL Scripts from RDi does NOT read
anything from the connection. The only thing RDi does is start ACS SQL
Scripts and then paste the currently selected text into the newly opened
(empty) script window. There's no implicit database connection in use;
we need to specify it one way or another:

cl:chglibl lib1 lib2 lib3;
cl:call setmylibl;
set schema prodlib;