Rocket® Visual COBOL®

so the following; 01 di-val string occurs any. set size of di-val to 1. move "123" to di-val(1) set size of di-val to 2. move "ac" to di-val(2) When "set size of di-val to 2" is executed, di-val(1) is set to null (ie. all elements in the array are set to null) Is there any way around this or an alternative approach. I basically want an array that can contain strings of varying lengths without taking up too much memory.#managedcode

I am taking the Micro Focus COBOL Fundamentals course (https://www.microfocus.com/en-us/cobol). I have installed the "Learn COBOL" extension into my pre-existing Visual Studio Code installation (using the extensions menu). Following the video instructions I have created a file called "Hello World.cbl" and typed in the COBOL code suggested. My program runs fine, but it does show an error as shown in the screenshot below. This suggests to me that something about my Visual Studio Setup is not correct. I had to add .cbl as a file extension because it did complain about that. So I assume there is also something else not correctly applied from the Micro Focus extension installation. The video at this part of the course suggests that we write this Hello World prog

Installed Cobol software: Micro Focus Visual COBOL Development Hub 7.0 - Patch Update 18 Invoking debug by setting export DEVANIM=+A and trying to debug a program but getting below error and unable to proceed with the debugging.

Hi, is it possible to know the encode of a string in cobol?

We have been implementing an upgrade from Visual COBOL 2.3.2 to COBOL 8.6 and have been utilizing it within our development environment from Visual Studio.  We have now moved to our TFS server which is 14.114.26403.0 (Tfs2015.Update4) running on Windows Server 2016 Datacenter. Initially our TFS build was failing due to the missing COBOL version in our project files however after this was updated, we received errors relating to the MicroFocus.COBOL.CurrentVersion.targets.  The first issue was with the same version error, however after fixing the version configuration in the targets file we are running into more issues with the builds.  Before I go modifying anything else to have this working, I'd like to ensure I am going along the right path. What I have done so far: Created an offline Visual Studio 2019 Enterprise layout with all of the required packages.  Installed Visual Studio 2019 Enterprise Performed all of the steps

Hi, we works with Visual Cobol runing in UNIX servers and our BBDD use UTF-8 encodig. Now we are starting to transfer informatión with other companies using API´s. The problem we have in this moment is that we recive the information ANSI encode and we need convert it to UTF-8 encode. is there some way to do this in cobol?

I have Visual COBOL 9, UnixODBC 2.3.9, Microsoft ODBC Driver 18 for SQL Server installed on RHEL 9. odbcinst -junixODBC 2.3.9DRIVERS............: /etc/odbcinst.iniSYSTEM DATA SOURCES: /etc/odbc.iniFILE DATA SOURCES..: /etc/ODBCDataSourcesUSER DATA SOURCES..: /xxxxxxx/odbc.ini I have ODBCINI set to xxxxxxx/odbc.ini LD_LIBRARY_PATH = :/opt/microfocus/VisualCOBOL/lib:/opt/microsoft/msodbcsql18/lib64:/usr/lib64 When I ran a simple COBOL program to connect to the database, I keep getting the following error:- OpenESQL Error: Unable to load ODBC Driver/Driver Manager. Ensure that yourdatabase environment is set correctly.Connection to database failed: Sqlcode = -0000010000 Sqlstate = IM001 Sqlerrmc = Any help/suggestion will be appreciated. Thanks!

youtu.be/X6YifKnVuHg#Videos

Hello, As I understand, there are 3 ways of dealing with XML (please correct me if I'm wrong): XML PARSE - a set of statements that are coming from IBM Enterprise Cobol. This syntax is allowed for compatibility reasons XML Extensions -> XML IMPORT/EXPORT syntax that is pure MF XML Extensions -> ORGANIZARION IT XML syntax that is also pure MF and more Cobol-like syntax. With the first one everything is clear. My question is concerning the difference between the points Nº2 et Nº3. Which one is advised to use? Any limitations? How to make the choice? There are the same libraries behind this 2 syntax? Thank you in advance.#xmlparse

Hi there, I have some questions about Visual COBOL for Eclipse Personal Edition. As I know, the PE license was for 1 year, renewable. I've installed it less than a year ago, then opening it now it's saying "Unable to find a license on this machine"... Once checked in https://my.microfocus.com/myproducts I see the license was like for 3 months... Before it was automatically renewable directly from Eclipse. Now it's not the case. How can I renew my PE license? Thank you in advance.#VisualCOBOL

Our application uses Microfocus Visual cobol 7.0 version and frontend application is in JBOSS. We are connecting the frontend (UI screen) and backend (COBOL) through activeMQ version 5.16.1. In the current logic, the activeMQ address with port number of 61616 and user_id and password are hard-coded in cobol module to send/receive the value from frontend to cobol module and vice versa. I am trying now to enable failover transport logic of activemq to acquire high availability. Logic can be included in the JBOSS configuration for failover as  "<config-property name="ServerUrl">failover:(tcp://broker1_url:61616,tcp://broker2_url:61616)</config-property>". We need the failover logic in cobol code to test the HA.

We are upgrading from NetExpress to Visual Studio/COBOL 8.0 We have a program that runs fine under NetExpress but with Visual COBOL it error with SQLCODE = 000019514-  (Cursor is not prepared) The program is doing the first fetch fine but gets the error on the second fetch, we are doing an update on another table between the fetches but the DB connection is not being disconnected (like in other 19514 issue I have seen). We are using transaction level commit, so a commit is done between the fetches. Any help would be appreciated. Thanks

I am trying to manage a pipe and for some reasion the compiler refuses to recognise the type i use; invoke pipeSec::AddAccessRule(new System.IO.Pipes.PipeAccessRule("Users", type System.IO.Pipes.PipeAccessRights.ReadWrite, type SysSec.AccessControl.AccessControlType.Allow)) it takes exception to "type System.IO.Pipes.PipeAccessRights.ReadWrite" even though it's ok with "System.IO.Pipes.PipeAccessRule"  and "SysSec.AccessControl.AccessControlType.Allow" where SysSec is mapped to SystemSecurity in the repository. Any help is greatly appreciated. Thanks Micro Focus Visual COBOL Version 8#COBOL

When moving a group item that contains a null to another field. The resulting field only contains characters up to the null. Here is a project that demonstrates the issue Any help is greatly appreciated Thanks#managedcode#VisualCOBOL

in sqlplus i was able to executeSELECT XMLELEMENT("EMPLOYEE",XMLATTRIBUTES('RAM' "NAME"),1022) FROM DUAL;but when compiling  the pro cobol program000001 IDENTIFICATION DIVISION.000002 PROGRAM-ID. XMLGEN.000003 ENVIRONMENT DIVISION.000004 INPUT-OUTPUT SECTION.000005 DATA DIVISION.000006 WORKING-STORAGE SECTION.000007      EXEC SQL BEGIN DECLARE SECTION END-EXEC.000008      01 XML-VAL       PIC X(100).000009      EXEC SQL END DECLARE SECTION END-EXEC.000010     EXEC SQL INCLUDE SQLCA END-EXEC.000011 PROCEDURE DIVISION.000012 PERFORM PARA-FETCH THRU PARA-FETCH-EXIT.000013 EXIT PROGRAM.000014000015 PARA-FETCH.000016          EXEC SQL000017   &

Hi, Currently we are using Micro Focus COBOL on windows. I have the following query on migration from 32 bit COBOL  to 64 bit COBOL . What are the necessary changes I have to do from Micro Focus end? I was not sure where to start as well. Please guide the same.

Hello, Currently we are using COBOL and DATACOM as database. Is Micro Focus COBOL supports DATACOM ??  Thanks Subbu

This is happening immediately upon the region starting up.  We can see in the logs that it finishes creating all the SEPs, and 10 seconds after all the SEPs abend with the message "CASCD0154S SEP 00001 for ES PROD abended by signal 4294967295". Our clients are using 10 SEPs, and they all abend the same way. See part of the log file below. The rest of the log file looks normal. The most recent clients are in versions "ED6.0/20230530_PU25" and "ED6.0/20230630_PU26". Has anyone had this reported? Thanks. 231023 05010373 5544 PROD CASCS5100I Communications Process instance 01 is ready to accept requests 05:01:03231023 05010389 CASCD0127I SEP 00001 created for ES PROD, process-id = 2448 05:01:03231023 05010392 CASCD0127I SEP 00002 created for ES PROD, process-id = 6484 05:01:03231023 05010392 CASCD0127I SEP 00003 created for ES PROD, process-id

We are trying to update to Visual Cobol DevHub 8.0 (Patch Update 9) from DevHub 7/DevHub 6. and we are getting below error when compiling a cobol program. The program or the compilation script is not changed and module is getting compiled without any error in DevHub 6 and 7. Even in DevHub 8 the module is getting compiled without any program errors but when creating .o file, below error is displayed. Kindly help to resolve the issue Current Configuration :Base Directory : /projects/pr/server/server** -- **Compiling : BATCHCON.cblM

Just an information request. Is there anywhere a document that lists the extent to which Visual COBOL adheres to the ANSI/ISO COBOL standards? Obviously COBOL 85. But what about 2002, 2014 and 2023? I know that MF produced Object Oriented support (Object COBOL) but I've not been able to find the extent to which it differed from the standard. I'm not interested in anything related to .NET - essentially Native (not Managed) coding. Thanks

We have recently migrated our product to AWS cloud environment, our product uses Visual Cobol version 7.0 and I am looking for recommendations regarding Visual cobol code scanning tools that are effective in identifying and mitigating code vulnerabilities.#VisualCOBOL

Hello,  I am currently working on a Unix server (Redhat 8 and AIX 7.3) to compile Cobol programs by using Micro Focus Cobol V8.0 . To compile these programs I use the 'cob64' command line. When there are errors in source code, I get this kind of log (for AIX) : *===============================================================** Micro Focus COBOL V8.0 revision 000 Compiler* (C) Copyright 1984-2022 Micro Focus or one of its affiliates.* REF GNR-078800000AM* Total Messages: 1* Unrecoverable : 0 Severe : 1* Errors : 0 Warnings: 0* Informational : 0 Flags : 0

in sql management studio i can use following command: use lohn;godeclare @loc_zahl as intset @loc_zahl = 0if not exists (select * from sys.objects where object_id = object_id(N't_svdata') and type in (N'U'))begin    raiserror('t_svdata existiert', 16, 1)end/* select * from t_svdata */select @loc_zahl = count(svd_schl) from t_svdataif @loc_zahl > 0   delete from t_svdata/* drop table t_svdata */goselect * from t_svdatago but when i use this in vc, the declare will not be accepted. How to declare a unique variable? Is there a precompiler or debugger to debug the mssql commands in a cobol program here the cobol statement: EXEC SQL                               &n

Hi, Good Afternoon!!! Need Help for the below Errors while compiling a RM COBOL With Visual COBOL. I am trying to CONVERRT the RM Program into Visual COBOL Version  USING the Microfocus as Dialect. I am getting the below Compilation error for one of my Program. And seems the RM Statement is not accepted in Visual COBOL. Here is the code :-   WS-ACCEPT-LAST LINE WS-CRT-BEG-LINE POSITION 13028600 PROMPT ECHO. And The error is :- COBCH0012S Operand ECHO is not declared YYYYY.cbl /CBL_RTE line 328 COBOL  Another issue :-  DISPLAY DISPLAY-HEADER-1LINE WS-CRT-BEG-LINE POSITION 1 REVERSE. Error :-  COBCH0012S Operand REVERSE is not declared YYYY.cbl /CBL_RTE line 522 COBOL Thanks !!

Micro Focus Visual COBOL version has recently been upgraded from version 6.0 to version 7.0 for our product. In version 6.0, we had the patch 18 changes. We need to confirm if we need to add patch 18 after upgrading to Cobol version 7.0. Will Micro Focus COBOL version 7.0 include the patch 18 changes?#Microfocus#MicroFocusVisualCobol