|
Marc, This would be doable if you were willing to open and read every file referenced in the program. Each of the /COPY members, display file members, physical file members, printer file members, etc... Build a huge list that would look, basically, the same way the variable list does at he end of a compile. Where each variable is declared and used (multi dimentional array would work). Then it would a simple matter of reading through your array and looking for where a variable is defined and never referenced. Hmm.. thinking on it though, wouldn't it be MUCH simpler to just take the output from a compile and process that? You already have all the cross reference information you need in there nicely laid out for you. It tells you all the member names for each physical file, all the variable names, where each is defined/referanced, etc... Why reinvent the wheel? In fact, I seem to recall, I could be mistaken, that you can compile without actually creating the program. Have your program run a compile without building and then read the spool file and process it. Regards, Jim Langston Zylka Marc wrote: > > Jim, you have another good point. Personally, I don't use > file record names to read. This situation would also occur > if the file was setup as a Primary, Update file (UP) and there > is either an update or delete statement. > > I could get all of the records associated with the files in > the program and reference that information while we're checking. > > You're correct, it's getting more complicated. > > Thanks, > Marc Zylka +--- | 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.