|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Which brings up a question. V5R2 allows you to store your source in the IFS instead of just the traditional source physical files. Is anyone using this? If so, how has this affected your naming conventions? CRTBNDRPG PGM(MYLIB/MYPGM) SRCSTMF('/ERPpgms/source/rpgpgms/mypgm.txt') Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Joe Pluta" <joepluta@PlutaBrothers.com> Sent by: midrange-l-admin@midrange.com 10/09/2002 04:49 PM Please respond to midrange-l To: <midrange-l@midrange.com> cc: Fax to: Subject: RE: Library and Source File Question > From: Tom Liotta > > An element I find troublesome is where I must replace a CLP with > an RPG > > I've never seen clear value in name by source type. I always rely > on other object attributes anyway. There's something to this argument. At the same time, I like certain naming conventions. I like to use a root name that has some meaning to me. An example might be P4UOEMNT. The "P4U" is a product prefix, and then the rest of the root name identifies the program, in this case Object Environment Maintenance. The root name deriviation is not relevant to this discussion, but it's important elsewhere (especially in procedure naming). However, once I have the root name, I like to use specific suffixes for the various types - "D" for display files, "P" for printer files, "R" for RPG programs. This works well in my environment because I never use display or printer files in CL programs. So what's the benefit? Well, I use a single source file. So, when I want to recompile all of the pieces of a program, I can do it quite easily: 1. Subset by the root name 2. Type my custom compile command in the first entry 3. Hit F13 to copy the compile command 4. Hit Enter Boom. Complete recompile of all the associated objects in a flash, in the right order, so no CPF4131 errors. Just one man's opinion. Joe _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.