Re: SQL Naming convention and the library list

[Alan Campin <alan0307d@xxxxxxxxx>]

Any iSeries SQL works that way. If you use SQL naming, it does not
know about the library list. It just looks in the default schema to
find anything.

If you use *SYS, it knows about library lists and searches the library
list for the job looking for the objects.

On Tue, Feb 10, 2009 at 4:36 PM, Jim Essinger <dilbernator@xxxxxxxxx> wrote:
> Just a quick question on SQL and the library list.  When using STRSQL
> to run some statements, I noticed that when using the SQL naming
> convention (lib.file) it does not seem to use the library list to find
> the file if the library is not specified.  When I go into F13 and
> change the session defaults to *SYS for the naming convention
> (lib/file), the files are found in the library list without specifying
> the library explicitly.
>
> Does this behavior also follow for the RUNSQLSTM command?
>
> Can I make SQL to look in the library list for files while using the
> SQL naming convention with STRSQL and/or RUNSQLSTM?
>
> Thanks!
>
> Jim
> --
> 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.