|
O.k. I'm kind of hitting a saturation point wrt service programs.
One thing I want to be sure of is to avoid having to recompile programs
that call procedures in a service program unless absolutely necessary.
Early on in my testing, I ran into MCH4431 - Program signature violation:
Cause: The source program AR8554R specifies a signature
X'FCC376CD114571CD674FE1584C1D6429' which is not supported by service
program UT9800.
Recovery . . . : The service program interface has changed. Re-bind
source program AR8554R.
Since I was doing a lot of development work in both programs, I didn't
investigate what changed, especially since this is brand new development
and the service program is not yet being used in production. I just
recompiled AR8554R and went on my merry way.
I've learned that I should add new exports only/always to the end of an
existing export list in my binder source. My understanding is that, by
doing so, programs that call existing procedures in the binder source do
not need to be recompiled. Correct?
Also, if I change an existing procedure in a service program but do not
change the procedure interface, do I understand correctly that I won't need
to recompile any programs that call that procedure?
Is there a go-to reference for this topic?
- Dan
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
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.