Re: RDi 9.5.0.3 Run SQL Scripts requires lib qualifier?

You need the JDBC settings in Run SQL Scripts to be set to naming=*SYS.

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles
Wilt
Sent: Tuesday, April 26, 2016 12:53 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.5.0.3 Run SQL Scripts requires lib qualifier?

You need the JDBC settings in Run SQL Scripts to be set to naming=*SYS.

That's the only way to use the LIBL to find unqualified tables.

With naming=*SQL, unqualified tables are implicitly qualified with your
user ID. Thus it looks for the file in MKOESTER.

Charles

On Tue, Apr 26, 2016 at 12:46 PM, Koester, Michael <mkoester@data-
east.com>
wrote:

I'm having a problem using this new feature for stub-testing the SQL
statements I code in my RPG. I asked this question yesterday under the

"Re:

[WDSCI-L] RDi 9.5.0.3 fixpack is now available!" thread, and am still
unable to make it work for me.
Here's how it goes:
1. I launch Run SQL scripts from RDi.
2. I set my library list for the job using "CL: Call

mkoester/nmslibl"

in the scripts window. (Thanks, Mike Jones. Didn't know I could do
that.) Message tells me library list was changed.
3. I check WRKACTJOB to see that the QZDASOINIT job that the Run
SQL scripts started for me indeed now has that library list. All's cool.
4. I paste in an sql script has a From-clause with an unqualified
file (which works nicely in STRSQL) and click Run-All. Message tells
me that file is not found in MKOESTER. Fine, but MKOESTER is not in
the library list, whereas GSTTSTLIB (where the file does exist) is the
first USR library in the list.
5. I add the "gsttstlib." before the file name (note that *SYS
naming is not in play here), and I get the expected result set.

So does this mean that I have to specify a library qualifier on every
file I use in my SQL statements in this environment?
Oh, and by the way, when I click stuff in the View menu (like view
joblog), my FireFox browser opens with the "Secure Connection Failed"
page. Not all that helpful, really.

I'm not quite there yet, but I'm trying...

Michael Koester