Rocket® ACUCOBOL®

Does anyone know if there is documentation on the “*** System error value = # *** errors? I see them pop up in my logs from time to time, but I’m not able to find what they mean in the AcuCOBOL documentation. I’m using 10.5.1 on RHEL if that matters.Thanks for your help!

We love that you can use OCCURS in the screen section and we use it quite frequently.Now - for the first time - we need a radio-button that gets its options from a table and we don’t know how to get the value.This is what we would like to use:78 T01-MAX VALUE 10.78 T01-GROUP VALUE 03.01 T01-RESULT PIC 9(02).01 T01-TABLE. 02 T01-RECORD OCCURS T01-MAX INDEXED BY T01. 03 T01-VI PIC 9(01). 03 T01-ID PIC 9(05). 03 T01-TITLE PIC X(40). 03 T01-VALUE PIC 9(02).01 SCRPP10-BILD. 02 LABEL LINE 10 VISIBLE 0. 02 OCCURS T01-MAX. 03 RADIO-BUTTON LINE + 1 COL 50

Hi everyone,A few weeks ago, Scot Nielsen, Vice President of Product Management, sat down with Channel Insider to discuss COBOL modernization, a topic that continues to shape enterprise technology strategies.The conversation explored some of the most pressing challenges organizations face when not modernizing COBOL systems, including:Preserving decades of proven business logic without disrupting operations   Making COBOL development attractive and streamlined for both seasoned engineers and new talent   Ensuring robust security for COBOL applications at the core of business, especially when integrated with numerous third-party services“We want to find ways to always help the organization leverage those [proven COBOL applications] rather than having to do something more profoundly risky like a rewrite. From a high-level perspective, it’s about leveraging what works — what you know works as an organization — rath

¡Reserva la fecha! Nos complace invitarte a nuestro próximo seminario web sobre la nueva versión de Rocket® ACUCOBOL extend® 11.13 de noviembre16:00 Spain / 12:00 Buenos AiresRegistrate ahoraAcompáñanos para conocer en profundidad las últimas novedades de extend 11 y disfrutar de demostraciones de sus nuevas funcionalidades.Durante el webinar aprenderás:Desarrolla más rápido con Visual Studio Code Permite a tus equipos desarrollar aplicaciones ACUCOBOL con una de las herramientas de desarrollo más populares y utilizadas del mundo.   Simplifica el despliegue en la nube con Rocket® AcuToW

Hi everyone, This year we released one of the biggest updates for Rocket ACUCOBOL extend 11 -- Visual Studio Code support. The response has been incredible, and we’re thrilled by the enthusiasm and feedback from the community. Huge thanks to everyone who’s adopted the extension and shared their thoughts. Link to the extension: Rocket ACUCOBOL-GT - Visual Studio MarketplaceWe’re committed to continuously improving the extension to make your ACUCOBOL development experience even better. Last week, we rolled out version 1.2.0, which includes: Enhancements Load COPY_PATH Environment Variable directory settings  Working Storage Editor enhancements  Highlight selected items in the project and file tree views Bug Fixes ACUW-2893 -

Welcome to Rocket® ACUCOBOL® Fuel, your monthly source for all things ACUCOBOL. In this issue, you’ll discover how Rocket Software is driving ACUCOBOL modernization, learn Railway Furnishers modernization story, and explore the renewed Rocket ACUCOBOL community.  Rocket Software Advances ACUCOBOL Modernization COBOL and its dialects remain a cornerstone of global business operations, powering 70% of the world’s business transaction processing across industries such as banking, insurance, travel, retail, and government. However, running COBOL and ACUCOBOL that have not been modernized, combined with outdated engineering tools and practices, can slow innovation, increase operational risk, and expose systems to today’s security threats. Organizations with COBOL at their core can no longer afford to operate on outdated applications and systems, or take unnecessary, expensive risks with application rewrite projects. Rocket ACUCOBOL’s latest

Hello ACUCOBOL Community! Last week, we brought together over 50 passionate COBOL and ACUCOBOL enthusiasts right next to the iconic London Eye, and what a day it was! The event was packed with learning, experience exchange, and networking. While every modernization journey is unique, many of you face similar challenges. That's why being part of a community matters. It gives us a chance to learn from each other, find inspiration, and grow together. A heartfelt thank you to everyone who joined us and contributed with insightful questions, ideas, and feedback. You made the day truly special. Here's a quick loo

