Rocket® Visual COBOL®

Currently, having the "Tools > Options > Debugging > Micro Focus COBOL > Suspend at 'STOP RUN'" option set, the debugger visually appears to stop before the final line is being executed: From above screenshot you can see that it looks like the CALL statement has not been executed yet. But actually, execution has already passed the final line in the code.This current behaviour is very irritating.Furthermore, I'm used to continue (by hitting <F5>) a successful program when it's halted instead of aborting it (by hitting <SHIFT> <F5>). So, it's cumbersome to alter that common behaviour just for the "Suspend On 'STOP RUN'" feature (see error message above). So, I'd like to suggest four improvements regarding the "Suspend On 'STOP RUN'" feature:When building a DEBUG build, have the COBOL linker add a terminating __debugbreak operation (or Debugger.Break method) to the generated code

Problem The Visual COBOL or COBOL Server setup fails with the following error: "Service 'Micro Focus Directory Server' (mf_CCITCP2) failed to start. Verify that you have sufficient privileges to start system services." The installation logs also report the following error: Micro Focus COBOL Server -- Error 1920. Service 'Micro Focus Directory Server' (mf_CCITCP2) failed to start. Verify that you have sufficient privileges to start system services. Applying execute package: cobolserver_50x86, action: Install, path: C:\\ProgramData\\Package Cache\\{A1DD402A-9C93-4A25-8505-70C3603C4966}v5.0.00256\\cs\\cobolserver_50x86.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" INSTALLDIR="C:\\Program Files (x86)\\Micro Focus\\COBOL Server" ECLIPSEINSTALLDIR="" BUILDSERVER=""' Error 0x80070643: Failed to install MSI package. Error 0x80070643: Failed to execute MSI package. Error 0x80070643: Failed to configure per-machine MSI package. Applied execute package: cobolserver_50

How many retail banking users do you estimate are taking advantage of the TRIAD COBOL-based services?#VisualCOBOLUniverse2020

How long does it take to learn object-oriented programming with modern COBOL? #VisualCOBOLUniverse2020

Can you give us an example of the benefits of using objects and Frameworks in our existing programs?#VisualCOBOLUniverse2020

How long does it take to transform COBOL applications?#VisualCOBOLUniverse2020

I can see that you are using AWS with Kubernetes.  Can you do the same with Azure?#VisualCOBOLUniverse2020

If we are not using 'MAIN' section in our COBOL code, then what will be the "MAIN" box in flow chart? In other words, is the "MAIN" box in flow chart is due to Procedure Division or due to 'MAIN' Section?#VisualCOBOLUniverse2020

When extracting code to a program, can the new linkage fields be put into a copybook?#VisualCOBOLUniverse2020

Are the Refactoring features demonstrated only in Visual studio IDE or they are also available in eclipse IDE?#VisualCOBOLUniverse2020

In the session, there was talk of refactoring to create APIs or RESTful webservices from existing COBOL applications. Can you explain what technology options are available to deploy COBOL code as an API?#VisualCOBOLUniverse2020

Hi, I am trying to compile my JVM Project.Using the include-command does not work, the copy will not be found:EXEC SQL       INCLUDE HVEND-EXEC....-> cobol] COBCH0012S Operand HV-T-BEZUG is not declared HV-T-BEZUG ist declared in the copy HV.Using the copy HV by the command 'copy HV' there are no problems.My directives :hide-message"1158" REMOVE(NAME) REMOVE(USER) nospzero DATAMAP hostnum-compare"2"hostnum-move nobound nomfcomment assign"external" defaultbyte"00"notrunc setting adv NOKEYCHECK filetype"11" sequential"record" HOST-NUMCOMPARESIGN-FIXUP TRUNCCOPY"16" IDXFORMAT"8" CONSTANT COBCONNECT "TRUE" CONSTANTCONREUSE "TRUE" CONSTANT COBLOG "FALSE" REMOVE(BYTE) REMOVE(DECLARE)REMOVE(PARAMS) COPYEXT",cbl,cpy,mf,CPY,CBL" ILEXPONENTIATION "FLOAT"CHECKDIV "ENTCOBOL" NOBOUNDOPTSQL Pre Dirs:SQL(DBMAN=JDBC) S

I noticed that two project setting have double entries: After fiddling around a bit I have a feeling they both seem to serve the same purpose.► Why do they exist twice? What's the exact difference? PS: From what I also noticed:The entries on the COBOL Link page override the entries on Application page.Clearing the entries on the COBOL Link page copies the Application page entries over to the COBOL Link entries.I would have expected a drop-down for Entry Point, providing me with a list of all available entry points in the project.#application#Projectsettings#COBOLLink

Hi,Getting this error whiler creating COBOL project in Wondows 10:Errors occurred during the build.Errors running builder 'Micro Focus Project Builder' on project 'testproj'.Truncated class fileThanks.Gagan 

