|
1) There is something like the reference field. It's called the distinct
type. Based on the glass is half full argument you may, or may not, like
it.
2) If you don't insist on renaming your fields (like prefixing them with
an abbreviation of the file name) then you can use the system cross
reference files to see every file that uses that field name.
Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
Jim Essinger <esinger@xxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/10/2003 01:43 PM
Please respond to Midrange Systems Technical Discussion
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
cc:
Fax to:
Subject: Re: Ok, where is it?
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
6905 Highway 95
Fruitland ID 83619
or
PO Box 730
Fruitland, ID 83619
208-452-4058 Extension 133
esinger@xxxxxxxx
------------------------------------------------------------
_______________________________________________
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.
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.