Rocket® COBOL

Hi, in version 4.0 of CA constructor types are in a list and the documentation related to an option appears when the option is selected But in version 8.0 this documentacion don´t appears because constructor types are in a combo. How can we see this documentacion or help now?

Hi, we have update from CA 4 to CA 8 and and we have a problem that in version 4 don´t happens We works with BRP and verification process stops once the verifications are finished,but the process don´t dead.  If we execute the  PowerShell script on cmd, the same thing happens, we must click "Close" on the Queue Processor window to continue. We need that process dead completly when we wors in BRP. We have another question, Why don´t  we see this options? 1. Click Options > Workspace Options. 2. Click Verification > Parallel Verification tab. 3. Select either    • Run Parallel Verification in the online tool    • Run Parallel Verification in BRP 4. Adjust the Minimum Queue Processors to improve performance when using an optimized number of CPU cores.

The description for Event ID 1 from source Micro Focus RTS for Visual COBOL 6.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: d:\\psft\\pt85908\\CBLBINU\\SRPCERC.exe Execution error : file 'd:\\psft\\pt85908\\CBLBINU\\SRPCERPE.gnt'error code: 105, pc=0, call=1, seg=0105     Memory allocation error the message resource is present but the message is not found in the string/message table#Events

An application was being migrated from Server Express to Visual COBOL and was being built using a 3rd party build script. The build script directly referenced libcobrts64.so.2 in $COBDIR/lib. But when the build script was run and the system linker tried to link that file it returned the following error:ld-so-1-svr0102-fatal-libcobrts64-so-2-open-failed-No-such-file-or-directoryThis will apply to any of the following files:libcobrts64.so.2  libcobrts64_t.so.2  libcobrts.so.2  libcobrts_t.so.2 Full article: https://portal.microfocus.com/s/article/KM000011863#SupportTips/KnowledgeDocs

When building an application that uses the Pro*COBOL pre-compiler, the SOURCETABSTOP defaults to 8, even if the value specified is 4. The compiler shows the following message: “CSQL-I-049: Unable to support the SOURCETABSTOP directive, defaulting to 8” Full article: https://portal.microfocus.com/s/article/KM000011842#SupportTips/KnowledgeDocs

When trying to save a DSN for Oracle Managed ADO Provider in the Visual COBOL ADO Connection Editor an error is reported that it cannot save the DSN. Full article: https://portal.microfocus.com/s/article/KM000011916#SupportTips/KnowledgeDocs

Compile error with entry-point when using COBSQL where there are multiple lines of "using" parameters Full article: https://portal.microfocus.com/s/article/KM000011909#SupportTips/KnowledgeDocs

Having a central license server with client machines retrieving the license from it, can the License Manager have different versions in the server and the client machines? Full article: https://portal.microfocus.com/s/article/KM000011879#SupportTips/KnowledgeDocs

Questions about migrating Web Service Definitions into Visual COBOL Full article: https://portal.microfocus.com/s/article/KM000011973#SupportTips/KnowledgeDocs

How to set a CES Daemon trace for license troubleshooting Full article: https://portal.microfocus.com/s/article/KM000011965#SupportTips/KnowledgeDocs

