|
We just name them Rxxxx where xxxx is the next number in the list. ie R0001, R0002, R0003 The DDS is also named Rxxxx to match the program. Steve Jones "Brian Piotrowski" <bpiotrowski@xxxxxxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 02/22/2006 02:33 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> cc Subject Naming Conventions on Your Programs 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 -=-=-=-=-=-=-=-=-=-=-=-=-=-
As an Amazon Associate we earn from qualifying purchases.
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.