Since service program name is part of the criteria that system uses to find procedure during execution time, it won't be ambiguous if those service program names are unique. Another word, same procedure name in two different named service programs should not be a problem at execution time. However, it is a problem at compile time, which bring up my question of why not allow qualify of service program in RPG program, much like using a method in an oo object?
-----Original Message-----
From: rpg400-l-bounces+lim.hock-chai=usamobility.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+lim.hock-chai=usamobility.com@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, October 11, 2007 7:38 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: [SPAM] RE: Rép. : [SPAM] Re: Service program not using LIBL
<clip>
Though, I personally would recommend a different approach: Don't use
duplicate names. In my environment, it's a policy that no two service programs on the system can EVER have the same procedure name exported.
That way, when you call a procedure, the service program it'll use is unambiguous.
</clip>
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Rép. : [SPAM] Re: Service program not using LIBL, (continued)
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.