|
Naming convetion can depend on your application/system/company. For example the following convention might be useful: For Program: we have maximum field length of 10 for naming. XXXXXXXXXX So, first 3 can be used to depict the Application name Next 3 can denote your subsytem name. Next 2 places may indicate your function name last 2 places may be stored for sequencing. So a name may be BNKACTRT00 If yours is a banking application then BNKACTRT00 may mean, BNK for Bank, ACT for account, RT for rate. So a rate file may assume such name. Same goes for copybooks and files. Regards On 11/4/06, cobol400-l-request@xxxxxxxxxxxx <cobol400-l-request@xxxxxxxxxxxx> wrote:
midrange.com
Send COBOL400-L mailing list submissions to
cobol400-l@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/cobol400-l
or, via email, send a message with subject or body 'help' to
cobol400-l-request@xxxxxxxxxxxx
You can reach the person managing the list at
cobol400-l-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of COBOL400-L digest..."
Today's Topics:
1. naming conventions for programs and copybooks...
(Michael Rosinger)
2. Re: naming conventions for programs and copybooks...
(Winchester Terry)
3. Re: naming conventions for programs and copybooks...
(Scott Lindstrom)
----------------------------------------------------------------------
message: 1
date: Fri, 3 Nov 2006 14:40:30 -0500
from: "Michael Rosinger" <mrosinger@xxxxxxxxx>
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
------------------------------
message: 2
date: Fri, 3 Nov 2006 14:55:35 -0500
from: "Winchester Terry" <terry.winchester@xxxxxxxxxxxxxxx>
subject: Re: [COBOL400-L] naming conventions for programs and
copybooks...
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.
------------------------------
message: 3
date: Fri, 3 Nov 2006 15:16:26 -0600
from: Scott Lindstrom <SLindstrom@xxxxxxxxxx>
subject: Re: [COBOL400-L] naming conventions for programs and
copybooks...
(I don't do COBOL everyday, so forgive me if I have something wrong here).
Since we have separate libraries for development and production source
code, we use this version of a COPY statement:
COPY member OF filename.
The library list would be searched and find the copybook in the
development
library.
When the program gets recompiled into production, the production version
of
the copybook would be found. (If the copybook was changed as part of the
modification, then of course it has to be promoted to production also).
But since you have the same member name for the program and the copybook,
this does not sound like it would work for you.
You can use this format of the COPY if that helps you:
COPY member OF library-filename.
Where 'library' is the name of the library where the copybooks are (not
the
program source). Then the fact that they are the same name should not be
a
problem.
Scott Lindstrom
"Michael
Rosinger"
<mrosinger@cciws. To
com> cobol400-l@xxxxxxxxxxxx
Sent by: cc
cobol400-l-bounce
s+slindstrom=pact Subject
iv.com@xxxxxxxxxx [COBOL400-L] naming conventions for
om programs and copybooks...
11/03/2006 01:40
PM
Please respond to
COBOL Programming
on the
iSeries/AS400
<cobol400-l@midra
nge.com>
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
------------------------------
--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) digest
list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.
End of COBOL400-L Digest, Vol 4, Issue 114
******************************************
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.
