Browse all forums dedicated to the Rocket® COBOL product family.
Recently active
What is the maximum number of "OR" conditions that can be used in mfsort when run from the command line? Full article: https://portal.microfocus.com/s/article/KM000015467#SupportTips/KnowledgeDocs
On a high resolution system I retrieve for example the scaling factor of the display and it is returned as 100% even through it has been set to a different value. Full article: https://portal.microfocus.com/s/article/KM000015461#SupportTips/KnowledgeDocs
How do you display a tab-control on top of another tab-control ?
PROBLEM The Visual COBOL / Enterprise Developer install can fail, at the Microsoft Build Tools and SDK download/install stage, with error '0x8007000a - The environment is incorrect'.When checking the install logs, it shows that 'cblms.exe' fails with error 0x8007000a. SOLUTION After the failed installation, 'cblms.exe' can be used to check if the MS Build Tools and SDK are found by the MF product - https://bit.ly/2NwBqZY Check the output from the commands 'cblms -Q' and 'cblms -L' If the MS Tools are installed and found, then it will show something like this: cblms -Q Windows SDK location = c:\\Program Files (x86)\\Windows Kits\\10 version = 10.0.18362.0 Microsoft Build Tools location = c:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Enterprise version = 14.27.29110 cblms -L Windows SDK Id Version Location 0] 10.0.14393.0 c:\\Program Files (x86)\\Windows Kits\\10 1] 10.0.15063.0 c:\\Program Files (x86)\\Windows Kits\\10 2] 10.0.16299.0 c:\\Program Files (x
I am getting this error in a program that opens an indexed file in open mode of I/O. Copies of this program is called by several processes at the same time - meaning the same program runs in parallel with each other. Each program reads this file and skips any records it should not process. This happens at a client site, and running this results in a 99 error code intermittently. I don't see documentation of what a 99 i/O error is - but think it may be record locking. We do have code that handled this by looking at a return code of a 9D (locked record condition) and when the program got that, it looped back to do the same read that eventually will get it from another process no longer locking it. We tested this at our shop where program 1 would read the first record in the file and artificially 'pause' while the other 2 thru 12 programs would read that same record and get 9D's. However, if I know what a 99 I/O was, it would
Situation Is there a way to identify "who" is locking a record/file in Visual COBOL?In ACUCOBOL there is "C$LOCKPID" to do just thatIn RM/COBOL there is "C$OSLockInfo" to do the same. Resolution Use the command: wholockwholockUsage: wholock [options] file_pathOptions:-v -V Enable verbose mode-l -L Prints out list of processes that are using the file-R[m] Semaphore file before checking for locks- m = S use strict file locking (default)- m = N no strict file locking-h -H Prints out this help messagefile_path: Path to file read article#SupportTips/KnowledgeDocs
Encountering an error when executing the Visual Cobol installation (vcvs2022_80.exe). I have successfully installed Visual Studio 2022. The log reflects the error shown below: i301: Applying execute package: cblms_x86, action: Repair, path: C:\\ProgramData\\Package Cache\\331E737A96B5A92CF15EA8922FCA6D11D806FBB6\\cblms.exe, arguments: '"C:\\ProgramData\\Package Cache\\331E737A96B5A92CF15EA8922FCA6D11D806FBB6\\cblms.exe" -U'e000: Error 0x8007000a: Process returned error: 0xae000: Error 0x8007000a: Failed to execute EXE package.e000: Error 0x8007000a: Failed to configure per-machine EXE package.i319: Applied execute package: cblms_x86, result: 0x8007000a, restart: Nonee000: Error 0x8007000a: Failed to execute EXE package.i372: Session end, registration key: SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\{cecf3000-8979-4b05-b35a-ef938e63e49e}, resume: ARP, restart: None, disable resume: Noi371: Updating session, registration key: SOFTWARE\\Microsoft\\Wind
Hi, After upgrading yesterday on my Win10, to VS2019 Pro version, 16.11.25, when I try to access any of my solutions that I already had, it tells me that they are incompatible. How do I solve this problem and recover the solutions and projects, I have repaired the VCVS 2019, and it is still the same....
Problem: I would like to compile a Cobol source file with Oracle procob . The following message is always displayed : << Pro*COBOL: Release 10.2.0.1.0 - Production on Tue Jun 24 15:21:19 2008 Copyright (c) 1982, 2005, Oracle. All rights reserved. PCB-F-NOERRFILE, unable to open message file, facility PCB >> $PATH & $LIBPATH are validated Resolution: This message can be displayed when environment variable ORACLE_HOME is not validated Old KB# 2365
Hi, for some time we have a problem that happens randomly. Some of our programs remove all files in the execution directory. We has check all de call system that has a "rm " loking for a worng parameter in the call , but all the call are correct. My question is: is there a way in which CBL_DELETE_FILE function could delete all the files in a dirtectory
I am experimenting with switching our existing ANT based build for Visual COBOL to the new support for maven. in our ANT based build we use the mfjarprogmap utility. Does anyone know how to get the maven build to include a calll to this utility ?
Performance reading xml files slower with Visual COBOL than Server Express Read full knowledge article for resolution#SupportTips/KnowledgeDocs
When starting multiple threads in a .NET COBOL program using System.Threading.Tasks.Task::Run, if COBOL file I-O statements are run within the task, run-time errors regarding null reference exceptions can occur. Read knowledge article for resolution#SupportTips/KnowledgeDocs
When using imtkmake (Micro Focus Interface Mapping Toolkit v6.0.00) to build a Cobol proxy calling a REST API, it results in error: MccHttpRequest: Method GET does not permit a request body Read the knowledge doc for resolution#SupportTips/KnowledgeDocs
Although a reference to a native DLL COBOL project is added to the calling managed program's project, a dynamic call to any of the programs from the referenced DLL project fails with the error 173. Read full knowledge article for resolution#SupportTips/KnowledgeDocs
Situation When I launch the Eclipse debugger, this sometimes kicks off a rebuild of my project. Why does this happen? Is there a way to avoid this build? Cause By default Eclipse looks for changes in files inside the project since the last build was performed, and if it detects any, will force a build as part of launching the debugger. This helps ensure that the debugging experience is correct, because without it there is the risk of looking at updated source that does not match what happens during execution. Resolution If you wish to suppress this automatic build, there is a setting in Eclipse preferences for this. From the Eclipse menu, go to "Window -> Preferences" then "Run/Debug -> Launching". The setting is "Build (if required) before launching", and if this is unchecked, the automatic build will not occur. Read full knowledge article#SupportTips/KnowledgeDocs
Situation Compiling a large program in version 8.0 produces the following error: COBCH1674S Internal dictionary overflow. Program too large. Same program compiles correctly in previous version. Resolution This has been identified as a product issue, which will be addressed by defect OCTCR50A413202. To check the status of this defect, please contact Customer Support. Read knowledge article#SupportTips/KnowledgeDocs
When running the same SORT in versions v6.0 Patch Update 21 and v8.0 Patch Update 3, the results are different.The sort contains : export SORTTYPE=2 mfsort \\ sort fields "(50,2,pd,a)" \\ use DS_SYNCSORT_COBOL_K000_OUT org sq record f,100 \\ give DS_SYNCSORT_COBOL_K311_OUT.$A2_COBVER org sq record f,100 The results appear to be in a different order in v8.0 Patch Update 3 Resolution This has been identified as a product issue which will be addressed by defect OCRCT50A415194.To check for the status of this defect, contact Customer Support. Read full knowledge article#SupportTips/KnowledgeDocs
The process of upgrading Visual Studio 2022 to a new version like 17.4.5, removes the Visual COBOL extension from within Visual Studio 2022 and COBOL is no longer recognized as a language. Read full article for resolution#SupportTips/KnowledgeDocs
Where can I find guidance on using NATIONAL characters (not DBCS) in COBOL programs? Full article: https://portal.microfocus.com/s/article/KM000014767#SupportTips/KnowledgeDocs
Launcing the "start-gateway" script to start the AcuToWeb gateway daemon, the following error occurs: ERROR 10000:Duplicate keys! using start-gateway script Full article: https://portal.microfocus.com/s/article/KM000014925#SupportTips/KnowledgeDocs
Calling a .NET DLL may cause a memory access violation (MAV) with 32-bit runtime or a runtime crash without notification with 64-bit runtime. The behavior did not occur with earlier versions of the runtime. Full article: https://portal.microfocus.com/s/article/KM000014905#SupportTips/KnowledgeDocs
I have any programs that run correctly on netexpress 5.1! Now i am testing the new version visual cobol 8.0 and have now programs that want works. Own lbr's or dll's are not found by debugging or running see a little example here: Where must be placed the own lbr's or dll'?Wich runtime modules are needed? There are any modules that i was not able to find on vc8 as tools.lbr or utils.lbr, also cblvios.dll, cblrtss.dll and other I missed also many possibilities on debugging on vc8 comparing with netx5.1!!!! How can help? What are your experience? Thanks for your help Here a extract from a program: working-storage section. * Pointer 01 cgtoolsptr procedure-pointer. 01 cob32apiptr procedure-pointer. * PROCEDURE DIVISION. main. perform load-module *> wapiutil is in ossyslib.lbr and not found !!!!!!!!!!!!!!!!! call 'wapiutil' using null *> vorladen / load-module section. *> own lbr-modul not found in vc80 !!!!!!!! call 'ossyslib.lbr
Hello Community, I am currently using Acucobol version 9.2.5 in my organisation. Can anyone let me know if there are any security issues in the version 9.2.5 due to which i should consider upgrading AcuCobol version 9.2.5 to the latest ? Also, if anyone knows about any security issues in acuthin do let me know. Thanks !#AcuCobol
DISPLAY ... ERASE LINE in terminals wider than 200 characters would cause a memory error. Full article: https://portal.microfocus.com/s/article/KM000014725#SupportTips/KnowledgeDocs
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.