RE: Function Opinion

[rob@xxxxxxxxx]

Never name a module the same name as the service program would help to get 
around this.
Also helps to beat into submission those who clobber your program with 
CRTBNDRPG when they should have used CRTRPGMOD and then either CRTPGM or 
CRTSRVPGM, (or the UPD... variant.)

You could change the never to "never when the final object is composed of 
multiple modules" if it fits better.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




darryl.mavin@xxxxxxxxxxxxxx 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
10/15/2003 10:57 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
rpg400-l@xxxxxxxxxxxx
cc

Subject
RE: Function Opinion






That's fine as long as you know which developers are working on what
modules, or your change control software handles it.

If the modules are checked out and worked on by different developers in
their own libraries, when one of the developers create the service 
program,
they might not know about the changed module in the other developer's
library.  This could result in the service program only having the changes
of the last developer to create the service program.

Having 1 function/service program greatly simplifies any maintenance tasks
as only one developer can work on a service program at a time.

-----Original Message-----
From: David Gibbs [mailto:david@xxxxxxxxxxxx]
Sent: 15 October 2003 16:28
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Function Opinion


darryl.mavin@xxxxxxxxxxxxxx wrote:
> The main advantage for having one function per service program is
> maintainability.  It can get a bit messy if 2 developers try to modify
> different functions in the same service program.

That's really no advantage ... the two developers are actually working 
on modules, and then putting their modules in a service program.  Just 
have them put 1 function per module, and bind all the modules into 1 
service program.  You can rebuild or update the service program quickly.

Of course, there's really no reason to just put 1 function in a module 
... just make sure related functions are in the same module.  Chances 
are that two developers are not going to be working on the same logical 
function at once.

david


_______________________________________________
This is the RPG programming on the AS400 / 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.


------------------------------------------------------------------------------
The opinions expressed within this email represent those of the
individual and not necessarily those of Gullivers Travel Associates (GTA).

This email and any files transmitted with it are confidential and intended 

solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify 
postmaster@xxxxxxxxxxxxxxx

Should you wish to use email as a form of communication, GTA are unable to
guarantee the security of email content outside of our own computer 
systems.



________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
________________________________________________________________________
_______________________________________________
This is the RPG programming on the AS400 / 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.