Rocket® COBOL

We are having problem executing a programa compiled with Visual Cobol 2.2 and preprocessed with ProCobol. We are not using neither Eclipse nor .NET environment development. We have found in this ORACLE  URL: https://community.oracle.com/thread/466190?start=0&tstart=0 that the solution is use  the compiler flags "-C IBMCOMP". We tested this, but do not work. The problem occurs when trying to connect to the database. We are blocked and We don't know what can we do. Can anybody help us?

Procobol gives the next error: Pro*COBOL: Release 11.2.0.3.0 - Production on Tue Oct 7 16:59:46 2014 Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved. Open file: /MNG/DESA/VFUENTES/ATS/TST1F830.sksError at line 0, column 1 in file /MNG/DESA/VFUENTES/ATS/TST1F830.sksPCB-S-00400, Encountered the symbol "<end-of-source>" when expecting one of the following:    . , END-EXEC NOWAIT_ ORDER WAIT FOR @The symbol "END-EXEC" was substituted for "<end-of-source>" to continue. On line 0 (zero. The input file was produced by CP preprocessor. This is the only error produced by Procobol precompiler. Any idea? 

Problem: From Oracle's SQL*Plus prompt the following is entered to run a procedure: SQL> EXECUTE MYPROCEDURE('my data'); PL/SQL procedure successfully completed. The procedure simply updates a table with the new data, and it runs without error. When the COBOL program passes the same statement to the SQL.ACU program an error occurs about being invalid. This is the relevant portion of the runtime trace file:  Try loading 'SQL.ACU'... SQL.ACU loaded ora_execute: ORACLE EXECUTE : execute MYPROCEDURE('my data'); ERROR CODE = [900] ORA-00900: invalid SQL statement   Resolution: To execute an Oracle Procedure, the SQL command passed to SQL.ACU must use the BEGIN… END; syntax rather than EXECUTE: BEGIN MYPROCEDURE('my data'); END; Note that only procedures that do not return any data may be executed by calling SQL.ACU.

We just upgraded to netexpress 5.110.0022 and now it appears I can no longer debug my dialog.  Use to be when it was called I could substitute DSGRUN with DS and it debug the dialogs behind the screens. Now (and I tried several screens), I get "Execution of the program DSOO had been interrupted.  This program is not animatable, but you can view the call/perform stac..  The cause of the interupt was:114.  Attempt to access item beyond bounds of memory (Signal 11). I hope this is something I need to change somewhere and not a problem with the new version.#DSGRUN#dialog#DS#114

Current we are facing one issue. As per client requirement we have to create a file having record length 102729. But as per Microfocus Guide line Run Time Limits of File Size should not me more than 64K. Is there any alternate method to access the files having more than 64K of length. Please advice.#eclipsevisualcobolvariablesviewencoding#eclipseMFcobolcontenttypewithoutextension#Eclipse#rebuild#COBOLFILE#RMCOBOLfiles#visualcobolruntimeswitchlinking#VisualCOBOLautoscalemodescreenresolution#COBOL#buffer#COBOLOrion

Problem: Rather than using the SQL Server lock table the application uses the Vision lock file which is specified in the configuration variable A_MSSQL_VISION_LOCKS_FILE.  When the program runs it crashes on the first attempt to open a SQL Server table.  This is seen in the trace file:  opening data segment (#0): Lock4GL.dat   Alt lockfile [Lock4GL.dat] error 1 Resolution: The configuration variable A_MSSQL_VISION_LOCKS_FILE must be set to include the complete path and file name.  In this case the path was omitted and it specified only the file name.  Adding the path to the file name will resolve the error.

My English is very poor, but I try. I tried version 9.2.3 and have problems with headers grids, if the column is numeric, the title appears only if it is a number. Is there any "ecn" to fix this?, How do I get? Thank you very much.

Problem: When the user opens an elevated Net Express command prompt by right-clicking on 'Net Express 32-Bit Command Prompt' and clicking on 'Run as administrator', the command prompt session is created with the following error: 'createnv.bat' is not recognized as an internal or external command,operable program or batch file. The createnv.bat file is the script to set up the Net Express environment variables, and in this case, the script could not be executed. Resolution: Behind the Net Express 32-Bit Command Prompt shortcut, it is actually launching:C:\\Windows\\SysWOW64\\cmd.exe /k createnv.bat In this same shortcut, you will notice that the Start in field is to specify the current directory as "C:\\Program Files (x86)\\Micro Focus\\Net Express 5.1\\Base\\Bin\\" In other words, the createnv.bat is executed from "C:\\Program Files (x86)\\Micro Focus\\Net Express 5.1\\Base\\Bin\\" When running this shortcut as administrator, Windows fo

PROBLEM In the AcuLocks table, the column Lockpid contains the SQL Server Process ID or SPID which is lockinga record. How can the owner of the Lock be determined ? RESOLUTION If SQL Server 2012 is running, then open the SQL Server Management Studio. On the left hand side in the 'Object Explorer' right click on 'Activity Monitor'. This displays all the current processes running on the server. Other methods:-   Open 'New Query' and type 'sp_who2', This gives the same display as the 'Activity Monitor'. Each process shows the 'SPID' with information including the Login and Host Name. Match the LockPid to the process running that has the matching SPID. Execute the stored procedure 'sp_who'. This gives the spid, username and hostname of every connection. Reference the spid associated with the lock. For more information, execute this statement: select * from sysprocesses where spid = nn This wil

I have Visual COBOL Personal Edition with Visual Studio 2012, running on Windows/8 I have set up a Project with several programs in it When I Build the Project it tries to compile each source member within the Project And it comes up against the 2200 Procedure Division line limit fairly easily If I have, say, 10 programs in a Project and I change one program, how can I just compile/prepare that one program Is it possible?

PROBLEM When installing AcuCobol, this error message occurs : "This installation package is not supported by this processor type." RESOLUTION AcuCobol 64 Bit cannot be installed onto a Windows platform with a System Type of 32 Bit.   Windows 32 bit                 Acu 32 bit    correct Windows 32 bit                 Acu 64 bit    wrong Windows 64 bit                 Acu 32 bit    correct Windows 64 bit                 Acu 64 bit    correct

Problem AcuXDBC error message - 'Vortex (simple) SQL Interface has stopped working' This occurred when running 'asql' for example with the following statement: - select * from table; Resolution The problem appeared after AcuXDBC V9.1.1 and was resolved in AcuXDBC v9.2.1. This was related to our AcuXDBC Trifox 3rd Party product. Please upgrade to our latest AcuCobol/AcuXDBC version.

Problem AcuCobol is not available for the Mac OS X operating system Resolution Micro Focus does not support AcuCobol on the Mac OS X operating system For a Mac which is setup to dual boot into Windows, then we expect AcuCobol to run normally. For a Mac which is setup to run Windows in a virtualized environment  (i.e. Parallels or VMWare Fusion) then we expect AcuCobol to run normally, however Micro Focus currently does not offer support for any errors in such an environment.

PROBLEMS The AcuCobol source program appears to compile but there is no runtime object program created RESOLUTION The problem in this case was that the compiler license (ccbl32.alc) had the 'Restricted Compiler' license set on. Creating a new compiler license with the 'Restricted Compiler' setting 'set off' resolves the issue

Hi, when I try to start debugging with Visual Cobol Personal Edition (VS2012) I get "Unable to start debugging" (critical error). Someone else got the same error? Some idea before trying to reinstalling the product?. Claudio      #debugging

We are having problem to compiling Visual Cobol 2.2 with SQL embedded (Oracle). We are not using neither Eclipse nor .NET environment development. We are compiling using a script, setting de compiler directives into the program using $SET USE statement. According with the documentation we separate de directives into two files. Within the program the SET statements appear so:       $SET USE"/MNG/DESA/VCFG/VCDirecSQL.dir"      $SET USE"/MNG/DESA/VCFG/VCDirectivesP1.dir" : first file includes: p(cobsql)  csqlt=oracle8 nomakesyn  end-c comp5=no sqlcheck=full mode=oracle dbms=V8 varchar=yes unsafe_null=yes close_on_commit=no end_of_fetch=1043 dynamic=oracle type_code=ansi USERID=CBL_OWNER/cobol2014@LBDCOB01 endp second file with the rest of the compiler directives. When we try to compile, we receive the next message:     2$SET USE"/MNG/DESA/VFUENTES/ATS/TST1F(·=.CBL*  53-S********

I have been using Net Express 4.0 for many years and it is an excellent product I want to be able to do the same with the new Personal Edition of Visual COBOL that I have on Win/8 I am at the stage where I can dbl-click a .cbl source code member and Vis CBL starts up and I can edit But I cannot see how to compile and then to run In Net Express 4.0 the red check mark compiles the current source code and creates a .int member if the compile is clean The I can set to run that program through 'Activate/Settings' and then click the running man in black and the program runs These are steps I cannot find how to do with Visual Cobol P/Edit Can someone please give me a starter on this Once I can run a simple batch style program under VC P/Edit I can then delve into the manuals and get it to talk to the screen, etc    

HI, I have many question to post because I returned to Cobol years later. The most important question regards the database pre-compiler. In particular: 1) With EXEC SQL Can I set isolation level and begin transaction ? 2) How Can I test if an insert or updated does not succeed because of constraints violations? 3) If I set autocommit disabled in SQl properties can I use commit and rollback ? 4) To set a null value it is sufficient move -1 to :name-fileld-null  ? Claudio  #EXECSQL

