Re: Maintaining Service Program signatures

Buck

I agree that many local installations has a "change one, compile all"
strategy,
but if you as I depend on other Open Source Projects that strategy dosn't
fit in
when I build up a product stack I havn't control of.

Components in the stack has to be backward compatible as far as it is
possible, it is a matter of stability and good Change Management.

If you look at my basic product stack here:

http://184.172.184.159/~servus/pextdrupal/sites/all/themes/theme548/images/powerEXT_Core.png

there is a lot of service programs that depend by each other and
by using signatures it is a very stable platform and it does ensure that
most modules can be upgraded without dependency of each other.

Since it is quite simple to implement, I don't se any reason not to
implement the strategy in legacy code if any wants to use service programs,
that many IBM I shops don't.






On Wed, Feb 20, 2013 at 9:02 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 2/20/2013 2:07 PM, Henrik Rützou wrote:

To make a simple example, lets say I have som CGI programs that is build
on My Framework V1.6 that run on lowest level Core V4.3 I have an initial
stack

1. My CGI program
2. Framework V1.6 service programs
3. Core V4.3 service programs

You can install any Core V4.3+ without recompilation in that environment,
if you wish to install Framework V1.7 you will at least have to install
Core V4.8
first because Framework V1.7 uses Core V4.8 as lowest level, but you

could

also install Core V4.11 and Framework V1.7 - but still without

recompiling

the
CGI programs (ad. 1)

This is what those signatures are for! I wonder how many non-vendors
have interlocking service programs like this? I don't, because if my
equivalent of Framework needs a new Core subprocedure, they are always
compiled together :-)
--buck
--
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: 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.