× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Best practice...don't do it :) . Updating a service program shouldn't
require recompilation of the callers.

You can change the PI in a manner that doesn't requires recompilation, by
adding NOPASS parms.

If you're using binder language and EXPORT(*SOURCE) on the CRTSRVPGM...
Then you can do stuff like, rename the export and add a new export with the
name. Existing programs will continue to call the old procedure, but when
recompiled, will start calling the new. (and get a compile error if the
parms don't match anymore)

If you absolutely want to force a recompile, make sure you're changing the
*SRVPGM signature. Anything that doesn't get recompiled will get a
signature mismatch (hard error).

The only other thing to watch out for is how your programs are bound to the
*SRVPGM. Is *LIBL used? Or a qualified name? Could be in either the
CRTPGM BNDSRVPGM(...) parm or in the binding directory entries specified in
BNDDIR()...).

Charles




On Tue, Nov 3, 2020 at 3:04 PM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Unfortunately, I have to modify an application that consists of 4-5 pgms
and a service program. I'll be changing the PI on most calls.

With programs I normally just make the change, stick them in a test
library to work out the bugs, then move them into a "ptf" type library.
That way if something happens I can simply remove the objects from the PTF
library.

Is there a trick to doing this when you're binding to a service program?

TIA
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.