Re: [open-cobol-list] organizing code in Cobol

[Chris Geldenhuis]

On 01/22/2013 05:29 PM, Patrick wrote:
> Hi Everyone
>
> So I am working through online documentation about opencobol and cobol
> in general and making progress.
>
> I have ordered several Cobol books but they won't be here for a while.
>
> I was wondering in the meantime about a couple of things.....
>
> 1)There are billions of Cobol lines in service but actually I have not
> been able to find any sizable Cobol codebases to study, just short
> snippets of code. Does anyone know of a project I could study?
>
> Have people wrote these million line+ applications using just copybooks
> and compilation order to organize their code? I could see myself getting
> confused past about 10K lines.
>
>
> -Patrick
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnnow-d2d
> _______________________________________________
> open-cobol-list mailing list
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/open-cobol-list
Hi Patrick,

I find that the most effective way of organizing your source code is to 
have a rigidly applied naming convention for both program and copy book 
names. I use something like:

xxxtNaaa.[cbl or cpy] where xxx is an abbreviation for the project,
                                              t is either 'p' for 
program or 'l' for libarary (copy book)
                                              N indicates the type of 
program or copy book e.g Data input, Report etc.
                                              aaa is a sequence number 
for that type of program / copy book.

for copy books relating to files I use N = 0 for select clauses,
                                                           N = 1 for 
File definitions (FD + record definitions)
                                                           N = 6 for 
routines that manipulate the files (Open, Read variations etc)

Regards

ChrisG