|
----- Original Message ----- From: "afvaiv" <afvaiv@wanadoo.es> To: "MIDRANGE-L" <MIDRANGE-L@midrange.com> Sent: Thursday, July 04, 2002 7:11 PM Subject: SQL using access paths NOT meant for his use ... > Am I correct interpreting SQL might be using our logicals "as convenient > paths" even though they are not in the BPCS job's library list ? > If the answer is YES, how can we prevent it without recompiling programs > (BPCS source is, of course NOT available) nor going into securing these > logicals are restricted access thru special authoritites, groups, etc? Yes. That is simply the way SQL works. If the optimizer finds an index it can use to improve the access to the data, it will use it. You WANT it to do this. The SQL statement gets the data. The indexes, whereever they may be, are used to tune the performance, not limit access. The historical nature of logical files is that they are both a view and an access path combined. SQL does not treat them as such. As for the logicals not having all the data, so what? The data is not retrieved through the "view" of the logical file, only the access path is used. The data is still retrieved from the physical file through the SQL statement. =========================================================== R. Bruce Hoffman, Jr. -- IBM Certified Specialist - iSeries Administrator -- IBM Certified Specialist - RPG IV Developer "There is a crack in everything, that's how the light gets in. - Leonard Cohen
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.