Cobol - COBOL Source Parser

Author

COBOL Source Parser

Bruce P. Barrett

2006-10-15, 6:56 pm

Recently I looked at some software that I have developed and evolved over
time to help me determine the impact of changes. The system reads job
streams(JCL), COBOL program source code, copybooks and screen source for a
job, program, map and/or group of files and parses selected information to
files for online access. Information maintained includes jobs, program
source/executables, files, records, data elements, screens, called modules,
copybooks, verb counts, referenced file actions(by program), identities,
dates, where/how used, location and titles when available. Titles can be
added to source as a comment line prior to parsing. Online interrogation
allows initial access at various levels within a project and provides a
strong "Where Used" option i.e. files can be viewed at the project, job or
program level.
No attempt is made at this time to identify errors. The objective is to
show what is reflected by the source however enhancements could be easily
included.
Does anyone know if there is any demand/interest in this type of software?

Thanks
Bruce Barrett

Binyamin Dissen

2006-10-15, 6:56 pm

On Sun, 15 Oct 2006 15:45:24 -0400 "Bruce P. Barrett"
<brucepbarrett@adelphia.net> wrote:

:>Recently I looked at some software that I have developed and evolved over
:>time to help me determine the impact of changes. The system reads job
:>streams(JCL), COBOL program source code, copybooks and screen source for a
:>job, program, map and/or group of files and parses selected information to
:>files for online access. Information maintained includes jobs, program
:>source/executables, files, records, data elements, screens, called modules,
:>copybooks, verb counts, referenced file actions(by program), identities,
:>dates, where/how used, location and titles when available. Titles can be
:>added to source as a comment line prior to parsing. Online interrogation
:>allows initial access at various levels within a project and provides a
:>strong "Where Used" option i.e. files can be viewed at the project, job or
:>program level.
:>No attempt is made at this time to identify errors. The objective is to
:>show what is reflected by the source however enhancements could be easily
:>included.
:>Does anyone know if there is any demand/interest in this type of software?

DocAID by ASG does the JCL part.

--
Binyamin Dissen <bdissen@dissensoftware.com>
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel

Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

ski

2006-10-16, 3:55 am

Bruce P. Barrett wrote:
> Recently I looked at some software that I have developed and evolved over
> time to help me determine the impact of changes. The system reads job
> streams(JCL), COBOL program source code, copybooks and screen source for a
> job, program, map and/or group of files and parses selected information to
> files for online access. Information maintained includes jobs, program
> source/executables, files, records, data elements, screens, called modules,
> copybooks, verb counts, referenced file actions(by program), identities,
> dates, where/how used, location and titles when available. Titles can be
> added to source as a comment line prior to parsing. Online interrogation
> allows initial access at various levels within a project and provides a
> strong "Where Used" option i.e. files can be viewed at the project, job or
> program level.
> No attempt is made at this time to identify errors. The objective is to
> show what is reflected by the source however enhancements could be easily
> included.
> Does anyone know if there is any demand/interest in this type of software?
>
> Thanks
> Bruce Barrett
I use not all in one tool, but set of tools:
revision control system, text manipiulation tools (grep sed etc.), tag
file builder which supports cobol (exuberant-ctags) and editor which
support tags database (a lot of).
Use lex/yacc (or more modern antlr) for writing custom tools for cobol
source manipulations and ctags files parsing, lex files for generic
cobol googled for free.
Tools i not try but seems could help: robodoc, some source+ctags->html
converter.

Alistair

2006-10-21, 7:55 am

Bruce P. Barrett wrote:
> Recently I looked at some software that I have developed and evolved over
> time to help me determine the impact of changes. The system reads job
> streams(JCL), COBOL program source code, copybooks and screen source for a
> job, program, map and/or group of files and parses selected information to
> files for online access. Information maintained includes jobs, program
> source/executables, files, records, data elements, screens, called modules,
> copybooks, verb counts, referenced file actions(by program), identities,
> dates, where/how used, location and titles when available. Titles can be
> added to source as a comment line prior to parsing. Online interrogation
> allows initial access at various levels within a project and provides a
> strong "Where Used" option i.e. files can be viewed at the project, job or
> program level.
> No attempt is made at this time to identify errors. The objective is to
> show what is reflected by the source however enhancements could be easily
> included.
> Does anyone know if there is any demand/interest in this type of software?
>
> Thanks
> Bruce Barrett

