Rocket® ACUCOBOL®

Created On:  31 January 2013 Problem: AcuRuntime 9.1.2.1 is the first release certified for Windows 8.  A CALL "C$SYSTEM" is executed always in asyncronous mode when run on this platform. Resolution: A possible workaround is to add the flag CSYS-SHELL to the CALL "C$SYSTEM".In future release 9.2.0, this behavior will be fixed in ECN-4210.This is the description of the fix:SUBJECT: On Windows 8, C$SYSTEM fails to wait for a console-mode programChange Number:  ECN-4210Status:         CompleteType of Change: CorrectionPriority:       MediumIncidents:      2608782RPI Number: 1087447 Date:        2013-01-28Product:     ACUCOBOL-GTModule:      runtimeNew Version: 9.2.0 Machines Affected: Windows 8Known Versions Affected: All DESCRIPTION of problem or enhancement: When running on Windows 8

Created On:  31 January 2013 Problem: How to setup AcuRuntime to work with Oracle pro*cobol pre-processor on a linux platform? Is a relink of the runtime necessary?Any possible attempt to relink AcuRuntime 9.1 returns errors such as:"direct.c:158: error: redefinition of 'LIBDIRECT'direct.c:109: error: previous definition of 'LIBDIRECT' was here"Any attempt to launch AcuRuntime without relink returns an error such as:"program missing or inaccessible" Resolution: To have the AcuRuntime operating with pro*cobol, there's no need to relink the runtime. Two solutions are available: 1.set LD_LIBARY_PATH in the environment to the LIB directory path of the Oracle installation i.e.: /opt/oracle/OracleBase/product/11gR1/client/libThen preload the library using the -y runtime switch.i.e.: runcbl -y libclntsh.so.11.1 -c .... prog 2.add the following variables in the /ect/cblconfi file:SHARED_LIBRARY_PREFIX  /opt/oracle/OracleBase/product/11gR1/client/libSHARED_L

Created On:  31 January 2013 Problem: AcuRuntime 9.1.2.1 may have introduced a bug in the way Paged Grid behaves.Here is an example of the behavior:A Paged Grid control shows a list of records: 01, 02, 03, 04 in the first page05, 06, 07, 08 in the second pageIn the first page, click on the Previous Record button.Then click on the Next Page button:records will be displayed as:04, 05, 09, 13The expected sequence should be:05, 06, 07, 08. Resolution: The bug has been corrected in next release 9.2 by ECN-4208:SUBJECT: Incorrect EVENT-DATA-2 for some PAGE-NEXT-PAGE eventsChange Number:  ECN-4208Status:         CompleteType of Change: CorrectionPriority:       HighIncidents:      2609120RPI Number: 1087460 Date:        2013-01-22Product:     ACUCOBOL-GTModule:      runtime, acuthinNew Version:

Created On:  20 December 2012 Problem: Working and debugging an application in Thin Client mode, the remote clients usually are remapped on the server to an unique local user-name. This causes different developers/testers to work in debug using an unique .adb file. Since developers may create their own breakpoints, the .adb file is constantly rewritten. Sometimes the file may become corrupted, breakpoints lost or the multiple accesses at the same time may cause remote debuggers to hang. Is it possible to isolate this file so that each user has its own file? Resolution: In order to have different debug files for different working users, you need to make sure you have different values of USER-ID for each local user-name. The best way to do that is to log in as different users, not have everyone use the same username. This means that you must have in the AcuAccess file and these variables in you acurcl.cfg file: SECURITY_METHOD   LOGONWINNT_LOGON_DOMAIN &nbs

Created On:  14 January 2013 Problem: The application sends terminal escape sequences to control terminal behavior. When running in standard mode it works correctly. In debug mode the escape codes are not interpreted but look like they are simply displayed on the screen. This occurred after upgrading from version 7.0 to 9.1. Resolution: In version 8.0.0 the handling of terminal escape sequences was modified to fix an issue where they interfered with the debugger window in some cases. A new configuration variable, ANSI_OUTPUT_IN_DEBUG, was also added to provide the old behavior. To resolve this issue set ‘ANSI_OUTPUT_IN_DEBUG’ to ‘TERMINAL’ either in the environment or in the Runtime configuration file. It may not be set programmatically as it must be applied before the terminal is initialized. n/a Old KB# 36734

