Product Forums

To our Valued Customers: We wish to inform you of an issue identified in our legacy Mobius viewing clients, DocumentDirect for the Internet (all versions), Mobius Luminist (all versions), or Mobius View versions 8.x or 9.x. As previously communicated, these products have not been supported since January 1, 2020. If you are still using these products, they are considered unsupported software.These software packages were last updated between 2018 and 2021. All versions noted above may be impacted by the issue described in this notice. Continued use of unsupported software is strongly discouraged.Rocket has recently become aware of a situation in which, under extremely high system load (such as when timeout, server busy, or other volume-related errors occur), content requested by one user may inadvertently be returned to a different user, resulting in unintended data exposure. This exposure is entirely random and cannot be intentionally triggered.To address this risk, Rocket strongly reco

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 few lines of code written from 1980s or earlier and conclude COBOL has no place in modern IT is like dismissing smartphones because you once used a brick-sized mobile phone in the '80s. Don't let your memory of COBOL - as it once was and when you once wrote it - cloud your judgment of what it's capable of today. And perhaps most regrettably, don't let that lead you to trade it for something that's little more tha

If so, is there an option to open a copybook? I can not find this essential functionality….

Hi! I am currently testing Visual COBOL 11 against my software, and when I run a program that has Database Connectors in them, I get a 9D,25 error on all the SQL tables that are in the program.Copilot tells me that the 9D,25 means the XFD is corrupt, but I re-created the XFDs and I am still getting the error. I re-created the Aculock DB, and made sure that my ACUFH file is pointing to the correct folder, and I have a valid license.  Is there anything else I can look at? 

I am pleased to announce the availability of Rocket ETX 12.5.4.Customers trust Rocket® ETX as their remote access solution for graphically intensive applications. With 12.5.4, Rocket Software product team is reinforcing its commitment to help customers keep critical IP secure and deliver high quality access to applications as the business needs grow. Improved performance and scalability. New security capabilities including native support for MFA and SSO via the new ETX authentication server.ETX 12.5.4 includes 44 bug fixes and 43 feature requests. For more details you can read the 12.5.4 release notes.Get started today - Download the latest release from the Rocket Customer Community (RCC) or talk to your Account Executive

I installed the latest Personal Edition of Visual COBOL.I'm trying to create a class that inherits from base and I'm getting the message "Inherited class 'Type base' not found".How do I fix this?

Welcome to Rocket® COBOL Fuel, your monthly source for all things COBOL. In this issue, you’ll learn about the first challenge of modernization and get the latest webinar recording.  Release of the year: Rocket Visual COBOL 11.0 Your COBOL applications hold decades of mission-critical business logic and data. They are not roadblocks. They are strategic assets. With Rocket Visual COBOL 11.0 released this year, you can unlock, modernize, and extend the value of these applications without disruption.Modernize your development Adopt Agile and DevOps practices in COBOL development using industry-standard tools and GenAI assistance. Onboard and train developers faster with AI-driven insights that make even the most complex codebases easier to understand. Modernize your infrastructure Run COBOL anywhere, from commodity platforms to containers, microservices, and the cloud. Version 11.0 introduces ARM support for greater deployment flexibility and cost optimization. It also expands coverage of

Welcome to Rocket® ACUCOBOL® Fuel, your monthly source for all things COBOL. In this issue, you’ll learn about the main ACUCOBOL release of 2025 and the first challenge of modernization.  Release of the year: Rocket ACUCOBOL extend 11As 2025 comes to a close, we’re proud to look back on one of our biggest milestones: the launch of Rocket® ACUCOBOL extend 11, the most significant update in seven years.Thanks to our incredible beta testers and this community, we delivered a thoroughly tested and refined release that empowers you to modernize mission-critical ACUCOBOL applications, enhance user interfaces, and unlock new business value faster than ever.This update brings major improvements across Rocket® AcuToWeb™, Rocket® AcuSQL™, Rocket® Acu4GL®, and Rocket® AcuXDBC™, giving you more flexibility and power to meet today’s business demands.Highlights of Rocket ACUCOBOL extend 11:Visual Studio Code Extension Developers can now work with ACUCOBOL in one of the most popular development tools

