We use SRC as our standard source file name and combine "CL" and "RPG" program, data file, display file, SQL and etc. in one source file.
We have copies of SRC for production, test and various projects.
I tend to group source members by an "application id" which I put in the first few characters of the source member text.
For example, Text for EDI 856 ASN source members all start with "EDI856:"
BUT, we never had the luxury of a change management system, so we made-up "standard rules" like this . . .
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob Cagle
Sent: Monday, March 30, 2015 2:00 PM
To: RPG400-L@xxxxxxxxxxxx
Subject: Standard source file names?
A friend of mine has gifted me a copy of his home-grown change management tool, but it requires the standard IBM names for source files, and has hard-coded them in all of the tool's programs.
He was shocked when I informed him that I don't use the standard names, and so this tool won't work as is.
I was shocked that he didn't allow for different names since the original intent was to sell this tool on the open market.
So I'm curious - what is your stance on source files? Do you use the standard IBM convention QDDSSRC, QRPGSRC, QRPGLESRC, etc., etc.?
Or custom names?
Single or multiple files for different source types?
Why?
Thanks
Bob Cagle
IT Manager
Lynk, Inc.
--
This is the RPG programming on the IBM i (AS/400 and 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
