Rocket® Visual COBOL®

Hi,I am posting this question on behalf of a customer, to ensure it goes to the relevant forum and a place they they can see the post. Once I post this I'll share the link with the customer and ask to reply/comment here also.They ask:Does somebody know how to translate the following C#-Lambda-Command to Visual Cobol ?Example (the second last line):private void FlexGrid_Load(object sender, EventArgs e){string conn = Util.GetConnectionString();var ds = new DataSet();string[] tables = "Customers, Orders".Split(',');foreach (string tableName in tables){Util.FillTable(ds, tableName, conn);}// Defining relation between master and detail gridds.Relations.Add("Customers_Orders",ds.Tables["Customers"].Columns["CustomerID"],ds.Tables["Orders"].Columns["CustomerID"]);flexGrid.DataSource = ds;flexGrid.DataMember = "Customers";flexGrid.RowDetailProvider = (g, r) => new C1FlexGridRowDetail();flexGrid.AreRowDetailsFrozen = false;}}They have used the C# to COBOL convertor website but the code that

Good morning.I'd like someone to explain how the cobutf8 utility works to see if we can use it in our company.We work with Microfocus Visual COBOL 8.0 for Eclipse (Unix/Linux).The database is Informix, and a few years ago we migrated to the UTF-8 locale.The OS has LANG=es_ES.UTF-8.However, some integrations with other companies require files with a fixed position structure. We've found that with UTF-8 encoding, there's a left shift for each UTF-8 character written. Currently, we've added calls to iconv before each move to the file variable, but that's very cumbersome when the file has many fields.

The following code crashes when it is executed within Visual Studio 2022: CALL GetCurrentDirectory  USING BY VALUE     PC-PATH-LENGTHBY REFERENCE CURRENT-PC-DIRECTORYRETURNING iRetEND-CALL.it fails with the error message: 173     Called program file not found in drive/directory: GetCurrentDirectoryAI updated the PATH variable to include the folders where the COBOL runtime exists. So why does it not find the Windows API function? Is this a limitation of the PE version or some other property to build has not been set correctly? Any help is appreciated. Kevin

Hi ,we works with Micro Focus Visual cobol 8.0 for Eclipse on linux/UnixWe have a program  with a file that we defines so:file-control.     select prevcob    assign to wk-prevcob     organization is line sequential.data division.file section.fd prevcob.01  reg-prevcob               pic x(185).and a working variable that defines the file structure as follows:01 wk-reg-prevcob-pru.    10 prevcob-nombre-pru            pic x(40)      value spaces.    10 prevcob-impdivisa-pru         pic 9(16)v99   value 0.    10 resto                         pic x(127).We define a cusor that obtains data from a database with UTF-8 locales in Informix and passes it to the variables of the working (the host variable are defined like pic x(300) and pic s9(16)v9(2))move clinombr                    to prevcob-nombre-prumove srvimpdivi                  to prevcob-impdivisa-pru we write the file as follws:write reg-prevcob from wk-reg-prevcob-pruThe problem is that when field prevcob-nombre-pru contains a utf8 ch

Is there any documentation on help in converting from Fujitsu COBOL to Visual COBOL? 

After installing the Visual COBOL PE, a took a utility program written in Fujitsu COBOL, to see how much of the source would or would not compile. There were few lines of code in the utility program that did not compile and I changed and/or deleted them so as the original source compiled successfully. However, the source included the COPY WINDOWS statement and that is where the majority of the errors occurred when compiled the windows.cpy file! My first thought was that the original source was to blame. I subsequently took the COBOL source template  file that is created when a new project is started. Below is the contents of that file:         identification division.       program-id. Program1.       environment division.       configuration section.       data division.       working-storage section.       COPY WINDOWS. *> pick up Windows defines       procedure division.           goback.       end program Program1. The above code produced the same errors in the windows.cpy file.

I have requested to download Visual COBOL Personal Edition, but I have not received an email or reply to download Visual COBOL Personal Edition. What should I do so that I can download Visual COBOL Personal Edition?

The book is by Micro Focus, which is the previous owner of Visual COBOL. It references available materials at their website: http://www.microfocus.com/visualcobolbook. The book itself is copyright 2017 by Micro Focus. Following that link results in a 404 (page not found) error. Is there a current website that contains the materials related to the book?Concerning murach’s mainframe COBOL, the book is copyright 2004, Mike Murach and Associates, Inc. It also makes references to Visual COBOL, but given the copyright date, I can see any links provided in that book as being more outdated than the Visual COBOL book. Is there a current website that contains any materials related to that book?