Hello All, When I tried to run the COBOL program by using the command Wrun32 <program name>, program is getting executed but the DISPLAY statements are not getting displayed in the command line. Can you please help me to fix this? and attached are the Program screen shot and run command. ------------------------------Sireesh Kumar YallaRocket Software Forum Member------------------------------

Hello ACUCOBOL community, A huge thank you to everyone who joined yesterday's How To Deliver Modern UI/UX with Rocket® ACUCOBOL® Webinar webinar! We loved seeing so much interest and engagement as we explored the role of UI/UX in ACUCOBOL applications and Railway Furnishers' modernization journey.  For those who'd like to revisit the content or couldn't attend live, we're excited to share the following resources: Check out the webinar presentation attached to this post

Hello Everyone, I'm looking to debug my ACUCOBOL program to better understand its flow and execution. However, I'm not familiar with the tools available for this purpose.Could someone please guide me on which tool to use and how to download and set it up?Thank you in advance for your support!------------------------------Sireesh Kumar YallaRocket Software Forum Member------------------------------

------------------------------Larry CarlsenPresidentSentinel Hill Software IncWest Vancouver CA------------------------------

Hi everyone, Today's users expect sleek design and seamless experiences. To meet those expectations and stay competitive, ACUCOBOL applications need modern, user-friendly interfaces. Join Dominique Sacre, Product Director for Rocket ACUCOBOL products, for our webinar, "How to Deliver Modern UI/UX with Rocket ACUCOBOL." Discover how Rocket® ACUCOBOL-GT® Extension for Visual Studio Code and Rocket® AcuToWeb® make it easier to create, modernize, and deploy application interfaces across platforms. Sign up here: How To Deliver Modern UI/UX With Rocket® ACUCOBOL® | Rocket Software In this session, you'll learn: How to build a product interface with Roc

Does anyone have any ideas what could cause this kind of memory error in A2W 10.5.1:   MemoryError: Exception ignored in thread started by: <bound method Thread._bootstrap of <Timer(Thread-10067461, initial 2862611264)>> Traceback (most recent call last):   File "/usr/acucobol1051/acutoweb/Tools/Python/lib/python3.8/threading.py", line 890, in _bootstrap     self._bootstrap_inner()   File "/usr/acucobol1051/acutoweb/Tools/Python/lib/python3.8/threading.py", line 918, in _bootstrap_inner     self._set_tstate_lock()   File "/usr/acucobol1051/acutoweb/Tools/Python/lib/python3.8/threading.py", line 913, in _set_tstate_lock     _shutdown_locks.add(self._tstate_lock) MemoryError: Same code/program is been running fine in Acu 10.4.1 and 10.5.0 or at least no similar errors have been written in gateway.log . Now that more and more users have changes to 10.5.1 this memory error comes at lea

COBOL remains a cornerstone of global business operations powering 70% of the world's business transaction processing across industries such as banking, insurance, travel, retail, and government. However, running COBOL that has not been modernized – combined with outdated engineering tools and practices – can slow innovation, increase operational risk, and expose systems to today's security threats. Organizations with COBOL at their core can no longer afford to operate on outdated applications and systems or take unnecessary, expensive risks with application rewrite projects.  However, for many people, COBOL's reputation is clouded by a number of persistent myths and misunderstandings – even those familiar with COBOL may still judge it based on how it looked and operated over 30 years ago. Join us for a LinkedIn Live event on COBOL modernization without myths and outdated perception.

Hi everyone, The idea that COBOL is "stuck in the past" is one of tech's most persistent myths - and one of its biggest disconnects, given how much COBOL is still actively being developed. Even those once familiar with the language can struggle to see how it fits into a modern tech stack in the age of AI. Perhaps you're one of them? There's more than a grain of truth, of course - many COBOL systems do carry the weight of their history. Real-world COBOL often contains layers from different eras, as you'd expect from software that's delivered value for decades. But to examine a fe

