Re: SQL question -- MIDRANGE-L

To add a little to this, the reason I've heard is that SQL generally knows nothing about libraries. IBM's knowledge base has a couple articles on this:

Using a Library List to Qualify Objects Used in SQL Statements and Stored Procedures http://www-1.ibm.com/support/docview.wss?uid=nas19d3e03ceba505db4862567ef0037496b&rs=110

SQL versus SYS Naming Affects Authorities for New SQL Objects
http://www-1.ibm.com/support/docview.wss?uid=nas1e4573a66d5a8378b862565c2007ca85b&rs=110

Client Access ODBC: Default Libraries Setting
http://www-1.ibm.com/support/docview.wss?uid=nas12554db904e5a601b862565c2007cc4b8&rs=110

I just did a search on the support site over "sql naming" - there's more there to be read.

HTH
Vern

At 07:12 PM 3/9/2005, you wrote:

On 10/03/2005, at 11:59 AM, Steve Landess wrote:

I have found that when using *SQL naming convention when using IBM's STRSQL,
the SQL interpreter will not find a file by using the library list.

This is normal, expected, and documented behaviour. *SQL uses a library of the same name as the user running the SQL statement to qualify unqualified references.

We get the exact same behavior when using a Java program with JDBC to execute the same SQL statement...


The same behaviour occurs in all SQL interfaces to DB2/400.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.