Beginning with release 6.1 where clauses can be added to SQL indexes.
At release 6.1 those indexes were introduced primarily for native I/O. (Even
though indexes cannot be specified directly in an SQL statement they can be
used like any DDS described logical file in composition with native I/O,
i.e. an index can be specified within the F-Specs in RPG)
Beginning with release 7.1 and the sub-sequent technologie refresehes, the
query optimizer can more and more use and profit from those indexes. In
either way the query optimizer is smart enough to the access path stored in
any index or DDS described logical file.
The main reason why you should create new logical files (views and indexes)
with SQL is DDS is stabilized since at least release V5R3.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Gqcy
Gesendet: Tuesday, 16.4 2013 20:34
An: midrange-l@xxxxxxxxxxxx
Betreff: convert LF's to SQL - LF's have Select/Omit
I am reading about converting my DDS files to SQL...
Most of our Logical files are doing both, ordering and record selection...
However I am reading that I should _only_ create indexes for my ordering.
I see I and put in a where clause for my indexes, but should I?
Should I create SQL indexes just on ordering?
will the Logical files share the index, even though the logicals have
select/omit logic?
--
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.
midrange.com
