Continuation of question:
@Tom - Thanks for answering with a question. Let's me layout the whole picture.
We're running as400 iseries R5V3M0.
99% of all AS400 work is done in RPG.
But, we're now tasked to create an executive portal using Sharepoint which contains dozens of very high-level roll-up type reports.
The reports often require summing dollars & tons & quantities from 10,000-20,000 records from tables holding 2-4 million rows and requiring joins across 3-4 different tables.
Our first attempts were to build SQL Views. Views are DONE, they run, and produce accurate data ... but ...
... the nature of a view is to be rebuilt every time the query is called ... SLOW ....
So now we're looking at DDS logical tables. If our logical tables are built WITHOUT the DYNSLT option, then IT IS OUR UNDERSTANDING the view is (in essence) kept in a pre-built constantly maintained state, thus eliminating the need to build the 10,000-20,000 record view each and every time the roll-up query is run.
So, we're trying to duplicate (rather complex multi-table-join roll-up record extraction) from SQL logic into a Logical DDS definition. Thus, some of the "strange" questions about DDS Logicals I've been asking.
Question: IS OUR UNDETSTANDING about life cycle of Logical Files correct? Are logical files kept in a pre-built constantly maintained state?