I am reminded that we do not use service programs as they use dynamic calls and
that would mean the same as going back to RPGIII.

RANT (but i don't care):

I don't really know the problem at hand, and i really don't care,
but remarks like this ("we don't use serviceprograms because ...
it's like RPGIII or whatever") is really the biggest problem our
platform has.

People (developers) who are simply not capable, or just don't want to understand.

Fact is, with a modular approach, or an OO approach, where the software is split into several
components with interdependencies, if you don't know what you're doing you can make a really
big mess out of it. Powerfull tools are only productive in the hands of capable developers.
The one advantage of having one source --> one program is that it's simple (too simple i mean).
If something goes wrong, the one source has all the info, although it can be like 10000 lines,
but still. The possibilities to make a mess are also limited.



From: David.FOXWELL@xxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Date: Wed, 27 Feb 2008 15:07:49 +0100
Subject: Service programs suck



-----Message d'origine-----
De : David FOXWELL
Envoyé : mercredi 27 février 2008 14:54
À : 'Websphere Development Studio Client for iSeries'
Objet : Service programs suck

Hi everyone,

We have this problem with 1 procedure that calls another that calls another :


Module 1 Procedure 1 calls Module 2 Procedure 1.
Module 2 Procedure 2 calls Module 3 Procedure 1.

Module 3 Procedure 1 gets the following modification : a parameter M3P1Parm that is a DS declared LIKE another DS in the same module. Module 2 Procedure 2 is modified accordingly.

Module 3 is recompiled, no problem.
Module 2 is recompiled, the compiler imports the protoypes of all the exported procedures of Module 3 with the definition of M3P1Parm, again no problem.
Module 1 is recompiled, the compiler imports the protoypes of all the exported procedures of Module 2 : Procedure 1 that is uses, and Procedure 2 that it doesn't - PROBLEM, it doesn't know what is M3P1Parm.


Bigger problem : the policy is to systematically compile ALL the modules that use the module modified. I realise that probably raises a few eyebrows but that's the way things are!

Now, I am asked what I think of this way round the problem :

If an exported procedure contains a DS as a parameter then that procedure must have its own module.

I suggest that Module 2 should be a service program and that Module 1 would not have to be recompiled.
I am reminded that we do not use service programs as they use dynamic calls and that would mean the same as going back to RPGIII.

Any enlightenment would be greatly appreciated.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


_________________________________________________________________
Nieuw: Windows Live Messenger 2008! Gratis downloaden
http://get.live.com/messenger

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.