|
I think it's the file scope array File Scope Array (Qdb_Qdbfb): A file scope array is present for all database files. The number of data members, Qdbflbnum (page 34-76), contains the number of file scope array entries. Each entry contains a based on physical file name and, optionally, a record format name. Externally described physical files have one entry that names the physical file record format. The entry's file name portion is not used. Program described physical files have one entry for each data dictionary record format. The entry names the data dictionary record format. The entry's file name portion is not used. Non-join logical files have one entry for each based on physical file. The entry names the based on physical file and describes the logical file record format to use with that file. Join logical files have one entry for each based on physical file. The entry names the based on physical file. Only the first entry describes the logical file record format. SQL view logical files have one entry for each based on physical file. The entry names the based on physical file that will be either an externally described physical file or another view logical file. Only the first entry describes the logical file record format. You can locate this section with the offset, Qdbfos (page 34-80), in the FDT header section, Qdb_Qdbfh. At 09:16 AM 4/3/02 -0600, you wrote: >Folks: > >A co-worker of mine is trying to analyze a SQL View to determine the files >used in it's access path. > >He's been looking at the QDBRTVFD API, but cannot figure out what >information (if it's there at all) to retrieve. > >The information we're trying to get shows up on a DSPFD as follows... > >Access Path Description > Access path . . . . . . . . . . . . . . . . : Arrival > Files accessed by logical file PFILE > File Library LF Format > V4 DEVAXMF V6 > V5 DEVAXMF V6 > >Thanks! > >david > >-- >David Gibbs >Sr. Software Engineer / R&D / MKS Inc., www.mks.com >Lombard, IL, USA; tel: 630-495-2108; fax: 630-495-3591 >Build Better Software > > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >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.