Stefan Bodingh

The easiest way to check if the problem really is COMP-3 is to create a small program that packs and unpacks a COMP-3 X number of times that would take 30 to 60 seconds on GnuCOBOL and run the same program on MF and check diff in seconds . If there is a huge difference, COMP-3 is the culprit. If the difference is small, it is something else.

Take a look at https://sourceforge.net/projects/cobolanalyzer/ Den 2021-05-04 kl. 14:54, skrev flaneur7508: Hello, My needs are not as complex :) I'm was hoping there was somthing out there that could be used to document my COBOL. i.e. provide insights into all the PARAGRAPHS and the various PERFORMS contained etc. In short i'm looking for somthing like this: https://github.com/BroadcomMFD/cobol-control-flow https://github.com/BroadcomMFD/cobol-control-flow That works with gnuCOBOL. This extension...

Probably it would. I changed to Micro Focus COBOL from Unisys before I wrote this tool. As I can remember Unisys don't have file extentions, so you will have to create that when you export the files to Windows. Source files should have extension of (.pco .cob .cbl) in order to be recognized by the COBOL analyzer and library (Copybook) source files should have an extension of .cpy to be recognized.

Looks interesting, but what changes do I have to implement to run if my GnuCOBOL...

I suggest you install VMware player or VirtualBox and run Linux in a VM on Windows....

I downloaded open-cobol-cpp_vs2010 form kiska.net and thought it should be a piece...

Usually you have different scripts when compile for test or for delivery to customer....

Micro Focus COBOL output is the same as IBM output.