Mark,
Thanks for confirming my understanding of how they work.
Dean Eshleman
Software Development Architect
Everence
1110 North Main Street
PO Box 483
Goshen, IN 46527
(800) 348-7468 ext. 3528
(574) 533-9515 ext. 3528
[Join our Talent Network]<
http://www.everence.com/careers>
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mark Waterbury
Sent: Monday, November 1, 2021 2:06 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: Sql views across libraries and restoring from backup
This email originated outside of Everence. Do not click links or attachments unless you recognize the sender.
Dean,
The same "cross-library" issue that exists for DDS-defined LFs is also true for SQL INDEXes, but not for SQL VIEWs.
This is because a DDS-defined Logical File contains the equivalent of an SQL VIEW and an SQL INDEX, while with SQL they are separate and independent objects (due to IBM Db2 conforming to the ANSI standards for SQL, apparently.)
Hope that helps,
Mark S. Waterbury
On Monday, November 1, 2021, 01:33:53 PM EDT, Dean Eshleman <dean.eshleman@xxxxxxxxxxxx<mailto:dean.eshleman@xxxxxxxxxxxx>> wrote:
Hi,
I was wondering if SQL views that join two files across libraries have the same constraints as join logical files when it comes to what library they should be in so that a restore of the view works successfully. In other words you should place it the library that is restored last alphabetically so that both physicals are there when it is restored. I know that an SQL view shows up on the system as a logical file object, but I also know they have some differences from logical files. TIA
Dean Eshleman
Software Development Architect
Everence
1110 North Main Street
PO Box 483
Goshen, IN 46527
(800) 348-7468 ext. 3528
(574) 533-9515 ext. 3528
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l<
https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l<
https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com<
https://amazon.midrange.com>
Confidentiality Notice: This information is intended only for the individual or entity named. If you are not the intended recipient, do not use or disclose this information. If you received this e-mail in error, please delete or otherwise destroy it and contact us at (800) 348-7468 so we can take steps to avoid such transmission errors in the future. Thank you.
midrange.com
