×
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.
Pending a[s likely resolution to the concern by a] change to the
SQL "naming" option, just library-qualify the object references in
the SQL statements. So for example instead of issuing the request
"SELECT * FROM MYFILE" for which the SQL infers the request to have
been "SELECT * FROM MYUSER.MYFILE", issue the request "SELECT * FROM
THELIBNAME.MYFILE". FWiW: Depending on the interface established by
WDSC for its connection\session, the option may exist to just issue
the "SET CURRENT SCHEMA THELIBNAME" before invoking SQL with
unqualified name references, to effect the library name as the
default for those unqualified non-path object references.
Regards, Chuck
GKern@xxxxxxxxxxxxxxxx wrote:
I recently discovered the data perspective and want to use it for
adhoc sql, but when I run a simple select statement, it returns
errors saying the file isn't found in 'library' - and the error
text shows the library as being my user id.
I tried qualifying the library name but that didn't work either.
How do I get it to recognize the proper location of the data
file?
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.
midrange.com