Hello,I am using Rocket UNIFACE 10.3. As part of our plan to upgrade the database server, we are considering an OS upgrade from AIX 7.2 to AIX 7.3.Could you please let me know if UNIFACE is planned to support AIX 7.3? If there are any existing validation cases or roadmap information available, I would greatly appreciate it if you could share them.Thank you in advance for your support.

Visma Enterprise, a leading provider of HR and payroll solutions for over 250,000 citizens and 1,500 employers, faced challenges with its COBOL-based application environment, including:Limited release frequency (monthly) Manual CI/CD processes Difficulty sourcing COBOL expertiseTo address these issues, Visma partnered with Rocket Software to modernize its infrastructure by:Replatforming COBOL applications to AWS without rewriting Migrating the database to Microsoft SQL Server Automating CI/CD pipelinesThe modernization project was completed in nine months, delivering significant benefits:50% reduction in infrastructure costs Increased release frequency from monthly to weekly 64% improvement in developer engagementThis case demonstrates how organizations can achieve modernization without disruption, leveraging existing COBOL investments while adopting cloud technologies.Read the full case study, here:https://www.rocketsoftware.com/en-us/case-studies/visma-enterprise 

Hello,We are in the process of automating a series of tasks in VS Code, in the tasks.json we defined a couple of tasks. Most of them are simple tasks, that can be executed by triggering a zowe command.Example : {         "label": "01 Clone ZMF package to local Git Repo",      "type": "shell",      "command": "git",      "args":[        "clone",        "ZMF://${input:zmfSubsys}/${input:zmfPackage}",        "C:/Users/${env:USERNAME}/.zmfGitrepo/${input:zmfPackage}"      ],      "problemMatcher": [],    },or     {         "label": "04 Audit ZMF Package",      "type": "shell",      "command": "zowe",      "args": [        "changemanzmf",        "audit",        "package",        "-p",        "${input:zmfPackage}",        "--zmf-p",        "${input:zmfSubsys}",        "--uv1",        "CAUD"      ],      "problemMatcher": [],    }, Now some of the tasks are more complex, where we need the execution of a REST API followed by data manipulations or multiple REST APIs to be executed to create a z

Visual COBOL 11, COBOL .NET, .NET Core -  using methods.When using namespaces why use:       $set ilusing "System.Collections.Generic"Over right clicking on the project, properties ~Namespaces or visa versa?The $set places it in the code vs properties~Namespaces setting it in the project.I think the $set is more visible personally at a developer level, But properies~Namespaces might be better for Pipelines. (Easier to pick up dependencies)What is the benefit of either method?Neil

I have MF Netexpress 5.1 installed on my laptop runing Win7 Ultimate. I want to move To Win11 with fresh installation not upgrade installation.before doing this I want to keep my Netexpress license,, this requires me to Revoke it, is it possible to get a response key after revoke?the name of the installer executable I have:  nxp3251060079 Bel ShattyIT managerManara Inforamtions Tecgnology

