× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.