Hello! I need help for load bitmap and DLL for acuserver. See my configuration: 1-Config CODE_PREFIX @192.168.0.222:F:\\IMP\\ACUSERVE\\PDV\\OBJ;@192.168.0.222:F:\\IMP\\ACUSERVE\\PDV\\OBJF;@192.168.0.222:F:\\IMP\\ACUSERVE\\PDV\\OBJC;. FILE_PREFIX @192.168.0.222:F:\\IMP\\ACUSERVE\\PDV\\DADOS;@192.168.0.222:F:\\IMP\\ACUSERVE\\PDV\\DADOSR;@192.168.0.222:F:\\IMP\\ACUSERVE\\PDV\\DADOSP |for load image and DLL  (not working) IMAGE_PREFIX @192.168.0.222:F:\\IMP\\ACUSERVE\\PDV\\IMGDLL_PREFIX @192.168.0.222:F:\\IMP\\ACUSERVE\\PDV\\DLL to solve I mapped the network, but is problematic! IMAGE_PREFIX I:\\ACUSERVE\\PDV\\IMG DLL_PREFIX I:\\ACUSERVE\\PDV\\DLL 2-Load image  ACCEPT WEXT-IMG-PREFIX FROM ENVIRONMENT "IMAGE_PREFIX". |CARREGAMENTO DA IMAGEM INITIALIZE WX100 STRING WEXT-IMG-PREFIX DELIMITED BY SPACES '\\LOGOEMP.JPG' DELIMITED BY SIZE INTO WX100 END-STRING CALL "W$BITMAP" USING WBITMAP-LOAD, WX100 GIVING LOGO-JPG END-CALL 3-load DLL ACCEPT WEXT-DLL-PREFIX FROM ENVIRONMENT

Hi everybody, I need to do a simple Http Get on this Url "">viacep.com.br/.../".Does anyone has an example of how to do that using native COBOL? If there is no way to do it using native, is there a way using modern(maneged) COBOL?#API#HTTP#get#COBOL#MicroFocus

We have the Micro Focus Visual COBOL(v6.0.0.138) application setup on Linux (RHEL 8) and the database is MS-SQL. The Cobol application communicates to an External application using a 'C' socket program. A Cobol module calls the ‘C’ socket program passing the required information (Server name, Port number) using a pointer. At the point of calling the ‘C’ program, the application fails with the message as below, Execution error : file 'system/bin/CallSocket.gnt' error code: 114, pc=0, call=1, seg=0 114     Attempt to access item beyond bounds of memory (Signal 11) Please find below the program logic which invokes the C program,  MOVE 1 TO WS-UNSTR-PTR. MOVE ZERO TO WS-UNSTR-CTR. MOVE ZERO TO WS-UNSTR-FLD-CTR MOVE SPACES TO WSOK-HST-NM. UNSTRING WS-SRV-NM DELIMITED BY SPACES

Hello, we are working with version 4.0 of CA and we want to update to version 8.0 of CA:1 - Is it possible to do it without installing the previous versions? 2 - Would it be necessary to completely uninstall the product and install it again with the correct version?

My solution involved existing PRO*COBOL modules compiled into Visual COBOL. and for this we are using 64 bit ODAC drivers provide by Oracle. Installation of the ODAC drivers have been successful, however when trying to consume the drivers using ADO.NET Connect Editor I endup with dependency on Microsoft .Net framework 3.5 or lower where as the ODAC provider is .Net 4.5 and above and I've selected Framework as 4.0 and above in ADO.Net and the CPU architecture as 64 bit. It would be great, if some one can point me in the right direction to install and use ODAC 64 bit drivers for my Visual COBOL 64 bit without any dependency on the 32 bit framework or 3.5 framework. Below are some images from my experience. Image 1. Image 2 Image 3

this is a COBOL performance issue related to PeopleSoft.  We are doing a system upgrade and having no change in COBOL program.  We are seeing our cobol process running much slower.  Available tracing shows us the issue is not SQL performance related.  We are upgrading from PT 8.56 to PT 8.59 and Oracle DB 12c Extreme Performance RAC to DB 21c Extreme Performance RAC. New and Old environments are all in OCI. Our issue is that existing COBOL program for GL Consolidation is running much slower on the PT 8.59 environment. We have worked with Oracle Support and provided AWR reports and can confirm the issue is not SQL or DB tuning related. In the COBOL trace we see that total time in application is greatly increased in our new environment compared to old. Process is running more than twice as long in new environment on equivalent linux process schedulers with same ocpu/memory etc. Any idea what influences the Total in Application time? Also - we have tried recompiling co

