Re: Module source naming schemes

For what it's worth, here's the idea we're going with:

We're using a prefixing system for our programs (Verb/object idea).

SRV = service programs, DBS = Database servers, WRK = Work with (subfile)
programs, WDW = Pick List window programs, MTN = Maintenance programs.
Following the prefix is the file or application that it refers to.  For
example, if I have a customer info application (database file is CustInfo),
here's a sample of how we'd name our 'stuff'.

Work with customer info = WrkCstInf
Maintain Customer Info = MtnCstInf
Customer File database server = DbsCstInf   (binder language source is same
name except in QSRVSRC src file)


The prototype /copy is suffixed with a 'P' and any related D spec /copy (if
needed) is suffixed with 'D'.

Prototype /copy = SrvDateP (this contains all the prototypes for all
subprocedures in the module)
'D' spec /copy (if needed) = SrvDateD
Subprocedures = USA2ISO, ISO2USA, MDY2USA, etc. (limit of about 10 per
module)

At this time, when it comes to service programs, we're sticking with one
module per service program.

We've just started to implement this idea, but so far it's working....for
us, anyway.

Just another option to muddy the waters.....



----- Original Message -----
From: "Jim Langston" <jimlangston@conexfreight.com>
To: <RPG400-L@midrange.com>
Sent: Monday, January 08, 2001 5:10 PM
Subject: Module source naming schemes


> I'm starting to build module source files, which I compile then
> create a service program with.  Each module source file will have
> a prototype file.
>
> What type of a naming scheme should I have?
>
> I have some functions that would serve one application called Cartage,
> so I'm thinking along the lines of CARTAGEMOD and CARTAGEPR for those.
> Or should I go with MODCARTAGE and PRCARTAGE ?
>
> And then I have some general utilities, such as my StampToHHMM and
> StampToCYMD routines, which take date/time stamps as input and return
> hours and minutes, or CCCCYYMMDD. Should I make a separate module for
> these and call it, what, MODDATTIM or DATTIMMOD ?
>
> Then I have one called RtvNetF which will Retrieve a user's list of
> waiting network files one at a time ('F' for first call, 'N' for next
> call, 'C' to close and set on LR).  What would I call this one?  MODSYSTEM
> or SYSTEMMOD ?
>
> And then I want to stick this whole thing in one service program, which
> I would call, what, ICSSERVICE ?
>
> What naming schemes has everyone else settled on?  So far there are no
> modules on the system at all, nor are there any service programs, so
whatever
> naming schemes I start with we will most likely go with.
>
> Any suggestions appreciated.
>
> Regards,
>
> Jim Langston
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
>

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---