Michael, FWIW, we use a single source file called SOURCE to store all of our program/DDS code (CBLLE, RPGLE, PRTF, DSPF, LF, PF, REXX, etc) and have standardized on a source member naming convention that will not result in duplicates. Our copybooks are the only pieces of code stored in a separate source file (called INCLUDE). This was setup this way because we came from a mainframe environment with a similar setup. It has worked fine for us...YMMV. I'm not sure their is any "recommended" method unless you prefer to follow the Q???SRC naming convention employed by IBM. We have found that having the majority of our program code in a single source file cuts down on the amount of "jumping around" that you have to do PDM compared to the IBM naming style. It also helps to simplify large-scale modifications by narrowing down source code changes to a single file. It all boils down to the type of shop your working in and which technique best serves your backup and change-control standards. Terry Winchester Programmer/Analyst ________________________________ The Raymond Corporation terry.winchester@xxxxxxxxxxxxxxx
-----Original Message----- From: cobol400-l-bounces+terry.winchester=raymondcorp.com@xxxxxxxxxx om [mailto:cobol400-l-bounces+terry.winchester=raymondcorp.com@mi drange.com] On Behalf Of Michael Rosinger Sent: Friday, November 03, 2006 2:41 PM To: cobol400-l@xxxxxxxxxxxx Subject: [COBOL400-L] naming conventions for programs and copybooks... List, I need some advice on naming conventions for programs and copybooks. What brought this to my attention is that I discovered in my conversion efforts that I have a COBOL program (sub-routine) with a corresponding copybook that have the same name. It was my understanding from others that I've spoken with that source "type" (or suffix - not sure of the correct term in the iSeries world) should be CBLLE for COBOL/ILE and SQLCBLLE for COBOL/ILE+SQL. I realize it is probably better not to have a copybook and program with the same names, but how is this handled in the iSeries world. Separating them to two different sourcefiles may not be enough because both may be searched during a compile procedure. Is there a way to differentiate between a program source vs. a copybook? What is the recommended way to handle this problem and why? TIA! -- Regards, Michael Rosinger Systems Programmer / DBA Computer Credit, Inc. 640 West Fourth Street Winston-Salem, NC 27101 336-761-1524 m rosinger at cciws dot com
Confidentiality Notice: The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is not authorized and may be unlawful.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.