Rocket® COBOL

Is there a way to turn off the code reformatting? We want the code to stay the way it is but every time we change or move a line of change it gets reformatted. We are using VS 2022/MF COBOL 8 Thanks

Join Our Webinar  Building for the Future OpenText Micro Focus Visual COBOL and Enterprise Suite 9.0  Event Details  Date: July 12, 2023Time: 8:00 a.m. PST | 5:00 p.m. CET  Speakers:   Scott Nielsen, AMC Product Marketing, OpenText  Guy Sofer, AMC Product Marketing, Open Text  Modernizing core business systems is now mainstream.  Over 70% of organizations plan to modernize their existing COBOL and mainframe applications. Cloud continues to drive IT transformation, but improving agility is also important for many IT leaders.  Now is the time to start that DX journey with a proven partner in modernization.  Join the Open Text product team for an exciting application modernization and product launch event: the release of Visual COBOL 9.0 and Enterprise Suite 9.0 from OpenText™. Join the COBOL and mainframe community for a closer look at these latest innovations supporting COBOL development and mainframe migration.  During

I'm an ole school programmer getting back into COBOL programming (for fun, not profit) currently using Visual COBOL in VS2022 to produce an application with character-based screens (i.e., screen section) and I have a couple of questions: How can I print a program listing? Ages ago on the mainframe I would print listings showing the assembler code. Is this even possible in my configuration? What are the prevailing COBOL coding conventions? If this question is likely to trigger a war of conventions, please ignore it and I'll make up my own. #standards#Listings#VisualCOBOL

We have a batch system which is being converted from NetExpress to MF Visual COBOL 8. In VS when debugging we are using Environment Variables to define file and report paths. But when the EXE is used in Testing or released to client we don't want the Environment Variable included as the report/file paths will be in the BAT file.   If we don't tick the 'Use variables when building the project' when debugging will the variables be used but when compiling/build for release will the variables be ignored?  In NetExpress we had two projects, a development project where the environment variables would be populated and then a release project which the environment variables would not be entered. I am trying to get away from having to have separate projects, one for development and one for release.

HI Team, I am converting RM COBOL to Visual COBOL. but getting the below error. Could someone please help. I am getting below Warning. Seems this would be an Issue. When I compile this same program in RM It doesn't give this warning.

Hi everyone,Haven't seen an example from NetExpress product that can;1. open an Excel file (say; myfigure.XLSX)2. go to a certain cell (say; A3)3. Then get the cell value and save it in a .DAT cobl datafileAnyone here?  Thank you very much.infoRene#SupportTips/KnowledgeDocs

Hello,I'm having trouble using "Wait for a debuggable attachment" feature of Micro Focus COBOL VSCode extension with "any" parameter : I successfully make it worked starting a "Wait for a debuggable attachment" runtime with "directory" in launch.json : {   "type": "cobol",   "request": "launch",   "name": "COBOL (native): Wait for attachment",   "waitForAttachment": {     "directory": "${workspaceFolder}"   } } But when I change "directory" to "any", it doesn't work anymore : The "wait" runtime starts successfully but it doesn't catch any program cobol (either with environment variable COBSW=+A or calling CBL_DEBUGBREAK in cobol program according to documentation).Instead of, it opens "Animator".launch.json with "any" parameter : {   "type": "cobol",   "request": "launch",   "name": "COBOL (native): Wait for attachment",   "waitForAttachment": {     "any": {}   } } Any idea how to make it work ?Thank you

I created an application with ESQL using Visual Studio 2019 and Visual Cobol 6. Now I have migrated to Visual Studio 2022 and Visual Cobol 8. Since then, the menu item for starting the OpenESQL Assistant is no longer available. Who knows advice.

I am trying to connect with MS SQL Server using acuSql but I get:SQLCODE -1SQLSTATE 08001 01 servername pic x(30) value "(LocalDb)\\MSSQLLocalDB". 01 userid         pic x(20) value "PCANDRE\\andre". EXEC SQL CONNECT TO :servername as C1USER :userid USING :passwd also tried withoud userid. Configuration: ACUSQL_RUNTIME_DLL asqlsrvr.dll However this works: sqlcmd -S (LocalDb)\\MSSQLLocalDB

I am trying to connect with MS SQL Server using acuSql but I get:SQLCODE -1SQLSTATE 08001 01 servername pic x(30) value "(LocalDb)\\MSSQLLocalDB". 01 userid         pic x(20) value "PCANDRE\\andre". EXEC SQL CONNECT TO :servername as C1 USER :userid USING :passwd Configuration: ACUSQL_RUNTIME_DLL asqlsrvr.dll However this works: sqlcmd -S (LocalDb)\\MSSQLLocalDB#Other#SupportTips/KnowledgeDocs#SupportTip

