Ok. The first example is one I'm familiar with. I wasn't sure if that
was very standard or not. I'm having troubles getting to the archive.
I've been experimenting with names and I'm not so sure about what I've
been doing. EDISEND, EDIRECEIVE don't seen too good. But one program
that will be used by several EDIWRTLOG makes sense. But then, if
everything else is numbered, shouldn't it be numbered also? :)
Thanks!
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[
mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Sharon Wintermute
Sent: Wednesday, June 27, 2007 7:56 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Source Naming conventions
Very subjective topic!!!!
In one shop we used whatever name we wanted as long as it wasn't crude.
In another shop we used a convention like this.
XXXYYYBBB
XXX = System Type - Like Purchasing, Inventory, Order entry, etx.
YYY = some number. The number range meant something as well.
BBB = Type of program, sometimes it was R or C (RPG or CL) then we
switched to functionality in order to use modules.
Plus, we went to once QSOURCE to hold all the source.
The we could subset to get where we wanted.
So for example,
SYS100F = Physical File
SYS100L00 = Logical File of SYS100F
SYS100D = display file
SYS100P = Report File
Then for a simple maintenance routine where each screen was in a
separate module:
SYS100 - Work with Subfile
SYS100UPD - Add or Update
SYS100DLT - Delete subfile
SYS100RPT - Report generation
SYS100DSP - Display only
Then the SYS100* were bound together into SYS100.
A CL could by SYS100C but not always. We made the actual modules
independent of language nomenclature.
Just my 2 cents,
Sharon
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[
mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Keller
Sent: Wednesday, June 27, 2007 9:22 AM
To: RPG programming on the AS400 / iSeries
Subject: Source Naming conventions
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.
CONFIDENTIAL
This e-mail and any files transmitted with it are the property of
BillSoft, Incorporated and/or its affiliates, are confidential, and are
intended solely for the use of the individual or entity to whom this
e-mail is addressed. If there is a non-disclosure agreement in effect
between BillSoft and the recipient, the contents of this email and any
files transmitted with it should be treated as confidential under the
terms of such agreement. If you are not one of the named recipients or
otherwise have reason to believe that you have received this e-mail in
error, please notify the sender and delete this message immediately from
your computer. Any other use, retention, dissemination, forwarding,
printing or copying of this e-mail is strictly prohibited.
"BillSoft" and "EZTax" are registered trademarks of BillSoft,
Incorporated.
--
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.
midrange.com