Rocket has an Enterprise Analyzer Certified Professional - L4XX training course. The start of the course has a hands-on lab for installing a demo workspace. Task 2 step 5 is to “Add sources manually”; the screenshot in step 7 shows this being done from C:\EA Sources\BankDemo\sources, but as far as I can tell, this is not installed with Enterprise Analyzer. (There are some demo files it puts in every workspace but not the full demo.So where is someone taking the class supposed to get the demo files?The training videos several time to go to the “attachment tab”. There is no attachment tab in the training site, as far as I can find. Nor anywhere else with downloads.I happen to have a .zip file with what I think you need, but only due to another case I had with Rocket.My question is: Where is someone taking the class supposed to get the demo sources from? Is this something that was lost in the migration from Open Text to Rocket?

Hello Team,Currently we have Enterprise developer already available in the system , I am trying to integrate VS Code using Rocket COBOL extension to do a BRD documentation using the Co-pilot features. We have two copybooks extension ,one with CPY and another COPYCOB. The intelisense is  able to identify the CPY copybooks but not the COPYCOB eventhough the extensions are mapped. Is there possibility to re-use the XML files of MFED for the integration of VS code.ThanksSanoop

I have @1000 VSAM files all of which hold the same data for different product types.  The first part of the name of the file indicates the product type. For example:   Product1 filename is FD0001.PRODUCT.INFO, Product2 filename is FD0002.PRODUCT.INFO.   These files are to be read by a Cobol program that populates the "FDnnnn" part of the filename.  Is there a way to have only one VSAM file definition in the JCL stream and query the JES catalog to get the right file, or some other way to avoid having a DD statement for all 1000 files?------------------------------Bruce CheatwoodBWXTLynchburg VA US------------------------------

I am trying to call the direct ODBC API from a Visual COBOL program using Visual Studio 2022. I want to know if there are any specific configuration changes required in Visual studio 2022 to make ODBC calls work correctly, especially when linking DLLs that are not part of the same solution. Also, if anyone has a small sample COBOL program that demonstrates how to call ODBC APIs directly (for example: SQLConnect, SQLExecDirect, SQLDisconnect), it would be very helpful. Could you please guide me on the correct setup and share any sample code?

Your Rocket® MultiValue Modernization Journey Starts with MVISWhether you’re just mapping your modernization journey or already well underway, Rocket® MultiValue Integration Server (MVIS) is the bridge to take your Rocket® UniVerse– or Rocket® UniData®–based applications further, faster, and more efficiently.Top five things you may not know about MVISHow many of these facts surprise you?We released MVIS in June 2019 to empower MultiValue customers like you. MVIS is available for newer versions of Rocket UniVerse and Rocket UniData. Check the Product Availability Matrix (PAM) to see if it supports your environment. MVIS is included with your maintenance agreement. If your maintenance is current, you can order and download MVIS at no additional cost on RBC. Connection pools power MVIS in your production environment. See how connection pools deliver high performance in our short infographic. Your peers already use MVIS for modernization. MVIS is a proven way to bring existing MultiValue a

Dear CustomersWe will be releasing the next version of Rocket Open AppDev next week. Expect version currency updates for Less, Nano and more. Vulnerabilities fixes for Git, Curl, Vim and more. Also, new port for confluent-Kafka. More release details to come soon.Did you know: The mainframe market is projected to grow from $5.33B in 2025 to $7.14B by 2030 (6% CAGR), with hybrid cloud and open-source integration as key drivers.

If you need a quick way to prove services will run on time, see the real business impact of schedule changes, and deliver stakeholder-ready reports, spend 15 minutes watching our demoWhat you’ll see:How autonomous workload orchestration ensures business and application services meet SLAs without constant manual intervention. Live dashboards and pre-built reports that translate run status into business impact for executives and operations. What-if planning: simulate schedule changes, see downstream effects on delivery and SLAs, and compare alternative remediation options.Why it matters:Confident decisions: quantify the business impact of changes before approving them. Faster reporting: produce stakeholder-ready views without ad-hoc data pulls. Less firefighting: reduce escalations by catching schedule clashes and SLA risks earlier.In case the video player does not work for your computer or browser, please feel free to watch it here.Have questions? Reply in the discussion thread below. 

If you need a quick way to prove services will run on time, see the real business impact of schedule changes, and deliver stakeholder-ready reports, spend 15 minutes watching our demoWhat you’ll see:How autonomous workload orchestration ensures business and application services meet SLAs without constant manual intervention. Live dashboards and pre-built reports that translate run status into business impact for executives and operations. What-if planning: simulate schedule changes, see downstream effects on delivery and SLAs, and compare alternative remediation options.Why it matters:Confident decisions: quantify the business impact of changes before approving them. Faster reporting: produce stakeholder-ready views without ad-hoc data pulls. Less firefighting: reduce escalations by catching schedule clashes and SLA risks earlier.In case the video player does not work,  watch it here.Have questions or want a tailored walkthrough for your environment? Reply here or DM me and we’ll set i