Re: Naming Conventions on Your Programs -- RPG400-L

I like the XXnnnnYY style, where XX is the application, nnnn is asequential numbering system, and YY is the object type (R= RPG, C = CL,D= Display file, O=output(printer), P=physical file, Ln = Logical files.)


I like two other refinements.

1)In the nnnn sequencing we often assign a series of numbers to aproject. (i.e. Use the 723n series for this project, or use 72nn forthat series.)2) use the application XX for the source file, as in ARSRC, APSRC,instead of QRPGLESRC, QCLSRC, etc.



Denis Robitaille wrote:

We use the following convention:

XXY9999Z

XX= Application (GL=General ledger ...)
Y= Type of program (U=update R=research ...) (If I could, I would let
go of this part)
9999=sequential number
Z= type of object (R=RPG D=Display file ...)

We use the 50 caracters description to do what you want to do with the
program name.

In fact, I strongly suggest that you stay away from trying to give
meaninfull name to your programs. The 10 caracters limit would force you
to use strange acronyms that, if you have any volume of prpogram, will
become rapidely incomprehensible.

Denis Robitaille
Directeur services technique TI
819 363 6130

SUPPORT
Jour (EST) Daytime : 819-363-6134
En-dehors des heures (EST) After hour : 819-363-6158
Network Status : 819-363-6157

bpiotrowski@xxxxxxxxxxxxxxx 2006-02-22 14:33:14 >>>

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

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