|
On Wed, 12 September 2001, Buck Calabro wrote: > Said much better than I could have. Here's what I'm doing. We're doing a > major overhaul of our product, and want to verify that the object code at > the customer sites matches the code we have here on the development box. > It's possible that source was shipped to the customer and changes made > onsite. The approach we decided on was to compare the source member change > date/time. That's easy for OPM programs: DSPOBJD *SERVICE to an outfile and > a simple query to find the differences. ILE programs don't fit that > pattern. I need to write a routine that uses QBNLPGMI to get that > information for all the modules in the ILE program. And you are (of course) aware of the help text for the MODULE() parameter of UPDPGM that states: "If the library of the module being replaced is different from the library of the replacing module, the module's library after the update will remain the library the module was in when the program was first created." That is, for ILE programs, be very careful how you handle module info from program information. However, source file info seems generally okay. Tom Liotta -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 Fax 253-872-7904 http://www.400Security.com ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/
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.