Hi everyone,
Thank you all for an incredible 2025. It’s been inspiring to see more customers upgrading to Rocket ACUCOBOL extend 11 and adopting VS Code Extension to accelerate modernization without disruption.
Looking ahead, 2026 will bring even more innovations shaped by your needs and feedback. Expect richer content, deeper insights, and more customer success stories that show how to drive innovation with ACUCOBOL.
Welcome to our first newsletter of the year, featuring the comprehensive list of supported platforms and January update of VS Code Extension.

Extend your ACUCOBOL applications with supported platforms & integrations
Explore a comparison chart highlighting supported platform for Rocket ACUCOBOL extend 10.0 and Rocket ACUCOBOL extend 11.0.
Learn more about supported:
- Operating systems
- Containerization services
- Cloud platforms
- Databases
- UI/UX tools
- Deployment options
and more.
VS Code Extension | January Update
Last year, we introduced one of the biggest updates to Rocket ACUCOBOL extend 11 — the Visual Studio Code extension. Your response has been outstanding, and our team is driven by your enthusiasm and the valuable feedback you’ve shared. Thank you to everyone already using the extension.
Link to the extension: Rocket ACUCOBOL-GT - Visual Studio Marketplace
We’re committed to continuously improving the extension to make your ACUCOBOL development experience even better.
In January, we rolled out version 1.3.0, which includes:
Enhancements
- Working Storage Editor - "Find in Objects" - Display and allow navigation to variable usages following search, delete or rename
- Environment Variables - Editing support
- Screen Designer - Collapse/Expand right pane
- Online Documentation - Tutorials
Bug Fixes
- ACUW-2905 - Working Storage - table refresh after each update
- ACUW-2909 - Right Pane - cell settings warning non-specific
- ACUW-2927 - Support opening several screens in parallel
- ACUW-3001 - Compilation fails for partially generated pjt
- ACUW-3074 - Program is not running if its project is created in another project folder
- ACUW-3078 - Screen, variable, event and control names should not contain parentheses
- ACUW-3080 - Multi-project pjt - Build fails
- ACUW-3083 - Working Storage - Entry Field control - variable name should be empty when using 'Value Multiple'
- ACUW-3084 - Working Storage - Decimal value treated as illegal
- ACUW-3087 - Working Storage - Any change in the screen designer triggers an update of the working storage
- ACUW-3088 - Working Storage - Occurs field causes error stack trace to appear on invalid text
- ACUW-3089 - Project view - projects are not sorted by name
- ACUW-3120 - Working Storage - items are not deleted if used as a property value of control
- ACUW-3144 - Copy/Paste actions outside the extensions do not work as expected while webview is open
- ACUW-3155 - Reverse highlight - incorrect when program name equals screen name
- ACUW-3178 - Working Storage Editor - find/delete variable should be case-insensitive
- ACUW-3189 - Build configuration error shown for non-acubench folders
- ACUW-3197 - Working Storage - Rename warning should not appear for case changes
- ACUW-3198 - Working Storage - Entry Field control 'Value Multiple' issue
Voice of ACUCOBOL
Thanks to everyone for being part of this vibrant ACUCOBOL community! We’d love to hear what would help you get even more value from your ACUCOBOL applications this year.
What would you enjoy seeing more of: feature walk‑throughs, real modernization stories, industry examples, or even something fun like ACUCOBOL memes?
Share your ideas in the comments. Your input guides what we create, and together we can make this space even more valuable for you and your business.



