|
My thoughts on this.
Doing a wholesale migration from DDS to DDL has some benefits but I am not
certain it would be the best use of your companies money at this time.
Doing all new development using DDL instead of DDS is a reasonable
approach.
Since you would be supporting a mixed environment one option would be to
put the DDL into the same QDDSSRC pf. While this may drive a purist mad I
believe it would make the transition for a new employee the easiest.
Hopefully, they would look for the DDS for the file, find the source
member and quickly realize that it's in DDL and they need to switch gears.
If they can't figure that out, you've made a hiring mistake.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.