|
That sounds good, Marc. Question though. FMyFile UF K DISK ... C MyFileKey Chain FileFormat 99 In this case it is not obvious that FileFormat comes from the file MyFile. Unless you also use a naming standard for field formats and stick to it (we pretty much do here, MyFile01 would be the file format for MyFile, if it had 2 it would be MyFile02, etc..). Something like this could be designed with your specific shop standards, but it would not be easy for others to use this same program, or at a different shop, or for different applications on the same system. I'm sure JD Edwards uses different standards than other applications (and if I could think of another application I would mention it <g>). Would this project be worth the effort, however? For the time involved in designing and testing it (and you would definately want to test the bejeevies out of this thing!) it could only be used for one application. Unless you spend a lot more time in the design phase making it very customizable. Then again, it would be something I would also be interested in, but the system I inherited does not use standards for variable names. Regards, Jim Langston Zylka Marc wrote: > > 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. +--- | 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.