Rocket® ACUCOBOL®

Created On:  09 August 2012 Problem: Is SQL Server 2012 supported in AcuCobol? Resolution: SQL Server 2012 will be supported/certified in AcuCobol Extend V9.1.2 due for release in September 2012. Old KB# 36203#Acu4GL#AcuSQL#SQLServer2012

Created On:  26 July 2012 Problem: Which is the exact syntax to use as a connection string with AcuODBC or AcuXDBC? Resolution: With AcuODBC, the connection string to use is:"Dsn=acuodbc_demo;Uid=yourusername;Pwd=yourPassword" With AcuXDBC Client, the syntax is:"acuxdbc04:system/manager/xvision:acuxdbc.cfg" where system is the default user of AcuXDBC syscat and manager is its default password. With AcuXDBC Client, connected to AcuXDBC Server:"acuxdbc03:system/manager/xvision:acuxdbc.cfg@20222:servername!acuxdbc04"where 20222 is the default port of AcuXDBC Server service. With AcuXDBC, using JDBC libraries:"jdbc:vortex:system//manager/testjava:acuxdbc.cfg!acuxdbc04" Incident #2584530 Old KB# 36155

Created On:  26 July 2012 Problem: Entering the command "acurcl -info" gives Socker Error: 10035. Resolution: While /etc/hosts had the server name defined correctly /etc/sysconfig/network did not. This must have changed a few days ago when we installed a new piece of software on the server which messed up the server name in /etc/sysconfig/network. As soon as I corrected this the socket error stopped appearing. Incident #2575420 Old KB# 36152#acurclsocket10035

Created On:  23 August 2012 Problem: When an ACUCOBOL-GT runtime terminates, all dynamically allocated memory is released. There are two situations where this is not true: CALL PROGRAM "program" using and CHAIN "program" using ....... Both terminate the current runtime but do NOT release dynamically allocated memory. This has been found to cause various problems including "Illegal Operation" errors and other unexpected results. For this reason, if you are using CALL PROGRAM or CHAIN, be sure to DESTROY all bitmaps, fonts (except those accepted from "standard object") and menus which have been created by that run unit. The exception here is any of these whose handles you may be passing in the USING section which you want to use in the called program. A second area which can cause problems is the situation where a subroutine is called several times, and each time it allocates memory by one or more of the above means. If prior to the EXIT PROGRAM you have not DESTROYED these i

Created On:  25 July 2012 Problem: The calculation is coded as follows: COMPUTE BEN-ER-PER-COMMUTED ROUNDED = (BEN-ER-CASH-LSUM-COMMUTED / COMM-FACT) / BEN-ER-FULL-ANNUAL * 100 The values loaded into COMM-FACT and BEN-ER-FULL-ANNUAL are zero. If the value inserted into BEN-ER-CASH-LSUM-COMMUTED is 63, the result is 300.00 It would seem as though where a value is loaded into the last integer digit the result is returned with a value other than zero. Resolution: In normal circumstances you cannot divide by zero and the SIZE ERROR option should be used. However, AcuCobol has the following configuration file setting A_CHECKDIV. This variable allows you to specify an alternate runtime response to a divide by zero condition when the statement does not include a SIZE ERROR clause. In COBOL, a division by zero produces a size error condition. The SIZE ERROR clause allows the programmer to specify actions to take when this condition occurs. If there is no SIZE ERROR clause,

Created On:  20 July 2012 Problem: What is supported when you have AcuXDBC Client and Server differences of 64 bit and 32 bit? Resolution: The rule is that all client/server products which use sockets for communication do not care about 32bit and 64bit mixing of client and server. For instance, you can use a 32bit SQL Server client with a 64bit SQL Server, ditto for Oracle. You can use a 32bit runtime to talk to a 64bit AcuServer. Old KB# 36127#COBOL

Created On:  25 July 2012 Problem: Compiling with the native compiler option --intel caused an immediate runtime MAV. Why is this? Resolution: After investigation by our development team it appears the problem on Windows when running programs compiled with –n or --intel is caused by Windows machines that have Data Execution Protection (DEP) enabled for all processes. Please set the following runtime configuration variable: - USE_EXECUTABLE_MEMORY TRUE When set to "TRUE", this variable enables a COBOL program compiled for Native Code (-n compiler option) to run on a Windows machine that has Data Execution Protection (DEP) enabled for all processes. The default value is "FALSE". Incident #2552337 Old KB# 36149

