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



On 05-Jul-2017 14:51 -0600, Steve Richter wrote:
when I create a view with an unqualified view name the view is
created in the library of the first from file. So I qualify the
view name. But that is a problem when I want to create a test
environment.

I use "set schema testlib" to set the current schema. But setting the
current schema means the unqualified from file is searched for in
only that schema.

How to create a view in the current schema but still search the
library list for the from files?

I am using RUNSQLSTM to run the CREATE VIEW statements. Using *SYS
naming.

Tried setting DFTRDBCOL parm of RUNSQLSTM to the name of the data
file library. But that caused the unqualified view name to be
created in that library.

Unfortunately there is no SQL naming option of "screw ANS" per NAMING(*SYSTEM_FOR_BOTH_CREATE_AND_RESOLVE_NOT_JUST_THE_LATTER)

A Doc reference can be found in the following message:
(https://archive.midrange.com/midrange-l/201605/msg00765.html)[SQL *SYSTEM naming default schema rule?]

Of possible additional interest:
(https://archive.midrange.com/midrange-l/201605/msg00763.html)[SQL *SYSTEM naming default schema rule?]
(https://archive.midrange.com/midrange-l/201605/msg00771.html)[SQL *SYSTEM naming default schema rule?]

And more generally, for that message thread:
(https://archive.midrange.com/midrange-l/201605/threads.html#00749)[SQL *SYSTEM naming default schema rule?]


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.