|
Actually I don't have a need now to change the interface but I am trying to "sell" my shop on using service programs and this issue came up. We use hawkeye now to tell where a file or program is used but there seems to be no way to find out if a program uses a particular procedure from a service program. I agree that changes to the interface should be made in such a way to minimize the impact on the system but if the change must be used by current users of the procedure then backwards compatibility would not be wise. From what I can tell so far, searching the source appears to be the most reliable method. Any information you have or can point me towards to assist my selling efforts would be greatly appreciated. Thanks Chris Bougher Scott Klement <klemscot@klements To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> .com> cc: Sent by: Subject: Re: Display Where Procedure Is Used rpg400-l-bounces@m idrange.com 03/31/2004 04:23 PM Please respond to RPG programming on the AS400 / iSeries Hi Chris, > Is there a way to tell what programs use a procedure in a service program? Personally, I'm a proponent of the "new way" of handling things, which is to make sure that service programs are ALWAYS backward compatible. In that situation, you never have to search out and find where each proc is used. If you're interested in this approach, give me a bit more detail on what's changing in your interface, and I'll suggest how you might do it in a backward-compatible manner. However, if you do want to do it the "old-fashioned" way and change/recompile every program that uses the service program, the FNDSTRPDM utility can be used to search the source code that's stored in source PFs, and QShell's grep utility can be used to search source files stored in the IFS. (Though, grep also works on source PFs, I prefer FNDSTRPDM) > We have a service program with multiple procedures and would like to be > able to get a list of programs that use one of the procedures to change the > interface without having to look through all the programs that reference > the service program. This isn't any different from changing the size of fields in an externally defined file. You need to search out where these procedures are called, modify the code to use the new interface, and recompile the programs. If you're going to break backward compatibility, I recommend making sure that the service program's signature changes as well, so that if you miss any programs they won't run (just like a record format level check on a file) _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.