RE: Service Programs and Naming Conventions

Marvin,

Check out the archives.  I asked a similar question about naming conventions 
for service programs and module a few months ago that generated quite a few 
responses on different methods.  Maybe something in that thread will help you.

Try searching with 'service program', module, and naming.

HTH,

Rick

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Marvin Radding
Sent: Wednesday, September 14, 2005 7:15 PM
To: RPG programming on the AS400 / iSeries
Subject: Service Programs and Naming Conventions


I am designing a service program and considering version, revisions and
naming conventions.



Here's what I am proposing so far.



1.      Every program has a name that consists of  upper/lower case
letters ending with a release.version numering.

        a.      How do I get the upper/lower case name?  The D-Spec
always comes out in upper case.
        b.      Can I append a number.number to the end of the name?  I
tried but the compiler rejects the dots.

2.      When an enhancement/improvement is made to a module, the
release.version will change and the new module will be added to the
service program but the old module will not be replaced.  This way no
recompilations/modifications will be necessary.  Is this idea feasible?
Can I added different modules for basically the same program without
encountering any problems as long as the external/exported names are
different?



Any idea if this is possible?



Marvin


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