× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Mark

One client I worked at used a two character prefix followed by four digits
followed by relevant extenders and that worked very well.

For example:

GL0100B01 where GL = "GL" application,
0100 = program sequence number
B = Batch program (an "S" meant "screen
based")
01 = was the module number

When compiled into a program the module number would be dropped to leave the
program name. Binding directories always had the same name as the program
or service program they were associated with.

Display files and printer files had the same convention with the "B" or "S"
being replaced by "FM" or "PR" as appropriate.

Database files had the convention of a two character prefix followed by four
digits and possible extenders.

For example:

GL1001 where GL = GL Application
1 = File type (1=PF, 2=LF, 3=Joined LF,
4=Work file)
001 = File sequence number

A logical file would have an additional character or characters to further
identify it. Other extenders used were "H" for history, so you might have
GL1001 and GL1001H.

Best regards

Jonathan

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Mark Keller
Sent: 27 June 2007 15:22
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.