|
Is there any way to tell if a data field in a reference file is never referenced? We have a huge field reference file that needs cleaned up and other than starting with an empty file and adding data fields as they are referenced, I can't think of another way. It seems to be the only way but with thousands of fields it could be a tremendous task. Should you have one field reference file per system or if the system is large should the file be segmented into logical parts? Is it better to specify the total characteristics of the field in the reference file and not have it refer to another field that might refer you to another field. We also have a lot of fields that add and subtract bytes from the referenced field or redefine the field in some other way (from decimal to packed). Is the flexiblility worth the confusion if the system data fields are stable? Should the reference file be in alphabetical order or partitioned by function? Many thanks in advance for any and all advice. PS. We're only using RPG III so all names are limited to six characters and with thousands of data items to describe it becomes harder and harder to come with a unique name that is meaningful. +--- | 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.