|
Jim, Due to the standards that we are using, this should not be a problem. All screen fields that we use begin with an '@'. I don't see any reason for declaring the same field in the 'D' specs. Basically, I'd want to read each 'F' spec and check if the file is referenced in the program and any /COPY members. After that, read each 'D' spec and see if those variables are used in the program and /COPY members. If no reference, either delete it or print a report. As mentioned by David, I could write it myself whenever I get some time. I may just do that. Marc Zylka, 228-5267. -----Original Message----- From: Jim Langston [mailto:jimlangston@conexfreight.com] Sent: Friday, December 01, 2000 11:49 AM To: RPG400-L@midrange.com Subject: Re: RPG/IV Source Utility Marc, To do what you are asking is no simple matter. You have to remember that programs use files which use variables, and display screens which use variables, and data structures and external declarations and it is not always obvious where a variable is being used, because it's not always in the RPG program. I came across a variable I thought was not being used in one of my programs, but before I deleted the declaration I did some tracing and found that it was being used in a very round about way in a display file I was using. It is not an easy matter when all the source code is not available in one file. There may be a tool to do this, but I doubt it. Regards, Jim Langston +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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-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.