Rocket® ACUCOBOL®

Created On:  24 January 2012 Problem: COBOL application batch programs which is processing a high volume of detail records and after several hours they abort with a COBOL File error 34 on SORTWK1. Resolution: The runtime SORT temporary files were limited to 2GB of data each on UNIX ports.  Since all the data is eventually merged into one temporary file, this meant that the total amount of data that could be sorted was limited to less than 2GB.  An error 34 during the SORT was the usual indication that this limit had been reached. In version 7.1.1 it was a change that enables large file support on those UNIX systems which support it.    The USE_LARGE_FILE_API configuration variable controls this support, just as it does for relative and sequential files.On UNIX systems, this variable allows you to turn on or off file system API support for very large files (greater than 2 gigabytes). Support for large files is enabled when USE_LARGE_FILE_API is set t

Created On:  14 December 2011 Problem: After an upgrade to version 9.1.0 the application no longer displays the jpeg images.  There are blank spaces where the images should be displayed. Resolution: The image handler, ajpg32.dll, was inadvertantly left out of the 9.1.0 32-bit installation.  It should be in the 9.1.0 AcuGT\\bin directory.  That is fixed with the 9.1.1 installer.  In the meantime the workaround is to copy the ajpg32.dll from a previous installation.  Or you may download the one attached to this article. Attachments ajpg32.zip Old KB# 35324

Created On:  14 December 2011 Problem: The application is deployed with version 8.1.3.1 so there is a need to compile for that version but the -Z81 compile option is not available.  The -Z80 compile option is there but is not appropriate as there is a fix for an issue with the date entry control that requires compiling for 8.1 or later. Resolution: AcuBench 9.0 is missing the -Z81 compatibility option in the Project Settings, Compiler, Miscellaneous Options, “Program can be run by the version” list.  The resolution is to not select “Program can be run by the verion” item.  Instead, enter -Z81 in the “Additional Options” box on the Compiler tab.  The same is true of the Project Settings, Compiler, Compatibility Options, “Version compatibility mode”, -C81 option.  The resolution is the same, add -C81 in “Additional Options”. Old KB# 35326

Created On:  16 January 2012 Problem: Prior to version 9.0, using Acu4GL Oracle or Acu4GL DB2 on UNIX it was a needed procees to relink the database libraries to the runtime. This process sometimes generated some errors. Resolution: Now, relinking is no longer necessary. For UNIX shared builds, Acu4GL Oracle and Acu4GL DB2 are now shared libraries, so all that needs to be done is to setting the appropriate environment variable (i.e LD_LIBRARY_PATH). Old KB# 35383

Created On:  23 November 2011 Problem: The application runs for a period of time and then encounters a memory access violation on a START operation. The file involved has been used in the same run unit, including START operations, with no errors. Resolution: The application was configured with MAX_FILES setting greater than 255. The MAX_FILES limit was increased in version 6.2. Prior to version 6.2 the MAX_FILES limit was 255. In order to successfully use a MAX_FILES setting of 256 or greater all objects must be version 6.2 or later. Some of the objects within the application were pre-6.2. The resolution was to recompile all of the application's programs. Old KB# 35251

Created On:  29 November 2011 Problem: The Thin Client application makes use of a COM object which must be invoked entirely on the server to avoid having to also install it on the client PCs. The usual way of instantiating a COM object seems to require the object be present on the client PC.  For example: CREATE Application of Excel      SERVER-NAME is "MyServer"     HANDLE in xl-app. This requires that Excel be installed on the client PC.  If not the create statement fails.  How can this be accomplished so nothing needs to be present on the client PC? Resolution: Using the “Local:” prefix with the server name will cause the COM object to be wholly instantiated on the server with no requirement of anything being present on the client PC.  The CREATE statement from the example above becomes: CREATE Application of Excel      SERVER-NAME is "Local:MyServer"     H

Created On:  29 November 2011 Problem: Using ACUCOBOL-GT version 8.1.2.1 when pasting text into certain entry fields the Runtime crashes.  Before crashing it sometimes repeatedly gives the message “Too many lines”. Resolution: This is a known issue that was fixed in Version 9.0.0.  Upgrading to version 9.0.0 or newer will resolve the error. The underlying cause is when a single-line entry field has the MAX-LINES property set. MAX-LINES is intended for use only with multi-line entry fields and should not be used with single-line entry fields.  Removing the MAX-LINES property or setting MAX-LINES to 0 will also resolve the error. Old KB# 35284

