This is my easy to use IDE for GnuCOBOL.
This is WINIDE - its use is for PC targeted GnuCOBOL programs - as opposed to WINZOS for zOS emulation.
Break points can be set after successful compilation
OR
During runtime execution of the debugger
Both are demonstrated in the video
Compiling is simple, two choices, compile with animation (A) or without animation (M)
If a compilation error is detected the compile panel indicates compiled failed
Use a "V" function code to view the compilation listing
Find error by "F ERR 1"
Start a concurrent edit session - locate the error (from the compile listing), fix the error in the edit session, save the edit session, recompile.
If 'EXEC SQL' is detected in your COBOL source - the DB2 preprocessor and bind are done automatically.
Execution is initiated by eXecuting a .bat file "X"
The editor you use is extensible via an environment setting - the animation always uses the Xpediter like user interface.
The animated debugger is full featured.
Right clicking a data field name will present a panel to display, modify, watch . . the selected data field.
Zoom "Z" animates the program at flank speed
Quite "Q" executes the program sans the animation - break points are still honored
There are help screens with most of the WINIDE features
IMO it is the best GnuCOBOL IDE targeting PC based applications.
You can even animate programs having a screen section.
I will provide another post that targets zOS emulation
I have watched the video and find it truly impressive—especially the debugger/animator component.
For the sake of completeness—and much to my own disappointment—I must add that I could not use this solution, as my understanding is that it does not support the "free-form" (source-free) format. I want to emphasize that this is strictly my own personal perspective—the viewpoint of a developer working on Windows or Unix applications, rather than on mainframes. In my opinion, being restricted solely to the "fixed-format" is an overly limiting constraint. I believe IBM has never supported free-form syntax on its systems, likely due to the limitations of mainframe Partitioned Data Sets (PDS), which are restricted to 80 characters per line.
On Windows or Unix platforms, no programming language imposes such a limitation, as it would create intolerable constraints for developers. We have discussed this topic before, so I will leave it at that.
My respects, Mr. Ralph—an impressive piece of work!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you Eugenio
So much of the improvement to the debugger can be attributed to Chuck H.
Chuck and I have collaborated on many improvements to GnuCOBOL, WINZOS, WINIDE.
Chuck's expert mainframe technical skills being applied to GnuCOBOL has made the debugger outstanding (IMO), the COBOL closer in functionality to Micro Focus / Rocket and IBM COBOL, runtime services, EXTFH.
Chuck has also implemented many of the CBL_ routines that are needed to make this effort cohesive and very functional.
Kudos to Chuck !
Eugenio regarding limitations:
db/2 would not be functional - the db2 preprocessor is wed to 80 columns
CICS would not work - again the preprocessor
Animation would not work - under the covers columns 1-6 and / or 73-80 are used for various I-O in the animator primitives.
In theory you could use WINIDE to edit, compile, and test - but not debug via the animation.
I think source free would pass thru the compile component- you would have to include the >> syntax in the source.
Eugenio, thanks again for the kind words.
Ralph
Last edit: Ralph Linkletter 2 days ago
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Indeed, and a bunch of things (EXTFH, CBL_) are upcoming - hopefully before end of December.
I think source free would pass thru the compile component- you would have to include the >> syntax in the source.
If you have a "current" version of GnuCOBOL and don't explicit specify the fixed reference-format (but that's included in all but -std=default, which is likely at least used for WinZOS as ibm = -fformat=cobol85), then cobc recognizes free format when used in the first lines of code.
Important for documentation would be where the compiler flags are currently set in WinZOS/WinIDE.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is my easy to use IDE for GnuCOBOL.
This is WINIDE - its use is for PC targeted GnuCOBOL programs - as opposed to WINZOS for zOS emulation.
Break points can be set after successful compilation
OR
During runtime execution of the debugger
Both are demonstrated in the video
Compiling is simple, two choices, compile with animation (A) or without animation (M)
If a compilation error is detected the compile panel indicates compiled failed
Use a "V" function code to view the compilation listing
Find error by "F ERR 1"
Start a concurrent edit session - locate the error (from the compile listing), fix the error in the edit session, save the edit session, recompile.
If 'EXEC SQL' is detected in your COBOL source - the DB2 preprocessor and bind are done automatically.
Execution is initiated by eXecuting a .bat file "X"
The editor you use is extensible via an environment setting - the animation always uses the Xpediter like user interface.
The animated debugger is full featured.
Right clicking a data field name will present a panel to display, modify, watch . . the selected data field.
Zoom "Z" animates the program at flank speed
Quite "Q" executes the program sans the animation - break points are still honored
There are help screens with most of the WINIDE features
IMO it is the best GnuCOBOL IDE targeting PC based applications.
You can even animate programs having a screen section.
I will provide another post that targets zOS emulation
This iis the URL to view the video:
https://connect.flashbackrecorder.com/Default.aspx?id=2jEfosHvw9FyLSX5sI9N2g2
If you got this message - I apologize - It is no longer necessary
"The owner of this video requires you to login so they can track views."
Both are FREE ! - No license fee - no maintenance fee
Last edit: Ralph Linkletter 3 days ago
I wanted to enjoy the presentation, but...
I went to this site on my wifes Ipad - it worked fine - I did not have to login.
Can you try again please
I was able to view the video, but I could not find a way to download WINIDE.
@zosralph Perhaps you could put WINIDE on the contributions page?
https://sourceforge.net/p/gnucobol/contrib/HEAD/tree/trunk/tools/
I have watched the video and find it truly impressive—especially the debugger/animator component.
For the sake of completeness—and much to my own disappointment—I must add that I could not use this solution, as my understanding is that it does not support the "free-form" (source-free) format. I want to emphasize that this is strictly my own personal perspective—the viewpoint of a developer working on Windows or Unix applications, rather than on mainframes. In my opinion, being restricted solely to the "fixed-format" is an overly limiting constraint. I believe IBM has never supported free-form syntax on its systems, likely due to the limitations of mainframe Partitioned Data Sets (PDS), which are restricted to 80 characters per line.
On Windows or Unix platforms, no programming language imposes such a limitation, as it would create intolerable constraints for developers. We have discussed this topic before, so I will leave it at that.
My respects, Mr. Ralph—an impressive piece of work!
Thank you Eugenio
So much of the improvement to the debugger can be attributed to Chuck H.
Chuck and I have collaborated on many improvements to GnuCOBOL, WINZOS, WINIDE.
Chuck's expert mainframe technical skills being applied to GnuCOBOL has made the debugger outstanding (IMO), the COBOL closer in functionality to Micro Focus / Rocket and IBM COBOL, runtime services, EXTFH.
Chuck has also implemented many of the CBL_ routines that are needed to make this effort cohesive and very functional.
Kudos to Chuck !
Eugenio regarding limitations:
db/2 would not be functional - the db2 preprocessor is wed to 80 columns
CICS would not work - again the preprocessor
Animation would not work - under the covers columns 1-6 and / or 73-80 are used for various I-O in the animator primitives.
In theory you could use WINIDE to edit, compile, and test - but not debug via the animation.
I think source free would pass thru the compile component- you would have to include the >> syntax in the source.
Eugenio, thanks again for the kind words.
Ralph
Last edit: Ralph Linkletter 2 days ago
Indeed, and a bunch of things (EXTFH, CBL_) are upcoming - hopefully before end of December.
If you have a "current" version of GnuCOBOL and don't explicit specify the fixed reference-format (but that's included in all but
-std=default, which is likely at least used for WinZOS as ibm =-fformat=cobol85), then cobc recognizes free format when used in the first lines of code.Important for documentation would be where the compiler flags are currently set in WinZOS/WinIDE.
Simon,
most of the CBL_ROUTINES.C functions require screenio.c to be implemented.