Created On:  20 December 2012 Problem: Acubench 9.1 returns "license file not found". Which are the correct licenses to use? Resolution: Acubench 9.1 used to have an issue with the license file. As a matter of fact, extend 9.1.0 and 9.1.1 contains AcuBench 9.0.1. You must expand the AcuBench license code and key with a 9.0.1 activator. For these releases, there is a 9.0.1 activator included in the AcuBench directory. The related acubench.alc file must contain:#  Product........: AcuBench#  Version........: 9.0.0 and usually is located inside this directory:%allusersprofile%\\Micro Focus\\extend\\9.0.1\\x86 This issue is now fixed in 9.1.2.1. So, this release and later need a 9.1.2.1 license which must contain:#  Product........: AcuBench#  Version........: 9.1.0 This acubench license file is located in this Windows directory:%allusersprofile%\\Micro Focus\\extend\\9.1.2\\x86 Incidents #2605858, 2602885 Attachments acubench-license-not-

Created On:  04 December 2012 Problem: The error message produced is: "Acubench Integrated Development Environment has stopped working". Sometimes, when compiling a COBOL program, AcuBench would crash. This was due to a correction made in 9.1.2 that removed memory leaks. Resolution: This issue has been resolved by ECN-WB915: SUBJECT: AcuBench crash on build Change Number: ECN-WB915 Status: Complete Type of Change: Correction Priority: High Incidents: 2597131 RPI Number: 1086395 Date: 2012-11-13 Product: AcuBench Module: ccbldll.dll New Version: 9.2.0 Machines Affected: Windows only Known Versions Affected: 9.1.2 and later DESCRIPTION of problem or enhancement: Sometimes, when compiling a COBOL program, AcuBench would crash. This was due to a correction made in 9.1.2 that removed memory leaks.Please either request or raise an incident with the Micro Focus Supportline and request this patch for V9.1.2. The next AcuCobol version release is extend V9.2.0 which  is cu