Created On:  10 November 2011 Problem: AcuBench 9.1.0 returns the following error while trying to create a new project or generating the source code: Cannot find required library ccbldll.dll Resolution: The ccbldll.dll located inside the AcuBench directory is not working as expected and therefore is not recognized.Add the full path of the BIN directory (i.e. C:\\Program Files\\Micro Focus\\Acucbl910\\AcuGT\\bin) to the user's environment variable PATH.  If this variable contains paths related to old ACU or Micro Focus installations, remove them or put the 910 string at their left so that it may be read as first.This issue has been reported to Micro Focus developers team who will fix it in the future release. Incidents #2545029, #2545826 Old KB# 35198

Created On:  28 November 2011 Problem: The user has noticed an accumulation of hundreds of Runtime log files on the server in the working directory of their Thin Client application.  There are no errors noted in any of them, only several lines of what appears to be connection information. Why are the log files there?  Is it possible to prevent them from being created? Resolution: When the Runtime detects that it was invoked via Thin Client it automatically creates a trace file in the working directory.  Normally, setting “A_REMOVE_EMPTY_ERROR_FILE ON” in the Runtime configuration file causes those automatically generated trace files to be deleted.  This prevents the accumulation of zero byte files. However, in Version 8.1.2 there was a bug which caused handshake entries to be written to that trace file and they are not empty as they should be.  This is already fixed in version 8.1.3.1, and upgrading is the recommended solution.  Make sure to a

Created On:  18 November 2011 Problem: While attempting to access Vision data using AcuXDBC Server version 9.1.0 on Unix/Linux the error below was encountered with both 32- and 64-bit versions. The error occurred whether using AcuXDBC client on Windows or UNIX/Linux and also using utilities like asql.ERROR: DLLLOAD: xvision, /bin/xvision.so: undefined symbol: ShowLicenseError Resolution: The behavior is corrected by ECN-XD071 in version 9.1.1. Install the new version when it becomes available.  In the interim, a patched version of AcuXDBC Server version 9.1.0 may be available by contacting SupportLine. Incident #2545001 Old KB# 35252

Created On:  28 November 2011 Problem: Using AcuBench 9.0.1 there is an error reported when compiling: "Compiled screen description too large" Is there a compiler option to get around this error? What is the limit for a screen description? How can I tell how large a compiled screen description is? Resolution: There is no compiler option to allow a screen description to be larger than the limit, which is 32k.  To determine how large the screens are compile with a full listing and examine the Screen Section items to see how big the screens are.  That is add the “-Lfo @.lst” compile option then check the .lst file for the screen sizes.  Each 01 level screen item may not be larger than 32k. If it seems the limit is only exceeded by a small amount then there may be a workaround.  Remove some of the properties from some of the controls in the screen section until it compiles.  Then in the procedure division after the screen is displayed, m

Created On:  25 November 2011 Problem: In thie example, two AcuCOBOL prgrams are called A and B. When verified in Modernization Workbench, A and B get verified into programs A and B - correctly. In program B there is a CALL “A.COB”. Logically, the parser searches for an entry “A.COB”, which does not exist. By putting an entry “A.COB” into the procedure division of A, the unresolved reference report show the missing .COB program entries. Without changing the source code, so that CALL “A.COB” is changed to CALL “A”, how can this situation be corrected and the programs successfully verified for analysis? Resolution: Create an Alternative Entry Point for all COBOL programs. Make sure the "Create an Alternative Entry Point" option in Workspace Options > Verification > Cobol > Settings, is set. Enter the value “=(.*)=\\1.COB” (no quotes required) This will generate a second entry point for all COBOL programs that will have .COB appended. Re-verification will be su

Created On:  10 November 2011 Problem: Using runtime 9.0.1, the tool Alfred returns the following error trying to open a Vision file: "The file system does not support requested operation".Using runtime 8.1.0 Alfred works correctly. Resolution: The error is caused by a known issue that concerns I$IO library and runtime of version 9.0 and 9.0.1.  A fix has been developed and released in version 9.1.0.  Be sure to upgrade to the new version of runtime. Old KB# 35199#901#91#90#ECN-4101

