×
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.
Just so I understand, SQL naming is a waste of time. With SQL naming you
only work in one schema at a time. Unless you qualify your references.
When creating a view the unqualified specified database objects are
resolved
from either the library list (System Naming) or the current/default schema
(SQL Naming).
I am finding that once you "SET SCHEMA" the code runs as if SQL naming is
in effect. All unqualified references look in the current schema only.
If the view itself is not qualified it is created in the QGPL library
(System Naming)
just to clarify, an unqualified view is created in the library of the first
from file. Unqualified tables or routines are created in the current
library.
So, you need to qualify.
which is a real pain in the neck. How to code a CL procedure that will
setup a test environment when multiple libraries are being used?
I have an INFOR production data library. And an INFOR test data library.
Then a production library which contains custom written programs, views and
even data tables. The code that creates a view is stored in a source
member and is run using the RUNSQLSTM command. That create view code
qualifies the view being created to place it in the production custom
library.
Now to create a custom test library I would like to run each of CREATE VIEW
statements. But I cannot because the view name is qualified to the custom
production library.
midrange.com
