|
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
As an Amazon Associate we earn from qualifying purchases.
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.