× 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.



If you are working with SQL Naming conventions the library list is ignored,
you can only access database objects (tables, views and indexes) within a
single schema (Default/Current schema) unqualified.
If you need to access database objects from multiple schemas, you need to
qualify all database objects with the schema that are not located in your
default/current schema.
Alternatively you could generate an alias for each of these objects.

Stored procedures, User Defined Functions and user defined tables functions
are searched within the SQL path, where you can specify multiple schemas and
the special value *LIBL is allowed.
SQL path and library list can be differently.

If you are working with system naming conventions instead, the library list
is searched for all unqualified specified database objects (tables, views,
indexes, stored procedures, UDFs and UDTFs).

The default naming convention for green screen (STRSQL) is System Naming
conventions.
All "colored" interfaces (ACS, Squirrel etc) use SQL Naming conventions as
default.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Donnerstag, 28. März 2019 16:03
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Library lists vs Run SQL Scripts

BTW, many functions,
when ran in Run SQL Scripts,
do not seem to respect library lists for finding the function themselves.

cl: addlible routines;
select * from qsys2.library_list_info;
values MYFUNCTION(...);

But this works
values ROUTINES.MYFUNCTION(...);

Why is that?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

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

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.