Problem: Installing Net Express 5.1 Update (or WrapPack) fails with the following error: Error 1305. Error reading from file C:\\Windows\\Installer\\xxxxx.msi. Verify that the file exists and that you can access it. Resolution: This problem occurs when the SYSTEM account does not have a full permission on the folder that the installation was launched from. By default, the SYSTEM account is granted full control to all files on local NTFS volumes. If Net Express 5.1 Update file is located on a network drive, you might want to copy it to your local drive, such as in C:\\Users\\YourID\\Downloads or C:\\Users\\YourID\\Documents where the SYSTEM account has full control.

Hello. I`m using Acucobol-Gt Thin client 80, and it`s saying: "conection failed"-"Connection to server refused"When I try to log on from some of my clientpc`s. The odd thing is that 1. W7 ok. 1 XP, ok. 1 w8.1 ok. 1 W7 refused. 1 w8.1 refused.The only differense is the brand of Pc. HP seems to be the best.I have a HP server running W server 2012R2. Is this a known issue? Regards Guffen#ThinClient

Problem: When obtaining the AcuShare report the meanings of the various items is not clear. Here's an example of such a report:  Server Statistics: ================== server PID: 19134 IPC key: 0x01010101 shmid: 40370176 listening port: 44659 start date: Tue Apr 19 03:04:34 2014 clients: 2 client deaths: 0   message type        sent       received --------------   ----------   ---------- HANDSHAKE                 8            8 ACK                       2            0 INFO                    &nbs

Problem: By default, the COBOL Text Window comes with the system menu that allows to minimize, restore down, and close the application window. Clicking on these buttons does not unfortunately trigger an event for the application to act upon, so it abruptly terminates the COBOL application without giving any chance to stop graciously. This often results to data file corruptions and other unexpected results. The proposed solution in the past (see CloseButton.zip at the Examples and Utilities page) was to remove the system menu by using a Windows API functions GetWindowLong and SetWindowLong, and this does avoid the users to click on the Close button. What if you simply want to disable the Close button and keep the minimize and restore down buttons enabled? Resolution: There are actually other Windows API functions that can be used to disable the Close button from the system menu, and the following codes show how to use GetSystemMenu and EnableMenuItem:       &nbsp

Problem: A DB2 application runs fine on a machine that has Net Express 5.1 and DB2 client installed, but it fails with the following error when it is executed on a machine that has Server 5.1 and DB2 client installed: Load error : file 'sqlgstrt' error code: 173, pc=0, call=1, seg=0 173 Called program file not found in drive/directory Resolution: This problem usually occurs when the DB2 runtime files are not found in the PATH. However, the Server 5.1's installation inserts quotes around the location of the COBOL runtime files (i.e. "C:\\Program Files (x86)\\Micro Focus\\Server 5.1\\Bin") causing a problem with the search through PATH and/or COBDIR. The purpose behind the quoted path was for backward compatibility with older versions of Windows. Until an Update (formerly known as WrapPack) is released to remove these quotes, the workaround is to update PATH and COBDIR manually in the Micro Focus registry entries by following the steps below: Open t

High Everbody, How can I trap the Windows Shutdown with NE5.1?

We use the browser component in lots of places in our system but there are times that certain websites throw errors.  Below is a sample of an error that is thrown up to the user.  Does anyone have any clue on how we can stop errors like this from being thrown up to our users?