Hi, I am trying to create a build pipeline for a simple cobol console app created using Microsoft Visual Studio. I have installed Microfocus Visual cobol and VS 2022 in an azure VM which I use as self hosted agent in Azure pipeline. While executing the pipeline , I am getting the error  "The nuget command failed with exit code(1) and error(NU1101: Unable to find package MicroFocus.COBOL.Runtime. No packages exist with this id in source(s): NuGetOrg Errors in c:\\work\\1\\s\\DemoCobolApp\\DemoCobolApp\\DemoCobolApp.cblproj NU1101: Unable to find package MicroFocus.COBOL.Runtime. No packages exist with this id in source(s): NuGetOrg)" Am I missing any nuget configuration. Please note that the same app can be build successfully using VS 2022 when running in the same machine. Any help is appreciated.  My actual target is to create Azure CI/CD pipelines for cobol program. Hence I am doing a small poc by creating a small cobol console app. Thanks, Jay#azurepipeline#Knowledgepartner

Hi - We are moving from NetExpress 5.1 to Visual Studio 2022/Visual COBOL 8.0 We have several program that use COMMIT TRANSACTION transname-name  these compile in NetExpress but in Visual COBOL they error with  COBES0100 Incorrect SQL statement syntax near: ONE We are compiling using the same COBOL.DIR. This the a setting, directive or something else that will get the program to compile without changing the code? Thanks

I am using Relativity to define ISAM file.Below is one such exmaple:  File structure [EMPLOYEE] 01  Record-1.      02 EMP-ID         PIC 9(10).      02 EMP-NAME PIC X(30).      02 EMP-DEPT-CODE PIC 9(3). Relativity Definition TABLE : EMPLOYEE EMP_ID      DECIMAL(10,0) PRIMARY KEY NOT NULL.. EMP_NAME CHAR(30) NOT NULL. EMP_DEPT_CODE SMALLINT   NULLABLE. When I am trying to INSERT Value. Insert query has only 2 columns. Insert query is failing for null value in EMP_DEPT_CODE. INSERT INTO EMPLOYEEE (EMP_ID,EMP_NAME) VALUE ("ABC","SWAP") My question : Is there a way to DEFAULT Value inserted into the column(s) not passed via Query? I saw Default Value column in File Definition portion of Relativity but it is not editable.  Any help or guidance is highly appreciated. ### Above query is for reference only. Actual query has 100 columns.  #Relativity#RM/COBOL

In Visual cobol eclipse, While compiling the cobol program XXXXX.pco , getting error as " PCB-S-00106, Unable to open INCLUDE file ....." This is the first time in my machine i am doing compilation.

I am looking for information on how to get list&label to work in our application. Does anyone have used this already and is willing to share the solution with me?

I want my display statements to be put into a file. I have set up compiler option on the COBOL screen. (I want to create COBOL.DIR but not sure where I should put it) Here is a complete list of the Additional Directive I have  DEFAULTBYTE"00"COMPNOTRUNCMFNOADVAPOSTNOFLAGMIGNOBOUNDCONVERTPTRADDRSV"CURRENT-DATE"ADDRSV"TIME-OF-DAY"PERFORM-TYPE"OSVS"ASSIGN"EXTERNAL"OUTDD"SYSOUT"COPYEXT"CBL,COB,CPY"idxformat"8"nolistsql(dbman=odbc)omf"obj"P64 Now under the Application Environment, I have SYSOUT pointing to a file.  With my OUTDD'SYSYOUT' in the compile directives and SYSOUT file I would of expected the displays to be written to my SYSYOUT file but there are not. Is there any other setting that I need to get the display written to my file? Thanks

I'm about to create a support case regarding this. Before I do I'm just curious if anybody has gotten this to work? On a clean Win10 install visual studio 2022, version 17.6.2 visual cobol 8 with PU07 oracle instant client 32 and 64-bit, versions 19 and 21 What I'm trying to do is this: Simple program using cobol and procob with oracle instant client Program reads db name, user name, and password from environment variables Connects to database Reads System Context Updates client info No other dependencies, only copy used is sqlca Before starting Visual Studio two directories are added to the front of PATH instantclient_xx_xx\\sdk - location of procob.exe, installed as c:\\oracle32\\instantclient_19_18\\sdk or c:\\oracle64 instantclient_xx_xx - location of oracle dll:s The solution is int/gnt, debug as console application Compiling isn't a problem. Procob is found, source code is OK. Setting up a 32-bit project and a 64-bits project. Testing four different instant

