When working with IBM i Navigator for generating the SQL scripts, you have
an option that can convert logical files into SQL Indexes and another option
that can create a view and an additional index for the key fields.
The new Stored Procedure GENERATE_SQL also has these options.
SQL handles logical files per default as views, because a view can be
accessed in SQL statements, while indexes cannot.
In SQL indexes are only used by the query optimizer and the statistics
manager.
BTW SQL indexes can be accessed like any keyed logical file with native I/O.
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 [mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Vicki Wilson
Gesendet: Thursday, 26.2 2015 01:03
An: midrange-l@xxxxxxxxxxxx
Betreff: Why does the system see the logical file as a view
Hi all,
We are starting to talk about modernization. We have older logical files
that have new record names, specify the fields in addition to a key for
sorting.
We were experimenting with generating an SQL script. We did not find the
logical with indexes - we found it with the views. I'm curious. Why does
the system recognize it as a view? And how do the key fields get handled
since they can't be included in the view?
Bonus question for anyone further down the modernization road. How are you
handling goodies like this?
Vic
--
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
