@Joni: one point of criticism: one SRVPGM per view, not per file!!! Never
use a file (table) in any SQL statement.
The most important topic is: decoupling database access from database design
and implementation. Using SQL based DAOs for all access to the database
opens up the possibility to rearrange data, as long as you could provide
views with the same capabilities. (here you could win back performance,
you've lost by replacing native I/O with SQL).
@Dave: +1
- with one question: who is responsible for the state of the process?
D*B
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.