I filled out the digital form with my email, as you are supposed to do to get the license to use the product. But I have not received a license code via email yet. I was hoping someone here could help me. 

I have successfully downloaded Visual COBOL. Reading the pdf, I find it talks about which versions of Visual Studio are supported. I think the doc may be somewhat outdated since it doesn’t talk about .NET 8 or Visual Studio Community 2022 edition. The first recommended topic to view is 8 years old, so I don’t think it applies. I am withholding installation until I know it will work with my system. I have:--HP Pavilion 64-Bit Gaming LaptopAMD Ryzen 5 Processor16 Gigs RAM1-TB Internal StorageWindows 11 Home EditionExternal 8-TB Solid-State Hard DriveVisual Studio Community 2022 64-bit Edition, Version 17.14.24Will Visual COBOL work with my system? 

Hey everyone,As we step into 2026, one thing is certain: GenAI will remain a major topic this year. That raises an important question — how can you leverage GenAI to accelerate COBOL modernization?This question inspired our latest insights article:✅ When generative AI delivers real value in COBOL modernization, and when it can lead to dangerous hallucinations✅ How to address the skills shortage and improve knowledge transfer using GenAI✅ What makes Rocket Software’s approach to GenAI different, ensuring you get insights you can trust for your modernization projectsRead the full post here: The Role of Generative AI in COBOL Modernization | Rocket SoftwareIf you have any questions or want us to dive deeper into any of these topics, let us know in the comments. We’d love to hear from you!

We currently have a native COBOL application that uses dynamic SQL (via OpenESQL) to fetch, insert and update into Microsoft SQL.This includes varbinary(max) columns which we have working and I suspect it was based on the demo which was available from this link https://community.rocketsoftware.com/rocket-visual-cobol-28/demo-using-the-varbinary-max-column-type-from-cobol-4560. Unfortunately the link to the actual demo is no longer available.I now have the fun and games of trying to convert this logic to .NET core Visual COBOL and I am really struggling to work out how to ‘stitch’ the 65k blocks back together into the correct format and would really appreciate some guidance on this (the same goes for splitting it into the 65k blocks to insert/update).Is there any chance for the demo mentioned to be converted into .NET Core VC so that I can refer to it and work out what I need to do?Thanks in advance 

I think that no, but…Can I do something like that?:       77 lsMethod string.           Move 'gabert' to lsMethod           Invoke Classes lsMethod returning QuebraGalho  Hugs.Antonio JoãoVisual COBO + Visual Studio.

Hi everyone,Thank you again to everyone who joined the State & the Future of COBOL webinar.  If you missed it or would like to share it with your colleagues, here is the recording: The State & The Future of COBOL | Rocket SoftwareStay tuned and turn on the Rocket Forum notifications so you don’t miss the next event. Here are the quiz winners:Marc C.Sebastian S.Thibaut C.Elsabe A.Frank B.Jebastin K.Paul M.Jonathan S.Juan U.Florian G.And then Allan L. who guess the author of the COBOL quote.We'll share the gift details with everyone next week.Best,Rocket COBOL team

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 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

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 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?

Visual Studio 2022, Visual COBOL 11 Update 1. When migrating old native COBOL code to COBOL .NET which has lots of reference modification code you have to sometimes work out something simple as the length of a string.In OO COBOL you had character arrays and you could get “size” or “sizeinbytes”. Due to my very poor understanding of what a character array was many years ago I got unstuck when using simplified Chinese to do reference modification as getting the “size” means how many simplified Chinese characters are in the array and doing reference modification would truncate the data because I didn’t use “sizeinbytes”.So now moving to COBOL .NET I’d better check the behaviour of this and see how it works.I have a simple C# winform Thread.CurrentThread.CurrentCulture = new CultureInfo("zh-CN");Thread.CurrentThread.CurrentUICulture = new CultureInfo("zh-CN");  This is passed into a C# class and and the RunUnit started.The data is then passed from the class into 2 working storage fields, 1

Hi,I have found that the EXIT PARAGRAPH doesn’t work in .NET COBOL. Is this an error or is it deliberate, and if it is deliberate then is there an alternative?Thanks in advance