Re: Duplicating SQL View logical file objects to another library -- MIDRANGE-L

I think the rules are the same as for our old-time logicals. Once created, you are stuck with whatever the compiler found for the references in a normal logical file. You don't need to qualify the PFILEs or JFILEs, either, but once created, they point to parent physicals in the library where created, and in the library list, if needed. IIRC. When you CRTDUPOBJ or RSTOBJ, this resolution needs to be done again. Boy the details of this are deep in the recesses of my garbage pail mind! I try never to have things cross over library boundaries, I guess, so I never deal with this very much anymore.

Maybe the Database Management or Database Programming manuals (whatever they are called these days) have the answers. I know I've seen the library references change in the file description of a view when I;ve moved or copied it.

HTH
Vern

At 04:39 PM 8/20/2004, you wrote:

What are the rules for duplicating SQL View logical file objects to another
library?

Example files:
  PHYFILE  - DDS Physical file
  LOGFILE1 - DDS Logical file
  LOGFILE2 - DDS Logical file
  LOGVIEW3 - SQL "Create View" file

All files originally reside in LIB1.  When I use CRTDUPOBJ to duplicate
these objects to LIB2, the DDS logicals files LOGFILE1 & LOGFILE2 are based
on LIB2/PHYFILE, but the LOGVIEW3 file is based on LIB1/PHYFILE.

I think I've found the answer, although I would appreciate confirmation from
others.  Looking at the DSPFD on the LOGVIEW3, even though the CREATE VIEW
statement used did NOT qualify the tables, the "SQL view create statement"
in DSPFD shows that the tables were qualified according to where the files
were found in the library list at creation time.

If so, total bummer!

db

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