Created On:  31 October 2011 Problem: XDBC Server 8.1.3 can be started, but the connection from the client is raising this error:Connection failed:SQLState: 28000[TOD] [ODBC Driver] DLLLOAD: acuxdbc04, This application has failed to start because the application configuration is not working properly. For troubleshooting, you should reinstall the application. Resolution: Some Visual Basic 2008 RT-Files got corrupted or deleted. Reinstalling those files solves the issue. Incident #2543749 Old KB# 35115#SQLState-28000#AcuXDBC

Created On:  21 October 2011 Problem: After the installation of runtime 9.1.0, no bitmap or jpeg image is displayed inside the application.  W$BITMAP returns an invalid handle. Resolution: This is caused by the lack of the correct library inside extend setup 9.1.0 for Windows 32-bit.  Either copy the missing library ajpg32.dll from an existent 9.0.1 installation, or extract the attached zip file into the newly installed 9.1.0 BIN directory. Incidents #2542782, #2542215 Attachments ajpg32-901-32bit.zip Old KB# 34988

Created On:  18 October 2011 Problem: I am having problems accessing SQL Server on a remote server on the network. Resolution: If you are running the AcuSQL interface to Microsoft SQL Server, you must have the SQL Server client software from Microsoft. To see if the SQL Server client software from Microsoft is on your system, Open the Query Analyzer. (For information on opening the Query Analyzer see SQL Server client documentation.) If the Query Analyzer opens and you are able to connect to the database, the client libraries are most likely all present. Your SQL Server data source may be hosted on one (or more) of the following environments: So now you should be able to access the server on the network....Ensure that you set - ACUSQL_RUNTIME_DLL to asqlsrvr.dll**  asqlsrvr.dll is the DLL specifically for connecting to MSSQL.** esqllib.dll is not supported for connecting to MSSQL.When using asqlsrvr.dll the CONNECT statement must specify the MSSQL Server, rather t

Created On:  19 October 2011 Problem: Is it possible on a system with dual monitors to determine and ensure which screen the output appears on? Resolution: Since the Runtime was never developed with dual monitors in mind, the output will always be displayed on the primary monitor. There isn't any other option. Since changing this would require enourmus efforts, an enhancement is not likely. Incident #2542225 Old KB# 34962#primary#output#dualmonitors#screen#runtime#ACU

Created On:  18 October 2011 Problem: In specifically the Linux environment, we encounter the following error transaction error 05, 02 when invoking a program that contains rollback functionality. Resolution: This is the breakdown of the error codes 05,02 you are receiving: 05 This indicates an operating system error that is not otherwise covered by one of the standard error conditions.  You can determine the exact nature of this error by examining the value of the secondary code.In Linux the secondary codes are held in errno.h (/usr/include/asm/errno.h). The code equates to - #define ENOENT 2 /* No such file or directory */You can find out more details by running a trace for example: - runcbl –c config.cfg –lxe error.log program Old KB# 34955#AcuCobolLinuxError

Created On:  21 October 2011 Problem: Are ACU runtime and other programs of the suite extend 9 compliant with Windows 2000?These are some of the problems encountered during an installation of 9.1.0 on a Windows 2000 Server:- InstallShield Wizardextend(R) Version 9.1.0 requires that the following requirements be installed on your computer prior to installing this application. Click Install to begin installing these requirements: MSXML 6.0 SP1- InstallShield 1210: Setup requires Windows Installer version 3.0 or higher to install the Microsoft .Net Framework version 2.0.- dotNetFx40_Full_x86_x64.exe is not a valid Win32 application.- acuthin.exe is not a valid Win32 application. Resolution: Windows 2000 is not supported with extend suite 9.x.The supported Microsoft Operating Systems for 9.x are:Windows XP, Windows Vista, Windows 7, Windows 2003, Windows 2007, Windows 2008 R2. Incident #2542799 Old KB# 34993

Created On:  19 October 2011 Problem: How do you change the text item of a tree view control? Resolution: In version 9.0.1 there is an enhancement that enables the user to change the text of a tree-view item. This feature is controlled by a new runtime configuration variable TV_EDITLABELS. When this variable is set to "1" (on, true, yes) you can change the value of the tree-view item by clicking it with the mouse (just like with Windows Explorer). When the variable is set to "0" (off, false, no) text changes are not allowed. The default value of TV_EDITLABELS is "0". To keep track of the changes, two additional messages are generated from the tree-view to the COBOL program: MSG_TV_BEGINEDITLABEL and MSG_TV_ENDEDITLABEL. MSG_TV_BEGINEDITLABEL is sent to the COBOL program when the user begins the edit. EVENT-DATA-1 is always 0, and EVENT-DATA-2 contains the handle of the item being modified. The program can prevent the modification by setting EVE

