Re: Naming Conventions on Your Programs

[Jerry Adams <jerry@xxxxxxxxxxxxxxx>]

Programs are named thusly:

   AAFNNN where

   AA   =   Application, such as Inventory (IV)
   F      =   Functions, such as Update (U), report (R), selector (S), 
Extraction (X)
   NNN   =   next sequential number

   IVU010   =   Item Master Maintenance

Sometimes I'll skip around the sequential numbers so that I can name all 
programs in a string with the same numbers, such as:

   IVS002 (selector)
   IVX002 (data extraction)
   IVR002 (generate the report)

Still use 'FM' for displays: IVU010FM.

The CL that runs IVU010 is IVU010C.  The CL that runs the report string 
is IVR002C.

Physical files are just named.  NVMAST = Item Master table.  Logicals 
over a table are L01, L02, etc., such that

   NVMASTL01 and NVMASTL02 are logicals over, you guessed it, the Item 
Master. 

Giving logicals meaningful names isn't worth the trouble.  The naming 
convention, though, does group them under the parent in the QDDSSRC file. 

Sometimes something comes out of left field (doesn't really fit any of 
my "rules").  Then I just make up "stuff"; makes the day seem a little 
lighter and breezier. 


        * Jerry C. Adams
*iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.995.7024
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Brian Piotrowski wrote:

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