×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Seems like you are making this more complex than it needs to be.
When you create an index in SQL, it creates a keyed logical file with
all the fields in it. In a sense this is a place holder but the AS/400
needs something to hold the SQL index.
From within SQL, it looks like an index. From outside, it looks like a
logical file.
Same thing is true for a view. Create a view in SQL and you get an
un-keyed logical file.
Both can be opened in an RPG program.
Of course, the question is why would you want to do this? You can just
access the data through an SQL statement.
Also, if you have an SQL index created and you re-create a logical with
the same keys, the AS/400 will reuse the SQL index and not create a new
index.
IBM recommends doing this because it increases performance of indexes
since SQL index are several times faster than DDS indexes so in a sense
you can have both.
Create an SQL index and then create a DDS logical that uses the SQL
index.
As an Amazon Associate we earn from qualifying purchases.