Skip to main content

[archive] Acubench or not?

  • October 6, 2010
  • 14 replies
  • 0 views

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?

14 replies

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
Hi,

We use AcuBench to paint our screens, but we generally code the PROCEDURE DIVISION ourselves.

Ian

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
we are hard core coders ^^
using textpad as editor

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
We use AcuBench
In very specific cases we edit the resulting src/cbl file.
We edit the marker tags so it doesn't regenerate a certain bit of code which we've rewritten.

Generally speaking with screens we terminate the accept and call code in an exception other procedure.

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
We use AcuBench
In very specific cases we edit the resulting src/cbl file.
We edit the marker tags so it doesn't regenerate a certain bit of code which we've rewritten.

Generally speaking with screens we terminate the accept and call code in an exception other procedure.

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
We use vi.

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
That's hard core man! Don't let me down by telling me you're actually using VIM though :D

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
Ian - I will let you down. I am using GVIM - with a mouse.

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
Ian - I will let you down. I am using GVIM - with a mouse.

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
We use Acubench for screen develop and take advantage of the before and after procedures and when converting character screen programs we have developed a standard that allows us to switch back and forth from GUI to Character and vice versa for development.

We use both the Acubench code editor and VEDIT which a wonderful editing tool.

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
We use acubech to design screens, menu and generate the code from that. We use it also as editor, but we don't le it generate code for the other parts of the program such as working, linkage procedure etc etc.

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
Hello,

We use only acubench, but .wrk and in some cases .cbl are edited manually to control the tags regenerated.

We code in .evt but events are generated by acubench

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
Hello,

We use only acubench, but .wrk and in some cases .cbl are edited manually to control the tags regenerated.

We code in .evt but events are generated by acubench

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
After 35 years (yes 35 years) of using various editors (VIM in character mode being the latest) I am overjoyed at having Acubench to do some of the hard work for me. We write the procedure division using it, design screens and events with it and even let it generate working storage. We do remove a few of the tags to prevent it screwing up clever bits of code but I would say 95% of what we do is via AcuBench and I love it! It gives me one place to access all elements of the system, including copy libraries and I'd hate to go back to VIM for COBOL. I only have a few years left to retirement (that makes me sound very old) and I intend to keep using Acubench until I code no more!

[Migrated content. Thread originally posted on 05 October 2010]

We try to use acubench exclusively for all things cobol, but finding lots of weird little shortcomings with it, like no events inserted by acubench for thread messaging. And I noticed a lot of the samples people throw around on here are not developed using acubench. So I was wondering what everyone uses to develop their gui cobol applications. Are people using AcuBench exclusively or are they just hard core coders and and not use acubench, or is there some other product out there for painting screens, and managing your GUI code projects?
We have always had a single minded approach to software developemnt (a) generate as much code as you can (b) never modify the generated code (c) ensire the generator has the capacity to insert hand coded routimes where necessary.
From day one almost 30 years ago we used a screen and program generator for all of our software and the advantatge of this is that as new features evolve we just change the generator and regenerate the code. The tool was written in Cobol originally but has since been re-written in Java and saves all programs and screens in XML format which then generate Cobol code using Velocity.
This type of approach allows us to easily explore really big projects with limited risk. The major task we are undertaking in 2011 is to make our generator produce code which will work with Xcentrisity BIS. We believe that this will allow us to put an Apache Pivot GUI web services front end on to our software while leaving much of the core Cobol buisness rules and processing in place.
So we are firmly in the space of using generators, whether AcuBench or homegrown like ours