RE: Naming Conventions on Your Programs

Same thing here....works nicely...

The 3rd character *could* be considered redundant as far as programming
source goes (since you can subset PDM/WDSC by source member type...but
on a separate production machine it really helps out when you see
Oexxxxx you know to look in your Order Entry source.

IMO any shop that uses the same 2 character prefix are losing a lot of
manhours...

Say you need to add a new field to filea

If filea is only used for Order Entry program you still have to comb
through every source member using the "SS" where with a structured
approach you'd only have to comb through the source members starting
with "OE". 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Phil Kestenbaum
Sent: Wednesday, February 22, 2006 1:31 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Naming Conventions on Your Programs

We name based on function, first 2 would be OE, AR, etc. then R=Rpg,
C=Cl, P/L =-PF/LF, rest is up to the programmer.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Piotrowski
Sent: Wednesday, February 22, 2006 2:33 PM
To: RPG programming on the AS400 / iSeries
Subject: Naming Conventions on Your Programs

Hi All,

 

I wanted to take a quick poll as to how you name your programs in your
shop.  Currently, our parent company names the programs based on their
operation.  All programs were formatted as such:

 

SS + 3 digit number + Program Type (ie: R for RPG, D for DDS, etc.)

 

So we had names such as SS112R, SS112D, etc.  We did originally have
"SP" programs but post-conversion these programs became "SS" (not
exactly sure why this is done - it has always been SOP in our
programming departments).

 

I'm trying to move away from this practice of using SSxxx because any
new programmer coming into the company will not know what these programs
do.  They will need to spend time reviewing the source code to
understand what is happening.

 

I'm of the mindset to name our programs with something more meaningful.
For example, if we have a program that creates master packing lists, I
would probably name it CRTMPLR and it's DDS/PRTR files CRTMPLD and
CRTMPLP respectively.

 

I do wish that the AS/400 would accept file names larger than it's
current limitations.  It would be nice to be able to name a program
"Create Master Packing List" instead of trying to do it shorthand.

 

What is your shop's policy for naming files?

 

Thanks!

 

Brian.

 

-=-=-=-=-=-=-=-=-=-=-=-=-=-

Brian Piotrowski

Specialist - I.T.

Simcoe Parts Service, Inc.

PH: 705-435-7814

FX: 705-435-6746

-=-=-=-=-=-=-=-=-=-=-=-=-=-