RE: Procedure names vs. production support

Bob,

Option 2 was to name the procedure the same as the source member.  In our case, 
today, that would result in a source member name like SP4531M  and a call 
statement like SP4531M(PARM1 :PARM2).

<snip>
If it was the 1 proc per source member/module rule--then all I can say is if
people think that's a good idea, then they are not up to the skill level to
be using procedures anyway.
Now, this does not preclude you from occasionally having a procedure that is
the lone ranger within a module, it just means that having a rule that
requires that kind of thing is only due to lack of experience with this
stuff.
</snip>
Could you expand on this?  In an earlier post I gave the reason I think we 
should have a one to one relationship in this shop. 

Rick

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Bob Cozzi
Sent: Thursday, February 17, 2005 3:56 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Procedure names vs. production support


Rick,
What was option 2 again? I deleted the email.
If it was the 1 proc per source member/module rule--then all I can say is if
people think that's a good idea, then they are not up to the skill level to
be using procedures anyway.
Now, this does not preclude you from occasionally having a procedure that is
the lone ranger within a module, it just means that having a rule that
requires that kind of thing is only due to lack of experience with this
stuff.

All this procedure talk reminds me of when color displays came out on the
System/38. Nobody had experience enough programming color so we had all
kinds of colorful displays created, lots of rules and controls put in place.
As we as a community gain experience with procedures and service programs,
the things that are obvious to others who have already been through it will
become apparent to most people.

On the other hand, if option 2 wasn't the one-proc to one-module thing,
forget everything I just said. :)
-Bob


Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain legally 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.