|
Vern, James, Raul, Richard, (& all)
Thank you for your replies. I guess I will have to start defining my files using SQL scripts. I just wish IBM would keep DDS current with the SQL functionality. I like to use field reference files created in DDS, and then create all my files from the field reference. That way when a field size has to change, one change in the reference file, and a recompile of file (or change file) and recompile of programs, and the change has been propagated through the whole system. I don't like having to search the script for every time that field appears, and having to trust/hope/pray that I find them all, and then recreating the whole mess.
I like the source reference in DDS. I have all my generic fields defined 1st in the reference file, then reference them in the source. 1 change to the generic field, and the rest of the fields referencing the changed field are changed. Great for maintenance. I guess I don't see the advantage to SQL scripts, other than there is functionality that DDS no longer offers. How hard would it be to add keywords for some of the SQL functionality, and keep DDS caught up with SQL functions?
Thanks again for the responses. It does help. If anyone has good maintenance tips for SQL scripts (maybe similar to the Reference file concept) I would love to hear from you.
----------------------------------------------------------
Jim Essinger Senior Programmer/Analyst Student Loan Fund of Idaho
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.