I expect that if offered for free then there would be enough takers but
if you try charging for it then demand would drop. If you wish to
publish the software, you could do so using one of the open source
licence types, perhaps making the s/w free for personal use?

Bruce P. Barrett

2006-10-22, 6:55 pm

Thanks for the comments. I know there are tools available, especially for
new/recent development, that provide a single repository for project/system
information. I imagine there are places where a frantic search occurs when
a request is received requiring change to a system/sub
system/program/file/copybook/screen/job stream etc that hasn't been opened
since Y2K and in some cases last w

. My objective was to mechanically
extract data/information from various sources and create a single repository
showing what, where, when, how and relationship with minimal human
intervention.
Allister, you are probably right about offering it free.
Thanks
Bruce

"Bruce P. Barrett" <brucepbarrett@adelphia.net> wrote in message
news:PpKdncxmFpTRDa_YnZ2dnUVZ_rudnZ2d@ad
elphia.com...
> Recently I looked at some software that I have developed and evolved over
> time to help me determine the impact of changes. The system reads job
> streams(JCL), COBOL program source code, copybooks and screen source for a
> job, program, map and/or group of files and parses selected information to
> files for online access. Information maintained includes jobs, program
> source/executables, files, records, data elements, screens, called
> modules, copybooks, verb counts, referenced file actions(by program),
> identities, dates, where/how used, location and titles when available.
> Titles can be added to source as a comment line prior to parsing. Online
> interrogation allows initial access at various levels within a project and
> provides a strong "Where Used" option i.e. files can be viewed at the
> project, job or program level.
> No attempt is made at this time to identify errors. The objective is to
> show what is reflected by the source however enhancements could be easily
> included.
> Does anyone know if there is any demand/interest in this type of software?
>
> Thanks
> Bruce Barrett
>

Alistair

2006-10-23, 6:55 pm

Bruce P. Barrett wrote:[color=darkred]
> Thanks for the comments. I know there are tools available, especially for
> new/recent development, that provide a single repository for project/system
> information. I imagine there are places where a frantic search occurs when
> a request is received requiring change to a system/sub
> system/program/file/copybook/screen/job stream etc that hasn't been opened
> since Y2K and in some cases last w

. My objective was to mechanically
> extract data/information from various sources and create a single repository
> showing what, where, when, how and relationship with minimal human
> intervention.
> Allister, you are probably right about offering it free.
> Thanks
> Bruce
>
> "Bruce P. Barrett" <brucepbarrett@adelphia.net> wrote in message
> news:PpKdncxmFpTRDa_YnZ2dnUVZ_rudnZ2d@ad
elphia.com...

Many years ago, I saw a similar tool permitting tracking of variables
through programs (including maps and CICS source). It had one real
problem: it was able to list all occurrences of a named variable
throughout the system but where the name changed (from input file to
working storage to output file) the trail was broken and needed the
user to either be aware of the name change/transformation or to be
aware of which programs were most likely to contain the important uses
of the variable.

One tool that I did find really useful was one which listed all file
names, DDnames, etc., the procedure and line numbers. It also covered
procedure names and in which job streams they could be found.

Bruce P. Barrett

2006-10-30, 6:55 pm

Alistair wrote.

> Many years ago, I saw a similar tool permitting tracking of variables
> through programs (including maps and CICS source). It had one real
> problem: it was able to list all occurrences of a named variable
> throughout the system but where the name changed (from input file to
> working storage to output file) the trail was broken and needed the
> user to either be aware of the name change/transformation or to be
> aware of which programs were most likely to contain the important uses
> of the variable.

No effort is made to show the flow of data. Using the "Where Used" option
one can identify where the data element is used and view the line of code
where it is used with a click of the mouse.

>
> One tool that I did find really useful was one which listed all file
> names, DDnames, etc., the procedure and line numbers. It also covered
> procedure names and in which job streams they could be found.
>

The tool shows the above and includes executed programs, libs, parms and
variables. The program source and/or expanded source can be viewed along
with program files, records, record data elements, where and how used.

Thanks
Bruce

Sponsored Links