|
Reuse of code - or field definitions for that matter, since that is no more than a minor form of reuse of code - is the basis of ILE. is the basis of inheritence and therefore of things like Java. If an FRF already is to difficult to maintain, don't step into Java business. One thing might be important for creating a useable FRF, but that is for any programming task: Start with a general naming standardization before beginning with anything. Some legacy coding may not disrupt the overall logic. -----Oorspronkelijk bericht----- Van: nina jones <ddi@datadesigninc.com> Aan: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> Datum: zondag 27 september 1998 20:34 Onderwerp: Re: DB2/400 Rerference file >> I agreed with this up until my first exposures to this on a fairly large site with many applications, assorted third-party packages, and sites around two continents. Their two field reference files had become a mish-mash of stuff, usually every new application had a new section with all of it's fields including date fields even though the fields were typical of other fields already defined. At first I felt the site was unusual, with unusual solutions. But since then, on other sites, it appears to me that the idea of reference file is good in theory, but just not scalable to large installations. Of course I have seen very few installations, so perhaps other sites have other solutions; perhaps the scaling issue is normally resolved in ways not clear to me yet. > >we started out using them too, until it became unmanagable. so we quit using them, except for the limited ones we started with. > >i suppose it's ok if your applications are small, but if you have thousands of fields, over several hundred files, it is a lot to keep up with. at least for my simple brain... > >nj > >+--- >| This is the Midrange System Mailing List! >| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: david@midrange.com >+--- > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.