Has anyone experienced this error and know how to correct the problem?  It was working fine yesterday before the update occured.  I uninstalled/reinstalled Visual COBOL Personal Edition to no avail.The "MicroFocus.Cobol.BuildTasks.Cobol" task could not be loaded from the assembly C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\MSBuild\\Micro Focus\\Visual COBOL\\v1.0\\MicroFocus.COBOL.BuildTasks.dll. Method 'get_SourceFileExtension' in type 'MicroFocus.COBOL.BuildTasks.CreateCobolManifestResourceName' from assembly 'MicroFocus.COBOL.BuildTasks, Version=16.0.0.0, Culture=neutral, PublicKeyToken=0412c5e0b2aaa8f0' does not have an implementation. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

At this time, I don't need the left margin, so it's currently loss of workspace to me.So far, I couldn't find an option yet to hide it.Can the left margin be hidden in Micro Focus option settings?

Hello All,I have converted my Netexpress5.x Projects to Visual Cobol, but continue in the Moment with Dialog System Screens, i have no experience with dotnet Screens/Windows!Who want to share his experience?Where is it possible to buy any Standard moduls to implement in new programs, toolbar, taskbarI don't want to do many Errors and reject all developments.Thanks for your help.The used database is MSSQL or other SQL-Database, here i can take the part from netexpress! And don't use mf isam files at this time!

With the current version of Visual COBOL it's impossible to inspect multidimentional table data items in a debugging session: Visual COBOL should be able to inspect multidimensional table data items like in this sketch: 

  Utilia S.p.A. un caso di eccellenza tutto italiano! A 60 anni dall’introduzione del COBOL, Utilia S.p.A racconta come fare Digital Transformation per il propiro Successo, al servizio del mondo Energy e Utilities. Speaker: Stefano Nicoloso - Responsabile Sviluppo Software e Infrastrutture Applicative, #Webinars#COBOL#SoftwareeInfrastruttureApplicative

GOOD MORNING EVERYONEI have a problem and have not been able to fix it. Working with Windows 10, single user environmentMicrosoft Visual  Studio 19Micro Focus COBOL Version 5.0Working Directory is called G2, on drive CAll source, executable, data, copy members are in that directory. We are able to compile properly, and execute the programs individually ; however, if program A, calls program B, then the error occurs . We installed, repaired, deleted an reinstalled the compiler but still get the same error. Investigating via the internet, we found some comments about the %path% not being set properly, and the recommended solution is to use REGEDIT and eliminate the quotes "" from the %path%. We reviewed the register and there are not quotes in the path.  Could someone help? Thanks in advance

The "Show All Files" button in Visual Studio Solution Explorer doesn't work with COBOL projects: Without this functionality, it's hard(er) to add existing files to the current project.

Hi,We are doing a POC in our organization to prove a Cobol program can call a restful API(built in .Net C#). We generated the input and output JSON schema files from the JSON data using a free online tool(JSCON schema draft 6) and used in Visual studio 2012 to generate the clients. Since the generated client had the service address blank(it will be auto populated if we generate the client from wsdl for SOAP services), we manually types in the URL to be called. However, we are getting error "Service name not found in IDT" when we executed the client program. I am not sure if we are doing something wrong in this process. Can someone help us ? Please notes that we use enterprise server version 3(enterprise developer ver 3 in machine).

Creating a COBOL console application solution I don't seem to be able to run the compiled EXE file by double-clicking it.I get a system error message telling me that "cblrtsm.dll" is missing: I can debug the file without flaw from within the IDE.Am I missing something? How can I start the EXE file from the Windows shell?I read through the documentation at Building COBOL Applications and Running Applications (Native COBOL), but the information there couldn't shed any light on my problem. The only issue I found in the forums so far didn't yield a result, too.

I noticed that negative numbers seem to be sort of encoded by Visual COBOL when written to line sequential files. PIC S99 VALUE -2, for instance, is stored in a line sequential file as "0r": Is this by intention? I couldn't find any documentation describing how negative numbers are stored in line sequential files. Until now, I would have believed they were stored like any other literal value (e.g. as "-02").Just in case, please find a sample project attached, depicting the issue.Your help is appreciated.

I noticed a setting in the COBOL project settings that may clash with other projects in a Visual Studio solution when compiling for x64 processors: Apparently, the Visual Studio 2019 MSBuild platform target (1) is ignored while at the same time a proprietary Platform Target property (2) has been added in project settings.From what I can see so far ...the proprietary setting is pointless as it is ignored by the compiler(i.e. no compiler settings are changed when this value is changed (see Build Settings text field at the bottom of the COBOL settings page))no MSBuild platform target is available for x64 in the solution (1)The compiler appears to compile to the MSBuild platform target (3), ignoring the proprietary setting (2)As a beginner to COBOL (particularly to Visual COBOL) I'm anything but sure and I'm not able to set-up a sample solution at this time; yet, adding a 64 bit .NET project to this solution and adding dependencies to the COBOL project should result in failure