|
System can figure out if an index that has the same keys already exists and creates the new index as a "shared access path" index. Basically, it means that the new index is not eating up DASD, but instead using the existing index as base. Elvis -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rick.baird@xxxxxxxxxxxxxxx Sent: Tuesday, March 16, 2004 10:38 AM To: midrange-l@xxxxxxxxxxxx Subject: secondary access path owner on logical file. Hey all, I've got a joined logical that (I think) was duplicated from another library. they both have 3 files joined, the original ( WRKLIBA/JOINLF ) file description shows it's based on these files: WRKLIBA/FILE2 WRKLIBA/FILE2 MSTLIB/FILE3 the new one's ( WRKLIBB/JOINLF ) file description shows it's based on these files: WRKLIBB/FILE1 WRKLIBB/FILE2 MSTLIB/FILE3 (note, they both use MSTLIB/FILE3) but I noticed something weird - on the second LF (in WRKLIBB) has this under the third based on file: Based on file . . . . . . . . . . . . . . : FILE3 Library . . . . . . . . . . . . . . . . : MSTLIB Member . . . . . . . . . . . . . . . . : FILE3 Join secondary access path owner File . . . . . . . . . . . . . . . . : WRKLIBA/JOINLF Member . . . . . . . . . . . . . . . : JOINLF can anyone explain what this means? Is it only using the FILE3 portion of the access path of the WRKLIBA joined file? Thanks, Rick _______________________________________________ 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.
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.