We are a batch system that is converting from NetExpress 5.1 to Visual Cobol 2022. When compiling we are getting errors with the file name and assign name being the same. This compiles without an errors in NetExpress. ENVIRONMENT DIVISION. CONFIGURATION SECTION. SPECIAL-NAMES. C01 IS H-O-F. INPUT-OUTPUT SECTION. FILE-CONTROL. SELECT G05 ASSIGN TO G05 FILE STATUS IS GT-STATUS ACCESS IS SEQUENTIAL. DATA DIVISION. FILE SECTION. FD G05 BLOCK CONTAINS 0 RECORDS LABEL RECORDS ARE STANDARD. 01 CODE-REC. The error is COBCH0005, User-name G05 not uniquethe error is on the SELECT G05 Assign to G05 line. Do we have to make the file name and assign names different or is there another way?

Hi I'm running into an error when using a cursor that fetches 0 results which results in an error and reports 'SQL error -9514 Invalid Cursor State)'.  We are using the current SQL directives: SQL(DBMAN=ADO) SQL(BEHAVIOR=ANSI) SQL(CHECK) SQL(DB=CSISD) SQL(TARGETDB=MSSQLSERVER) SQL(DEF_CURSOR=RO) SQL(ALLOWNULLCHAR) Running from a Windows 10 VM to SQL Server 2016 on a Windows Server 2012 rd (soon to be Windows Server 2022). I've found that DEF_CURSOR is still valid as per the Micro Focus documentation however according to VS 2019 'Invalid directive. The selected directive is not valid for this version of the product'. Any ideas? James

We are using the Microfocus Database Connectors with Visual COBOL, and I am all of a sudden getting a 9D,00 Error when trying to run my program. It is like it can no longer find the Database?    I haven't changed any of my settings in my script except the name of the Database and Aculock Database that the program is using. What is a 9D,00 anyway  - I can't find that code in any of the error documentation.  I see 9D,01 and higher.

I am trying to to add the Transparent-Color property to Push Buttons in AcuCobol-GT, Version 10.   In the below screenshot, I would like the grey around the buttons to be transparent, allowing the blue to show through.    I’ve attached a couple of the bmp’s that are currently in use.  I’ve tried converting these to 16 color, 256 color and 24 bit bmp without success.         I’ve also tried several different values for TRANSPARENT-COLOR in the push button display, using working storage values as well as the integer itself.  78  WS-TRANSPARENT     VALUE x#c0c0c0.       |Windows Gray 192,192,192 <OR> 78  WS-TRANSPARENT     VALUE x#1000000.    |BM-CORNER-COLOR from ACUGUI.def, as mentioned in the Acucorp doc).  I've tried the following in Display Push-Button: TRANSPARENT-COLOR WS-TRANSPARENT <OR> TRANSPARENT-COLOR  1677

I've been scouring through the forums looking for information on this. We have a lot of Relativity tables and most of them work great without any errors. Sometimes we've run into problems like: Numeric item in key contains nonnumeric charactersNumeric value out of rangeNumeric item contains nonnumeric characters (this one happens on dates too!) This causes problems as I'm trying to SELECT * on a table and when an error happens, the ENTIRE query is halted (Relativity server on linux, connecting via unixODBC). I found a great post by Tom who explains how you can use the Relativity designer to create a function f(x) IsNumeric() or IsValidDate() to get around some of these errors. This has been a great solution so far - because while we intend to fix the programs that allow this bad data to get into the data files, we also really need something that can just query a table and get very row possible, excluding errors. Again, the programs that introduce these errors should and will be fixed

When doing a fresh installation of RMCobol 12.19 the install.sh fails to find the eula.txt.  I see it in a subdirectory and copied it to the installation directory just incase it was a pathing issue but still install fails to get past that point.  #Linux#RMCOBOL

Load error : file 'CBL_FN_INTEGER0OF0DATE_IBM' error code: 173, pc=0, call=1, seg=0 173 Called program file not found in drive/directory 12:52:56. Does anyone know what the file name is for this routine and in which folder does this date routine go? Also, much appreciated if you have a copy of this routine and can attach it to this request. Thanks!

Hi there,today we checked the installation requirements for MicroFocus Cobol Server 6.0 and 7.0. The supported OS version include CentOS 7 and 8 but not RockyLinux 8 or 9.  Because CentOS 7 and 8 will no longer developed and will run out of support soon, is there any plan to support RockyLinux as a non official replacement for CentOS? Best,Thomas#CENTOS#RockyLinux#COBOLserver