Does anyone have any experience in how best to configure processors on virtual servers?  We have a client that upgraded their server and is now experiencing issues with some batch oriented programs (reports, updates) taking noticeably longer to run than on their old server.  Their IT guy has run tests on both old and new servers and is showing stats that in most cases the new server is returning better results.  The programs that seem to be running slower are doing a lot of reading and some rewriting and some report creation.  The IT guy is asking if it makes any difference to the AcuCobol-GT Runtime as to how he configures the processors, such as 2 CPU's with 4 cores each, versus 1 CPU with 8 cores, etc.  We do not do much multi-threading within our Cobol programs, and not at all in a few they are seeing decreased performance in, but not sure what/if any of this processor configuration on a VM matters to the Runtime either, or if it does affect it at all.  Just curious if anyone ha

I am trying to set a windows variable in COBOL that I will be able to read in a C# program I am calling from COBOL. "SET testvar=xx" works at a DOS prompt. However the following does not work. move "SET testvar=xx" to AFLD60CALL "C$SYSTEM" USING AFLD60, 97 END-CALL. | Called ASYNCH so no delay Any ideas would be most appreciated. Thanks, Steve  

Hi everyone, I'm Dominique, product director of Rocket ACUCOBOL products. First of all, thank you for the interest in Rocket ACUCOBOL extend 11. We're excited to see so many upgrades in progress. We're currently preparing a webinar on the modernization of ACUCOBOL applications, and we'd love to feature real customer stories. If you've been modernizing your applications and are ready to share your journey (where you started, where you are today, and what's ahead) we'd be thrilled to hear from you. If you want to share your ACUCOBOL modernization story, leave a comment in this thread or contact me directly via dsacre@rocketsoftware.com  Thank you------------------------------Dominique SacrePrincipal Product ManagerRocket Internal - All BrandsParis FR------------------------------

Hi everyone, COBOL has powered the world’s economy for decades, delivering reliability and scalability. Yet myths and outdated views persist, even among those who have worked with it. Many still picture COBOL as it was 30 years ago, missing how much it has evolved. Let’s separate myth from reality and give you the facts to talk about COBOL with confidence.

Does anybody have a sample to send emails with AcuCobol to Office365? Until now we use sonnectors/dlls like Simple MAPI, Extended MAPI, SMTP or MSMAPI After installing Office 365 it seems we have to use the Microsoft Graph API. But no one knows how to integrate this API. Best regards Martin Richter------------------------------Martin RichterCEORop It Gmbh & Co. KgGermering DE------------------------------

Hi everyone, Today's developers expect a certain toolset for any project, with Visual Studio Code being one of the most popular development tools in the world. To make it easier to attract new specialists and to streamline the development within your enterprise, we've built the Rocket ACUCOBOL-GT Extension for Visual Studio Code, bringing key Rocket AcuBench features directly into VS Code on Windows. (with Linux support coming soon) Import your existing Rocket AcuBench projects, keep your compiler settings, and continue building, editing, compiling, and debugging without missing a beat. Inside the extension, you'll find: Rocket AcuBench

Linux/Windows thin client; runtime 10.51 I need to display any of a series of bitmaps in a grid cell.  I am using WBITMAP-LOAD (I have also tried WBITMAP-LOAD-IMAGES) to load a .bmp file, and I get a handle to the object.  However, these bitmaps will not display in grid cells if the runtime is thin client (if not thin client, it works).  I can display the bitmaps if the grid is not active. The grid is an active-x control called #grid.  ------------------------------Ken Schwartz Lead EngineerSouthWare ApteanOpelika US------------------------------

Hi, we use C$LOCKPID in Linux. Now we have a customer who's working with AcuConnect for Windows and we need something like C$LOCKPID. Is there a C$LOCKPID for windows or an alternative ? I found a post here from 2004, but perhaps there was some progress in the last 20 years ? ------------------------------Andreas WeinandSend invoices to this addressVacos GmbHStuttgart DE------------------------------

Hi everyone, With Rocket ACUCOBOL extend 11 now available, our team is already working on the next set of updates and improvements. As we plan future enhancements for ACUCOBOL products, it's a great opportunity to reflect on how COBOL (and ACUCOBOL) continue to successfully support critical systems around the world. Here are five reasons why COBOL remains ideal for enterprise-grade applications. Designed for business and built to last COBOL was purpose-built for high-volume data processing, complex reporting, and precise financial calculations. Every day, COBOL applications process nearly 200 times more transactions than all Google and YouTube searches combined. High performance and rock-solid reliability have always been hallmarks of COBOL systems. High portability: it runs just about anywhere COBOL applications written decades ago still operate seamlessly on toda