× 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.


  1.  Home
  2. RPG400-L
  3. February 2006

RE: Best way of using Service programs.

Hi Don,

<snip>
Name clashes are more difficult to manage when your prototypes are scattered
among many different source members.  That's why we have all our prototypes
in one source member.
</snip>
I agree that name clashes are more difficult to manage when using multiple source members, but in large MIS departments the thought of runnning multiple concurrent projects, is bad enough. But with the added complication of putting all prototype changes/additions into the same source member makes me want to take a lie down. :-) I can't even image how we would handle that. 

<snip>
As for initial design and development definition, well, those steps here
tend to be one person shows.  When we were a big shop, we have a quality
assurance team to handle stuff like that.  We figure our small team size (6)
and the senior level experience (noone with less than ten years on
iSeries/AS400) negates the need.  That's all the more reason to make
resolving issues like procedure name clashes as simple as possible.
<snip>
I take your point about smaller shops not being able to support the extra design/devlopment overhead I described, but I can't see how having a single source member makes things simple. With regard to name clash prevention - I can easily see the benefit of a central point to hold all prototype definitions, but this doesn't necessarily need to be a source member used to generate production code. I just don't like the idea of having to change a prototype in a module for a production bug-fix, only to find three other programmers are working on the source member for three completely different projects. They'd have to back their changes out so I could get the "clean" code + bug-fix back into production asap. The more modules you include in this source member the higher the chances this will happen. 

Cheers

Larry Ducie

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.