Created On:  20 July 2012 Problem: Customer had 130 licences with only 90 currently being used. They got intermittent connection refused error messages and it looks as if it's directly related to the number of users connected. Resolution: In this case the Acurcl service was started using the System account and it was only allowing 100 iterations of wrun32.exe to be launched. By changing the Acurcl service to use a local user account instead of the system account, the 100 limit did not apply. Incident #2549090 Old KB# 36128#COBOL#UsersConnected

Created On:  12 June 2012 Problem: When in AcuBench’s Screen Designer, a screen has an entry field named, as a sample, SCREEN-EF-FIELD1 that is defined in the properties to be displayed at line 5 and position 20. If by chance the control was setup with a line variable called SCREEN-EF-FIELD1-LINE but this variable is not referenced in the source program the generate sets this line variable to some other value than '5' as expected so the field ends up displaying at a different line number. Resolution: Delete the line variable from the control properties in the Screen Designer so that the control displays in the correct location. Users don't want to define line or column variables in the control properties if they don't plan to use them in the program. Incident #2573925 Old KB# 36010

Created On:  09 July 2012 Problem: Issuing an AcuBench command line to rebuild a workspace does not work.  There are no errors reported but there is no log file created and nothing happens to the project files.  They are not modified in any way. The command line is: c:\\Program Files\\Micro Focus\\Acucbl8xx\\acubench\\acubench90.exe /build C:\\My Projects\\project1\\project1.pjt Resolution: The problem is that AcuBench cannot handle spaces in the project path.  The resolution is to remove the spaces in the path; rename “My Projects” folder to “MyProjects”.  Or you can map a drive to the spacey part of the path and use that mapped drive in the AcuBench command.  In the above example we can map Z: to C:\\My Projects, and then we use Z:\\project1\\project1.pjt in the AcuBench command line. N/A Old KB# 36068

Created On:  09 July 2012 Problem: The AcuBench manual contains no documentation on the command line option to generate only.  Where is this? Resolution: The command line option to generate only was added in AcuBench version 9.0.0, however the manual has not been updated. Beginning in version 9.0.0 the syntax for generating a workspace using the command-line interface is as follows: [acupath]\\acubench90.exe /generate [projectdir]\\[workspace.pjt] For example, if you have AcuBench installed in the default directory, and you would like to generate a workspace called "Project1", use the following command: c:\\Program Files\\Micro Focus\\Acucbl9xx\\acubench\\acubench90.exe /generate C:\\path to project\\project1.pjt (on 64-bit Windows it is "Program Files (x86)") AcuBench regenerates the code but does not build the programs. This is the same behavior that you get when you execute a Regenerate Workspace command from the AcuBench Build menu. To Regen

Created On:  12 June 2012 Problem: [ISQL]ERROR: Could not SQLConnect, when using unixODBC on a Linux 64bit server with AcuXDBC. Resolution: To connect acuXDBC with unixODBC on a 64bit machine, you need to install unixODBC version 2.2.12 or later, at this point the version available in www.unixodbc.org is 2.3.1, install this version. Set the following variable in your environment to compile the isql executable as 64bit object: setenv CFLAGS -m64 or export CFLAGS=-m64 depending upon your shell Follow the instructions in the AcuXDBC User's Guide; Chapter 5:Installing AcuXDBC > 5.2 Installing AcuXDBC/AcuXDBC Server > 5.2.2 UNIX/Linux Installations, but you need to execute the following commands “asroot”, this is because a regular user doesn’t have permissions over the /usr/local/etc directory and the unixODBC process accesses this directory: Type "configure" and wait while features on your system are being checked. Type "make" and wait for the pack

Created On:  26 June 2012 Problem: Does Micro Focus certify ACUCOBOL-GT Extend for use with Windows Small Business Server 2011? http://en.wikipedia.org/wiki/Windows_Small_Business_Server Resolution: Micro Focus doesn’t support officially Windows Small Business Server (of any version).Some issues have been solved in the past changing the security settings on the SBS platform itself, to match the Standard or Enterprise editions of Windows. In case of more relevant issues, Micro Focus asks users to reproduce the problem to a standard Windows Server version.If the issue is reproducible on a standard installation, it may be furthermore analized by the MF Technical Staff. If the issue is NOT reproducible on a standard installation, it can be referenced to the limitations within Windows SBS itself and Micro Focus cannot do anything to work around this situation. The only possible solution is to upgrade user's server to a standard Windows edition. Incident #2580195 Old KB# 36

