Producing a structured chart from COBOL source code 1

[JasonRigby]

Hi. I was wondering if anyone knows of a freeware utility that can produce a structured diagram from COBOL source code. I have a number of large COBOL source code saved on my desktop as text files, and I was hoping to find a utility which can parse the code and produce a structured flowchart from this.

Does anyone know if such a thing exists?

Thanks.

 

[Crox]

Hi,

I am sorry it is not there, but perhaps we on the forum can make a project of it. Input: source that is 100% error free and output: HTML.

Perhaps some people can make some HTML examples. I can parse the source and generate HTML.

I would like to work with JSP or VSP structures.

Together it is nice to develop this.

Regards and hoping for some good response.

In fact it would be great if someone has a FTP directory for this project.

Crox

 

[NinaToo]

Don't most programmers do the structured flow chart and/or structured pseudocode before they actually write the code?

Though the structured flow charts are frequenly done in pencil and then wind up lost in some programmer's "filing" system on top of their desk.

What is the point of making structured flow-charts after the program has already been coded? Unless someone wants to keep a record of "program trees" i.e. Program A calls Program B which either calls Program C which links to Program X, or calls Program D which passes control to Program Y, etc. But this can be done with module diagrams.

In CICS, a programmer or analyst can run a utility called CEDF. This will display all CICS commands from various programs, and it will show which programs link or pass control to which other programs. Don't know if other systems have such a utility.

Nina Too

 

[Crox]

Hi,

The use of making a chart afterwards is that if you have to make changes in a program that you don't know, a good chart can help you to understand how the program works. Questions like 'can I savely change this-and-that in section/paragraph so-and-so without modifying the old functions'. That is where a JSP or VSP structure is going to help you a lot.

The situation that you make a chart and make a program, that is when you are building new programs. But if you do maintenance ....... and the documentation is always far behind the source ....

That is why I would like to put some efford in making an automated chart.

Regards,

Crox

 

[NinaToo]

Crox, I understand your reasoning.

Though I've found that, if a program is properly documented using flower-boxes, etc. throughout the program, and especially it was pointed out to me by a project leader, if the original program is written using structured programming methods with logical arrangements and numberings of paragraphs -- then whichever maintainer comes down the pike later on should have little trouble in seeing how the program works so they can put in additions to the program.

The purpose for your after-the-fact structured diagram utility, it would seem, would be to facilitate understanding older, poorly-documented programs full of "goto's" and other speghetti code. In which case, it would be quite helpful.

As for new programs being created, I usually make fairly extensive notes, pseudo-code, and also some structured diagrams on a Microsoft Word document (using their drawing facility). That way, this document can be kept online for anyone else's perusal in case they need it.

I also make a detailed test plan, so that the program can be regression-tested after changes are made. This is especially important in CICS and other online systems, as frequently one change can result in whole series of delicately-constructed logic sequences becoming undone.

Anyway, keep me posted on your progress. I do know of some source code macros and JCL's which, when run, will list the order that paragraphs get performed when running batch jobs. Perhaps you might start from there.

Nina Too

 

[Haha]

Jason,

Am not sure if this site could help you:

http://www.arcadsoftware.com/sca.php3

 

[NinaToo]

I looked at the Arcade site. I was about ready to ask my supervisor about whether our department should download this to use. Then I saw the requirements. One of them said that you need an AS/400 connected using TCP/IP.

We don't use the AS/400, we use IBM MVS/ESA. It doesn't look like this product is designed to be used with MVS/ESA. Oh well......

Nina Too

 

[Crox]

Hi,

I know from big companies about research they did if it pays to make up-to-date documentation for some old systems.

It does not.

The amount of work it costs to make the documentation (and to keep it up-to-date) does not earn itself back at the time someone has to update the system.

General information pays.

Automated documentation pays.

Nowadays there are systems that document other systems by interpreting the sources amd build complete data dictionaries accessable with SQL.

I know for example that Cornerstone's software does this and also extracts business rules from sources:

http://www.cornerstone.nl

What I want is a combination of a html source with zooming in possibilities when you use a call or a copymember or a perform, etc. and also a structured chart. It would be great if that would be a public utility.

I developed once something for PL/1 with a collegue. We didn't make the structures, but we made the colored source, zooming possibilities, enumerations of copies, programs, DB2 databases used, etc. and the other way around.

It was nice to do, but when I had to work at an other office, it bleeded a little bit dead, we didn't make it complete.

The same system is very usable to do COBOL. But I don't like to do it completely on my own unless there is a sponsor somewhere out there....

Regards,

Crox