Created On:  03 December 2012 Problem: When trying to install an AcuCobol product on Linux the error message appears - libc.so.6.1: version `GLIBC_2.3.4' not found. Resolution: To install an AcuCobol product on a Linux machine the minimum Operating System requirement is GLIBC_2.3.4.  The customer should be advised to upgrade the Linux platform to at least this level. Old KB# 36653#COBOL

Created On:  10 December 2012 Problem: Program that uses an ActiveX control works Ok with Windows runtime version 9.1.2.1 when it runs standalone; but with thin client it crashes, the program works Ok with previous Thin Client versions. Resolution: The problem is due to the ECN-4159 introduced in version 9.1.2.1, while development still is investigating this problem, the solution is to turn off the runtime configuration variable ECN-4159, like this:   ECN-4159 OFF Incident #2603362 Old KB# 36669

Created On:  12 December 2012 Problem: When a .Net control is local on the same computer where the Runtime is executing there is no error.  But when the .Net control is on another computer and accessed remotely via either UNC notation or a mapped drive the version 9.1.1 Runtime crashes with a memory access violation.  With 8.1.x runtime there is no crash - everything works as expected. Resolution: Version 9.1.1 implemented the .Net 4.0 framework, which has different security than previous versions of the .net framework. In particular, it won't default load an assembly on a remote machine (and in some cases, won't even load one that came from a remote machine, but is now local). Previous .Net versions did not have such a security restriction which is why earlier Runtime versions do not have a problem. To allow loading of remote assemblies requires the creation of a .Net configuration filenamed wrun32.exe.config in the same directory as wrun32.exe,

Created On:  10 December 2012 Problem: When compiling a COBOL program, AcuBench 9.1.2.1 crashes. Resolution: This is due to a correction made in 9.1.2 that removed memory leaks. There is a new ECN-WB915 that will be included in version 9.2.0, but there is already a patch available for AcuBench 9.1.2.1, which is patch 1357, that could be requested to SupportLine. Incident #2603766 Old KB# 36670

Created On:  12 December 2012 Problem: Having Internet Explorer 8 installed, the Web Browser control returns a value related to IE 7. This may cause some issue to customer's application which will run a test on the browser installed on end-users' machines. Resolution: This problem is caused by some changes that MS introduced during the IE 8 Beta1. The following link explains the problem and the solution. http://blogs.msdn.com/b/ie/archive/2009/03/10/more-ie8-extensibility-improvements.aspx In short, you need to add a registry key naming the executable (wrun32.exe or acuthin.exe, or if you have renamed the runtime, whatever name you gave it). Incident #2599414 Old KB# 36675

Created On:  04 December 2012 Problem: Is it possible through AcuCobol to change the fonts or enlarge the pop-up menu? Resolution: This is not possible from COBOL. You would need to choose the size of menus by using the Windows Control Panel. And there is only minimal control there. Old KB# 36660#COBOL

Created On:  25 October 2012 Problem: This article explains how to display the value of a configuration variable from within the ACUCOBOL-GT debugger. Resolution: To display the value of a variable set in the environment or in the cblconfi, the name of the variable must be preceded by a %. For instance, to inquire the value of CODE_PREFIX, this is the command line to use: d %CODE_PREFIX Incident #2281877 Old KB# 36506#COBOL#archive

Created On:  25 September 2012 Problem: Customers started already working with Windows 8 and MS SQL Server 2012, which are not officaly supported by our version 9.1.1. Resolution: Our just released version 9.1.2 officially supports Windows 8, SPARC running Solaris 11 and Microsoft SQL Server 2012. N/A Old KB# 36376

Created On:  25 September 2012 Problem: A Vision version 4 file is about 5 GB total size with 37 million records.  It has two keys and there is a need to specify an existing field as another key.  A COBOL program was created to read the existing file and write to the new file.  That program executed very slowly.  It had not finished after running for over a day.  The file is used for a batch process that must run every day so a faster method is needed. Resolution: The vutil -unload and -load options will produce much faster results in moving the data from the old file to the new file.  First, unload the data into a binary sequential file using:      vutil -unload -b originalfile tempfile Next create the new empty file with an OPEN OUTPUT from a COBOL program.  Next, after you have an empty file with the new definition load the data with:      vutil -load -b temptfile newfile Lastly rename the

Created On:  25 September 2012 Problem: The original source file for the program has been lost.  Can the source code be extracted from the compiled object? Resolution: If the object was compiled for source level debugging then yes, Micro Focus engineers can extract the source.  To check the progam, execute it in debug (wrun32 -d programname or runcbl -d programname depending on platform).  If you can see the lines of the source then decompiling is possible. Your Account Manager can provide information on the cost and availability for such services. n/a Old KB# 36374#decompileundebug

Created On:  21 September 2012 Problem: Read-only Entry Fields used to allow their foreground or background colors to be modified. ACUCOBOL-GT Runtime version 8.1.0 stops this behavior and leaves the read-only field gray. Resolution: This change was made to follow Windows standards and was implemented with ECN-3699 released in 8.1.0. Since ACUCOBOL-GT 9.0, this implementation can be turned off so that applications may be customized as usual. Set the following configuration variable in cblconfi file: ECN-3699 0 The value "0" turns the ECN off, value "1" activates the ECN and entry-fields remain gray. Incident #2131301 Old KB# 36363#910#colours#colors#9.1#COBOL#Color#customizing#customize#colour#archive

Created On:  07 September 2012 Problem: How to improve the performance of an AcuConnect Thin Client application. Resolution: In general two are the most important factors in performance terms when executing Thin Client applications, the application and the network latency, rather than bandwidth, latency is almost always the cause for poor thin client display performance, increasing the bandwidth does not necessarily reduce latency. In fact, when a client sends a request to acurcl, it just makes the connection via a socket, once a client is connected to the child runtime, acurcl is never again utilized for that client except during the runtime shutdown, in this case, during the execution of the application, all the performance depends on the speed of the network. The above points to the fact that the memory requirements are those for the runtime, which are minimum. A thin client program is less affected by the network latency if it has fewer calls that require a response. Re

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: 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:  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:  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:  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:  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,