Created On:  24 April 2012 Problem: Using AcuConnect Thin Client 9.1.0 or 9.1.1 and your focus is on a cell of a grid and you press a hot-key to call another program, when the called program is closed you could get a MAV (memory access violation). Resolution: This is a bug which now is been fixed with ECN-4163. The correction will be available in next release 9.1.2. Incident #2566228 Old KB# 35868

Created On:  23 April 2012 Problem: Is there a web service available if you wish to interface with your COBOL for extend application? Resolution: In order to access a published web service, your COBOL program will need to be able to execute HTTP requests, and, manage XML documents.  To address these two requirements, Micro Focus provides RMNet and XML Extensions for extend. The RMNet subprogram library ships for free with extend v9.0.0 .  RMNet is an HTTP client for the extend Runtime, and, it allows your COBOL program to make HTTP requests.  The XML Extensions subprogram library, also, ships for free with extend v9.0.0 .  This product will allow you to create XML SOAP requests and import XML SOAP responses. Attached to this Knowledge Base Article is a zip archive, RMNetTutorial.zip, that contains a tutorial that describes how to use RMNet and XML Extensions to consume a web service. Attachments RMNetTutorial.zip Old KB

Created On:  24 April 2012 Problem: A Java program calls a cobol program using CVM.jar.  It gets this java exception:Initializing logging.CVM:  begin loadCVM: runtime library successfully loaded.CVM:  exception caught in constructorCVM:  Exception caught loading CVM:  nullCVM:  end load Exception caught loading CVM:  null java.lang.NullPointerException      at com.acucorp.acucobolgt.CVM.getCommandLineArray() (Unknown Source)      at com.acucorp.acucobolgt.CVM.initialize() (Unknown Source)      at test.main(java.lang.String[]) (Unknown Source) Resolution: Check to make sure the environment is setup correctly, taking care about existing values for previous installations. For example, this command line was used to setup environment variables: export CLASSPATH=$CLASSPATH:/usr/acucobol/tools/CVM.jar:. export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/acucobol/lib export PAT

Created On:  24 April 2012 Problem: The default behavior on a screen form is to type data in the form using lower-case and upper-case text at the same time. In some cases, it is necessary to force the use of upper-case (or lower-case) only. Resolution: Adding the UPPER (or LOWER) property to the definition of a screen control is one method of accomplishing this. However, this requires the program to be recompiled. An alternative solution that does not require compiling is to configure some environment variables. For character screens, use this environment variable: KEYBOARD case=lowerorKEYBOARD case=upper For graphical screens, the KEYSTROKE environment variable allows you to remap lower-case to upper-case, or vice versa. For example:KEYSTROKE data=65 97    <- this will transform the edited 'a' in 'A'KEYSTROKE data=66 98    <- this will transform the edited 'b' in 'B'KEYSTROKE data=67 99    &

