|
I don't think you will be creating a view or index. What I think will happen is that you will change your HLL from reading a traditional file to using a SQL cursor. The first few times you will run this in debug in order to have the job log suggest various indexes to create over some of the files. Now, you won't name these new indexes, per se, in your hll program, or even in any of the cursors you use in the hll. SQL will use the new indexes 'under the covers'. I too find it a weakness that SQL does not allow the combination of a view and an index, like a join logical file does. I was hoping that, with the stupid limitation in DDS that you can only have keys from one file that SQL would overcome this limitation. But after listening to the siren's song for a long time you believe that this lack is only important if you want to create the file with SQL, but access it using traditional HLL methods. If you adopt the SQL model of separating your indexes from your views, and accessing the data via SQL versus HLL, then it works. And for the simple stuff that hll's excel in, like reading a single row then just create that table with a primary key. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.