Created On:  17 October 2011 Problem: How do you find in Acu4GL for MSSQL the unique SQL spid (process id)? Resolution: You can view the SPID in MSSQL using Activity Monitor etc or try using the function below.ACUCOBOL-GT Appendices Version 9.0.1 Appendix I: Library Routines > I.1 General Syntax and Library List > C$GETPID This routine returns the Process ID (PID) of the current process. This PID can be compared with the PID returned by the C$LOCKPID to determine if the current process is the one holding a file lock or record locked condition. Usage CALL "C$GETPID" GIVING PROCESS-ID. Parameters PROCESS-ID PIC 9(n) This contains a numeric data item large enough to hold a PID. On most platforms, PIC 9(5) is sufficient. On 64-bit systems, PIC 9(7) is recommended. Comments When called from a non-UNIX or non-Windows runtime, C$GETPID returns a PROCESS-ID of "0". This behavior should not be used for system identification. Use ACCEPT ... FROM SYSTEM-INFO

Created On:  25 October 2011 Problem: Since the release of extend version 8.0, Micro Focus released a 64-bit Windows native port for the extend product suite. The new installer for this port can lead to some misunderstandings about installation paths. Resolution: Usually, all Windows 64-bit programs are installed under "C:\\Program Files\\" while 32-bit programs are installed under "C:\\Program Files (x86)\\".Launching a 64-bit setup installer provides an option to select a different path where Acu product will be installed. A "Path" field can be filled to provide the new directory path.The path you provide will be the location for 32-bit libraries only. All 64-bit libraries will be placed under "C:\\Program Files", regardless of the drive and path chosen in the Path field.For example, if you choose to install Acu products on drive D:\\, you can enter this location in the Path field:D:\\Program Files (x86)\\Acucorp\\Acucbl811 This wil

Created On:  21 October 2011 Problem: The users would like the date entry control to initially display blank but even when the "SHOW-NONE" style is applied the control displays the current date.  What is required to make the date entry control display a blank date? Resolution: Assigning the show-none style only affects the value that the control RETURNS when inquired on. If the check box is unchecked then inquiring the value will return zero for a date and all 9s for a time.  The control still must display a valid date.  Show-none does not affect the value displayed. The date entry control is actually an implementation of Microsoft's calendar control which must always display a valid date.  It cannot display a blank date as blanks are not a valid date.  When the date entry control detects a value that is not a valid date then it displays the current date.  This behavior cannot be changed.Note that most GUI applications have this b

Created On:  10 January 2012 Problem: It appears that the Acu XDBC 64bit server can be selected when doing a Windows install, but the modules do not get copied onto the machine. Resolution: AcuXDBC does get installed on the machine, but gets installed into the default location of "C:\\Program Files\\Micro Focus\\Acucbl910\\AcuGT\\bin\\". If you want the files in another location there are five steps you need to perform to be able to use 64-bit AcuXDBC from the new location. The steps require that you have administrator rights to the local machine. 1. Copy the files from "C:\\Program Files\\Micro Focus\\Acucbl910\\AcuGT\\bin\\" to .2. Set GENESIS_HOME= .3. Change the properties of XDBC Query 64-bit shortcut so the target now points to .4. Run regedit and locate the HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBCINST.INI\\extend9 AcuXDBC (64-bit) entry. The Driver and Setup keys need to be changed to the following: Driver=\\bin\\acuxdbc.dllSetup=\\bin\\AcuXDBCSet

Created On:  21 October 2011 Problem: The program uses a line sequential file with fixed length records.  However, when writing records to the file the trailing spaces are removed.  For this application the trailing spaces are necessary and should not be removed.  Why are the trailing spaces removed? Resolution: Print files always have trailing spaces removed.  Somewhere in the program there is a WRITE statement that includes the ADVANCING phrase.  Even though this file is not specifically defined as a print file, the ADVANCING phrase causes it to be handled as a print file.  Removing the ADVANCING phrase from all write statements for this file will resolve the issue. Old KB# 34999