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



IMHO the main problem is, that the default for the naming conventions in ACS
(an all other graphical tools) is *SQL and not *SYS.

With SQL naming conventions the library list is NOT searched for unqualified
specified tables, views or DDS described files.
Instead the default/current schema is searched.
If a current schema is not explicitly set, the schema with the name of the
current user is searched (if it exists).
In your case the ROB schema is searched (I assume you are working with the
user profile ROB).

BTW stored procedures and user defined functions are NOT searched within the
Default schema but within the Current path.
The current path is set with the SET PATH statement and can include a list
of schemas or even the special value *LIBL.
If the SQL Routines are located within the data library, the data library
must be included within the SQL PATH.

If you change the connection to *SYS naming conventions, the library list is
searched, and the library list is searched, and you won't get the "NOT FOUND
IN ROB" message anymore.

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: Freitag, 4. Oktober 2019 16:00
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: library list vs Run SQL Scripts

Version: 1.1.8.2

JDBC Configuration:
Default SQL Schema: Use library list of server job Library list: *LIBL

select *
FROM QSYS2.LIBRARY_LIST_INFO;
Shows GDIHQ as an entry.

select *
from SYSIBM.sqltables
where table_name = 'LOOKUP_TABLE'
;
Says it is in GDIHQ.

Here's the problem:
select Lookup_value_integer
from LOOKUP_TABLE
where Lookup_item = 'JOURNAL_SEQUENCE_NUMBER'
;
SQL State: 42704 Vendor Code: -204 Message: [SQL0204] LOOKUP_TABLE in ROB
type *FILE not found.
Why is it looking in ROB?



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.