For web service deploys beyond Development, customer uses mfdepinst utility, which receives messages: 2007 (Mon Oct 31 09:06:15 CDT 2022): Unable to bind to directory: (81) SERVER_DOWN4020 (Mon Oct 31 09:06:15 CDT 2022): Unable to add service and package objects to directory9999 (Mon Oct 31 09:06:15 CDT 2022): Exiting. Installation not complete. Full article: https://portal.microfocus.com/s/article/KM000011815#SupportTips/KnowledgeDocs

Net Express's certification on Windows Full article: https://portal.microfocus.com/s/article/KM000011770#SupportTips/KnowledgeDocs

In this case the language was Hebrew and when moving text to an output file it was not being displayed at all. It was only producing an empty output file.This worked fine with Server Express Full article: https://portal.microfocus.com/s/article/KM000011746#SupportTips/KnowledgeDocs

How to determine the version of the product or compiler that was used to build a .gnt file? Full article: https://portal.microfocus.com/s/article/KM000011724#SupportTips/KnowledgeDocs

CodeBridge as a product was introduced to the RM/Cobol suite of products while there was only a 32-bit version of RM/Cobol. This meant that documentation only contained example command lines for compiling and linking within a 32-bit environment. As time progressed, a 64-bit version of RM/Cobol was released but the CodeBridge documentation was not updated to take account of changes required when compiling and linking a 64-bit application. Full article: https://portal.microfocus.com/s/article/KM000011814#SupportTips/KnowledgeDocs

It is possible to nest Cobol-IT programs together in the same source module.The -fstatic-call directive tell the compiler that all calls are considered static, ie all programs are in the same executable module.The -fnull-param directive tells the compiler to add a null parameter to end of a call statement.When the two directives were used together and the nested programs appeared in the source code error the following error was reported:Compile error:/tmp/cob12742_5.c: In function <source module>:/tmp/cob12742_5.c:179:5: error: too many arguments to function <called module>(*(int *) (b_10)) = routine (b_19, NULL, NULL);^/tmp/cob12742_5.c:35:5: note: declared hereint routine (unsigned char *);Where:<source module>: - name of the source module that is being compiled.<called module>: - name of a nest program that has been called. Full article: https://portal.microfocus.com/s/article/KM000011682#SupportTips/KnowledgeDocs

I would like to write a small Windows program for myself with a very short list of requirements (that I am aware of): I am not the least bit interested in OO It must access an embedded database like MS Access. It must be a Windows Form application with standard controls like edit, grid, button, etc. I've never seen Eclipse so Visual Studio is my preferred IDE. I assume I can achieve this with the Visual COBOL Person Edition, correct? I am confused by the choice of NATIVE vs MANAGED. Does it matter in my case? Considering my project, what are the merits of one over the other? If someone is aware of a tutorial or book that can take me through the process, I would greatly appreciate it. Thanks in advance.#VisualStudio#managed#VisualCOBOL#nativecobol

For the last two days I have been trying unsuccessfully to download Visual COBOL PE. The email address and password I had previously used fails with a mismatch error. So, I changed the password which produced the same results. So, I used a different email address and password, and it still fails. I've changed passwords on both accounts multiple times which produced the same results. Obviously, the original email/password combination is still able to get me into the Community to post this message. Is that portion of the site having difficulties or am I doing something wrong? Any suggestions? Thanks.#error#PersonalEdition#login

Hello, I am working on a trial version of Visual Cobol 8.0 since yesterday and I have a "homework" including PostGre database. I designed something very simple : a table "Individuals" whose columns are : first name, last name, birth date, creation timestamp, last update timestamp. I designed the table with pgAdmin 4. Does someone designed a visual cobol program accessing this kind of database ? If not, did someone create a program with Oracle database access ? My goal is to understand how precompilators work, how they replace SQL language by library calls (here, for Oracle or, better, PostGre). I used to work on Cobol batch programs with DB2 SQL, on Mainframe environment (z/OS), but the DB2 database, JCL, compilators, and so on, were already there. I didn't have to care about all this stuff because it was in the hand of database architects, mainframe architects, and so on. Thank you for your help, Didier