Created On:  03 April 2012 Problem: I am using MS SQL Server 2005 and Database Connectors (within MicroFocus' Studio Enterprise Edition 6.0). After creating a solution in Visual Studio 2008, I attempted to connect the Visual Studio solution (DBC.sln) to the SQL database tables through the debugging steps. I received a "File Error: 9T" in the debugging window. How do I resolve this issue? Resolution: For Studio 6.0 SP2 (and later), a 9.0 license for Connector for MSSQL is needed. It needs to live in %ALLUSERSPROFILE%[\\Application Data]\\Micro Focus\\ConnectorForMSSQL 9, and be named acufh.mlc. The “\\Application Data” part is included in the directory name if the version of Windows is less than 600. Another way to look at this is that the acufh.mlc either needs to be in \\ProgramData\\Micro Focus\\ConnectorForMSSQL 9, or in \\Documents and Settings\\Application Data\\Micro Focus\\ConnectorForMSSQL 9, depending on which pathway exists.To obtain the license, a S

Created On:  13 April 2012 Problem: Reading a large table with Acu4GL in a SQL Server Data Base accessing the records by alternate key, the performance decreases dramatically compared with a VISION file. Resolution: It is a fact that accessing a data base table instead a VISION file, the performance decreases due to VISION files are the native file system handled by Extend runtime with no translations at all. This performance hit increases if the program is accessing the tables using alternate keys; data bases don’t have and don’t know the alternate key’s concept. In Cobol, the two most expensive statements, in terms of performance, are OPEN and START; accessing a VISON file this  impact is not noticeable but it is when we are working with a data base. Using the above COBOL statements extensively in the same program or in the same runtime unit will decrease the performance of the runtime. Said that, there are some guidelines described in Chapter 9 Performance and Trou

Created On:  13 April 2012 Problem: While trying to execute a program sitting in a Windows server from a client machine through AcuServer, the execution fails showing in the  AcuServer trace file the following error messages: Cannot search (READ/EXECUTE) all parent directories Cannot create files in the directory Error like no such file? errno: 2 Even the user is part of the "Local Admin Group, and the "admin Group" was already on all the locations, also the user added the "Local Account " directly into the security of all the folder that is needed access to and gave him "Full Control". Resolution: This is a frequent problem that checking permissions in a Windows server, users circumvent the permissions of the root directory. Even the user is a local admin with full access to the files and directories, the problem in those cases is that the user who has being mapped in the AcuAccess file is not able to access the files at the top leve

Created On:  23 March 2012 Problem: AcuConnect fails to start its service. The error popup shows this message on an English Operating System:"AcuConnect - StartService: %1 is not a valid application of Win32."And this on an Italian Operating System:"AcuConnect - StartService: %1 non è un'applicazione di Win32 valida." Resolution: Verify the value of the Registry Key:HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\services\\AcuConnectIt may be useful to modify the value of the key "ImagePath" from: C:\\Program Files\\Micro Focus\\Acucbl901\\AcuGT\\bin\\acurcl.exe -startserviceto"C:\\Program Files\\Micro Focus\\Acucbl901\\AcuGT\\bin\\acurcl.exe" -startserviceDouble quotes may be useful to avoid any issue with paths which contain spaces. Incident #2543888 Attachments 35683-error.jpg Old KB# 35683

Created On:  28 March 2012 Problem: Is there a way for one program (Program A) to open files, accept input from a screen, then call a second program (Program B) for file processing without Program A closing the files and Program B reopening files? Resolution: Declaring the file FD as external in both programs accomplish the desired task: FD custom-file external. 01 custom-record ....etc This way the file can be opened and closed in ProgramA and read, write, etc. in ProgramB. ProgramB can not open again the file because it will generate an error. Incident #2191524 Old KB# 35719

Created On:  28 March 2012 Problem: I'm trying to get an F4-key exception from a Combo Box control it seems that doesn’t work. Any other F1-F9 keys generate an exception, but an F4-key won’t. Is this a limitation? Or what needs to be done to make this happen? Resolution: There is a configuration variable called WIN_F4_DROPS_COMBOBOX This configuration variable applies only to programs running under Windows. Its default value is "1" (on, true, yes), so, combo boxes use the standard Windows handling for the key. Pressing while a combo box is active causes it to drop its drop-down list, and the COBOL program is not notified of an exception. When this variable is set to "0" (off, false, no), pressing with a combo box active causes the COBOL program to get the exception, but the combo box does not drop its drop-down list. Incident #2191737 Old KB# 35720

Created On:  28 March 2012 Problem: Installing just Acuserver 64bit trying to execute the Control Panel it fails with the message “The program can’t start because acme2.dll is missing from your computer”. Resolution: The problem is that the acme2.dll for 64bit is downloaded just when the runtime is installed. The solution is either to install the runtime or copy that dll from the installation media at: DISK1\\Program Files 64\\Micro Focus\\Acucbl910\\AcuGT\\bin. Incident #2561691 Old KB# 35718

Created On:  08 March 2012 Problem: Alfred is no longer in the AcuBench Tools menu. How do you get Alfred back in the Tools menu like in previous versions? Resolution: In AcuBench go to the Tools menu, Customize, Tools tab.  Click the plus sign, , then name it Alfred and enter the following: Command: C:\\Program Files (x86)\\Micro Focus\\Acucbl910\\AcuGT\\bin\\wrun32.exe Arguments: -c ..\\tools\\alfred.cfg ..\\tools\\alfred.acu Working Directory: C:\\Program Files (x86)\\Micro Focus\\Acucbl910\\AcuGT\\bin\\ Then click Close. Alfred can now be started from Tools, Launch Tools. Incident #2561976 Old KB# 35627