Re: Source Naming conventions

We use single alpha characters to identify. Usually 3 of them... WKR268 =
Warranty system, the K stands for KIA I assume, and the R for RPGLE, 268 is
just a sequence number, which would kind of link say WKC268 is the CLLE that
calls WKR268 (Oh, and then if WKR268 is a Subfile Selection type program,
with a separate program handling a maintenance screen or something, it would
be WKR268A) Whatever makes sense to you and your shop I guess.

CJ


On 6/27/07, Mark Keller <Mark.Keller@xxxxxxxxxxxxxx> wrote:

Hello. I'm curious as to how people name their rpg source members. I'm
coming into a new shop where everything is pretty much open to however I
want it to be. We currently use 2 packages for most of our production
processing and most of my code and the existing code are interfaces into
one or both of these systems. I can break the systems down into 2 digit
codes AA and BB we'll say for now. Should I make all my programs fall
under one of these categories? AA0001, AA0002, BB0001, etc... I have
some code that interfaces with AA, but could be subcategorized as EDI.
I could name these EDI0001 or AAEDI0001. Also some Physical Inventory
programs. PI0001? AAPI0001.

I guess I'm asking for thoughts and opinions on this. What do you use
for your naming conventions? What works and what doesn't work?

Thanks! Mark

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