Rocket® ACUCOBOL®

Created On:  12 January 2012 Problem: On 32-bit Windows systems, the default ODBC registry location that contains AcuXDBC information is HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBC.INI (System Data Source Name Definition), HKEY_CURRENT_USER\\Software\\ODBC\\ODBC.INI  (User Data Source Name Definition) and HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBCINST.INI (Driver Definition). For 64-bit Windows systems, the default ODBC registry locations are also HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBC.INI and HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBCINST.INI, which are used by the 64-bit ODBC drivers for defining the System Data Source Name (DSN) and driver. For 32-bit ODBC drivers, there is a secondary ODBC registry location, HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\ODBC\\ODBC.INI and HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\ODBC\\ODBCINST.INI which holds the 32-bit system DSN and driver definition.The confusion can come with User DSN’s as both the 32-bit and 64-bit ODBC administra

A file opened for I-O gets a 48,01 error when trying to WRITE. Problem: An indexed file is opened for I-O. The application can READ and REWRITE a record, but gets 48,01 when trying to WRITE a new record. 48,01 means that a file that is defined to be access mode sequential is open for I-O, or the file is open for INPUT only. Resolution: The problem is in the File Control paragraph FILE-CONTROL ACCESS MODE. In AcuBench, it defaults to “none”, which means sequential. The error message indicates that the runtime is trying to write to a file opened I-O, access sequential, which is not legal. Set ACCESS MODE to DYNAMIC and the problem is resolved. Incident Number: 2264513 Old KB# 14657

This article describes how to modify AcuXDBC batch files to automate the process of removing public ownership of tables when populating the system catalog. Problem: Demo.bat and other supplies batch files automatically make the owner of the tables in the system catalog “public," yet many front-end applications require the owner to be blank. Which of the batch files need to be modified to make this correction, and what modification is necessary? Resolution: Add -o “” in the addfile.bat batch file to the xdbcutil commands:@echo offremrem Copyright (c) 2001-2006 Acucorp, inc.remrem======================================================================rem = addfile.batrem =rem = Usage: rem = addfile [-d catalog_directory] [-x xfd_directory] [-u user] filenamerem = addfile [-d catalog_directory] [-x xfd_directory] [-u user] -f listfilerem = -d specifies optional directory name to use for therem = System Catalogrem = -x specifies optional directory

This article describes an issue in accessing documentation from AcuBench help menu even though extend product documentation has been installed. Problem: After installing AcuBench the help menu item shows the appropriate documentation options, but nothing happens when they are chosen, even though the documentation has been installed on the machine – as can been seen by successfully accessing the documentation via the Windows Start menu. Resolution: This is typically caused by the helpfile.ini file pointing to a location other than where the documentation exists or the helpfile.ini not being present. When this occurs the options in the helpfile.ini need to be modified to point to the correct location for each of the help item options. For example: [MainHelp]AcuBench=C:\\Program Files\\Acucorp\\Acucbl810\\Docs\\acubench\\index.htmACUCOBOL-GT Manual Set=C:\\Program Files\\Acucorp\\Acucbl810\\Docs\\index.htmACUCOBOL-GT Runtime Manual=C:\\Program Fil

This article explains how to avoid having ENTRY-FIELD controls drawn incorrectly in a screen section. Problem: Starting with version 7.2.2 it is possible for ENTRY-FIELDS to be incorrectly displayed without an upper boarder. This behavior is caused by the combination of three events: The upgrade to runtime 7.2.2 from a previous version. A vertical size (LINES property) of the ENTRY-FIELD that is very thin (for example, less than 0,75 pixel or less than 1,10 cells). The ENTRY-FIELD is right justified using RIGHT property or using JUSTIFY_NUM_FIELDS environment variable set to TRUE. Resolution: There are several solutions to avoiding this behavior. One solution is to modify the code by resizing all the involved ENTRY-FIELDs. The amount of work that would be required in some cases may make this a non-viable solution. Another approach depends on whether or not the code can be recompiled. If recompiling is an option then use the -C71 com

The F4-key does not generate an exception with a Combo Box control. Problem: Pressing <F4> while a combo box is active causes it to drop its drop-down list, and the COBOL program is not notified of an exception. Resolution: If the runtime configuration variable WIN_F4_DROPS_COMBOBOX is set to its default value of "1" (on, true, yes), then combo boxes use the standard Windows handling for the <F4> key. When this variable is set to "0" (off, false, no), pressing <F4> with a combo box active causes the COBOL program to get the exception, but the combo box does not drop its drop-down list. It is not possible to get both behaviors at the same time. Incident Number: 2191737 Old KB# 14526

Setting the 'NO-TAB' property on a graphical control can be done using 'MODIFY' and this works properly. However, it is not clear if there is a way to reverse the 'NO-TAB' setting without exiting the screen. Problem: A screen has several entry fields and some fields need to be skipped based on information contained in other fields. The 'NO-TAB' property can be set on the desired fields using 'MODIFY' and this works properly. It is not clear if there is a way to reverse the 'NO-TAB' setting without exiting the screen. There is not an 'ON/OFF' or 'TRUE/FALSE' setting for the 'NO-TAB' property. Resolution: The only way to remove the NO-TAB style from a control is to destroy the control and redisplay it without specifying the NO-TAB style. The same is true for the SECURE style available on an entry-field. A different option is to avoid the NO-TAB style and used the ENABLED property f

This article explains the method for running a COBOL program in the background of Windows. Problem: How do you run a COBOL program in the background when using Windows? Resolution: To run a COBOL program in the background use the –b runtime flag which inhibits the terminal initialization done by wrun32. This can be useful if the program is run in the background because terminal initialization can prevent normal use of the terminal by the operating system. If this flag is used, the behavior of ACCEPT and DISPLAY statements is undefined; therefore use this flag with caution. A program can examine the ACU-NO-TERMINAL field after an ACCEPT FROM TERMINAL-INFO statement to determine whether it was started with "-b". Incident Number: 2350874 Old KB# 14586

This article explains how to configure the date-entry control to display dates prior to 1930. Problem: The date-entry control is set to the SHORT-DATE format. When the user enters a date prior to 1930 the year changes. For example the user enters 1929 and the control displays 2029. Resolution: When using the date-entry control’s SHORT-DATE format for displaying the date, the CENTURY-DATE style must also be applied. Old KB# 14543

This article explains how to activate the Database Connector component in Server Enterprise Edition 6.0 Problem: Having installed the runtime product Server Enterprise Edition 6.0 it will be necessary to activate the various components of the product using the various license keys and authorization codes supplied with the product. Database Connector is activated via two codes: a 16 digit Product Code and a 12 digit Product Key. How is this done? Resolution: In order to activate this component go to the Bin directory of the Server Enterprise Edition installation and identify the file activator. Double click on this file and you will be prompted to populate two fields; one for the Product Code and one for the Product Key. Old KB# 14593

This article explains what to do if the call to the C$SLEEP library routine is ignored when running in the debugger. Problem: When executing a program in the Runtime debugger the program’s call to C$SLEEP is ignored and the program immediately proceeds to the next statement. Resolution: The program in this case is multithreaded and the debugger was not set to run all threads. The resolution is to toggle the debugger to Run all Threads mode. This is done by entering “ra” at the debugger prompt or selecting the corresponding item from the Run menu. Old KB# 14542

The ACUCOBOL-GT runtime can manage different character sets other than the common Western European. Problem: Is it possible to use different character sets other than Western European in a COBOL graphical environment? Resolution: Yes, the ACUCOBOL-GT runtime enables you to change the locale of an application at runtime. When changing the character set, it is possible to accept and write into a Vision file characters that belong to different languages, such as Russian (Cyrillic), Greek, Turkish, Arabic and Hebrew. The attached program shows how to do this. Incident Number: 2351489 Attachments http://community.microfocus.com/cfs-file.ashx/__key/communityserver-wikis-components-files/00-00-00-01-22/0755.International.zip  Old KB# 14588

Attempting to add a record to a Postgres database table using AcuSQL encounters errors. Problem: Attempting to add a record to a Postgres database table using AcuSQL encounters errors: SQLCODE = -1, SQLSTATE = 42000, SQLERRMC = Attempt to execute nonexistent, unprepared or invalid statement SQLIST. Resolution: With the more recent ODBC drivers for UNIX and Linux the ReadOnly entry in the odbc.ini file needs to be set to NO. Once this is done any of the operations that modify data in the table (INSERT, UPDATE, DELETE) will work without error. Incident Number: 2220456 Old KB# 14527

This article explains how to generate XML header information when running in CGI mode. Problem: A COBOL program that runs in background mode must write to SYSOUT so that it will be shown in a web browser. The problem however is that the output must be in XML format instead of HTML. The error indicates that the content type needs to be XML. How can this be done this using AcuCOBOL? This is what has been suggested for php: header ("Content-type:text/xml") But this is not something that can be done in the XML file itself, but must be set as part of the header. How can this be accomplished with the AcuCOBOL-GT Runtime? Resolution: Set this variable in the runtime configuration file or environment: CGI_CONTENT_TYPE=text/xml. This will direct the runtime to provide the specified value for the Content-type header that the runtime automatically generates. The runtime can also be prevented from supplying _any_ HTTP headers automatically. To do this, s

This article explains how to resolve error 93 when accessing a file. Problem: When opening a file an error 93 is encountered saying: File locked by another user Resolution: There are three main causes of this error: Ungraceful exits. If the runtime exits in a manner that doesn't send a message to release the lock, the operating system will hold the lock until rebooted. On Windows Servers you can use the Administrative Tools > Computer Management > Shared Folders > Open Files to try to release locks on shared files. On UNIX/Linux copy the locked file to a different location, rename or delete the locked file and move the copied file back. For example: cp myfile ../myfile rm myfile mv ../myfile myfile Permissions problem. If the user has read-only permissions and the file is opened i-o this can cause the error 93. Other software having the file locked such as anti-virus or backup software. Inciden

This article describes a possible computational error when using fractional exponents and describes a potential work around. Problem: Upgrading to version 7.x uncovered a computational error that occurs when executing iterative mathematical statements that involve exponentiation with fractional powers, such as square root. For example, executing the following statement in a loop 50 times could cause the resultant value of MY-CALC-INT-A to equal 1 instead of the correct value of 3. COMPUTE MY-CALC-INT-A ROUNDED = 9 ** 0.5 Resolution: Upgrade to version 8.x or higher. A potential work around is available, but requires code modifications to the existing COBOL program source. To utilize this work around, an ON SIZE ERROR phrase may be added to the COMPUTE statement. For example: COMPUTE MY-CALC-INT-A ROUNDED = 9 ** 0.5 ON SIZE ERROR … Incident Number: 2264802 Old KB# 14459

This article provides information about the implementation date for the configuration variable A4GL-WHERE-CONSTRAINT. Problem: Although the Micro Focus Database Connectors User’s Guide documents the availability of the A4GL-WHERE-CONSTRAINT, it has not yet been fully implemented. Resolution: Currently, the full implementation of the A4GL-WHERE-CONSTRAINT is scheduled for version 5.1 WebSync 4 (WS4). Incident Number: 2285746 Old KB# 14493

This article describes how to use the WHEN directive to address this issue. Problem: A FILE SECTION field that is redefined by another field that is specified as a key, or part of a key, is not being added as a column in database tables. As an example, in the following FD the t_cod_tra and t_cgc_tra fields do not get created as table columns: fd trans_fil. 01 reg_tra. 05 t_cod-tra pic 9(03). 05 xt_cod_tra redefines t_cod_tra pic x(03). 05 t_nom_tra pic x(40). 05 t_end_tra pic x(40). 05 t_bai_tra pic x(25). 05 t_cep_tra pic 9(08). 05 t_mun_tra pic x(25). 05 t_uf_tra pic x(02). 05 t_tel_tra pic x(11). 05 t_col_tra pic x(11). 05 t_con_tra pic x(20). 05 t_mai_tra pic x(50). 05 t_cgc_tra

This article explains what to do if OEM font special characters don't display correctly in Microsoft Access or Excel. Problem: When reading from a file in which data was written using OEM font information (usually from an old DOS character-based system), special characters like $ and £ do not display correctly in Microsoft Access and Excel. The special characters display correctly, however, when using the AcuXDBC utilities asql or odbcsql. Previously, AcuODBC had an option that allowed the character set to be chosen (ANSI or OEM); this option is not available in AcuXDBC. Resolution: AcuXDBC does not have the character map functionality that AcuODBC had. The resolution to this issue is to convert the OEM font data to ANSI font data, which will display correctly in Windows-based business intelligence tools. Old KB# 14512

This article explains what to do if AcuXDBC sends you the error message “Too many columns NNN (max: 256)." Problem: When trying to access a VISION file through AcuXDBC that has more than 256 fields (columns) — the default maximum number of columns allowed — a user receives a “Too many columns NNN (max: 256)” error message. Resolution: The user can change the default of 256 columns in the “Advanced” tag of the data source name (DSN). The Maximum Columns field on this tag can be set to up to 8191. Incident Number: 2284263 Old KB# 14471

This article explains how to use the C$SOCKET routine to connect to a Network Time Protocol (NTP) server and obtain a Universal Time. Problem: Sometimes it is useful to know the Universal Time so that the exact time and date can be provided to an application (for example to check license expirations). Resolution: The Universal Time is available from the internet thanks to NTP servers. The attached program shows how to use the C$SOCKET library routine to get information from one of these servers. Incident Number: 2284151 Old KB# 14461

This article describes how to use AcuXDBC to connect a string from an ASP project. Problem: Using AcuXDBC to connect a string from an ASP project sometimes generates the following error message: "Microsoft OLE DB Provider for ODBC Drivers error '80004005'[TOD][ODBC Driver]VISION: 'GENESIS_HOME' environment variable not found." Resolution: The key points to success in this process are the following: The installer sets the GENESIS_HOME variable in the USER environment, not the SYSTEM; you need to manually set GENESIS_HOME as a SYSTEM variable (copy it from the USER variable). Create a System DSN, using the AcuXDBC driver; name it “MY_DSN," and leave all options at their default settings, including configuration files set to “acuxdbc.cfg.” Create a virtual directory within IIS, leaving all defaults except "Execute Permissions:"; set this to "Scripts only".In that direc

Compiling using the --netdll flag on Windows 7 generates a CreateProcess failed error. Problem: Take a sample program (such as calc3.cbl), use the .Net interoperability compiler option --netdll. Compile with the following options:-o .\\object\\@.acu -x --netdll:2.0 The following error message is returned: CreateProcess failed for C:\\Windows\\Microsoft.NET\\Framework\\v2.0.50727\\AL.EXE \\target:lib \\v:1.0.0.0 \\embed:".\\object\\ACU.acu",AcuNet \\out:".\\object\\ACU.dll" ".\\object\\ACU.NETModule" ACU.acu - Completed: 0 Error(s), 0 Warning(s). This works on XP and Vista machines. Resolution: al.exe is part of the Microsoft .Net framework SDK. al.exe is not included with the Windows 7 OS, you must download and install the .Net framework SDK. Old KB# 14511

This article explains what to do when AcuXDBC gives the wrong date for a date mask that specifies only the year and month, YYYYMM. Problem: AcuXDBC supports incomplete date types. This feature is documented in Section 3.3.4 of the AcuXDBC User’s Guide as: "It is sometimes desirable to have incomplete date types, for example to have YYYYMM to simply store the year and month. AcuXDBC defaults the month and day to 1, so that incomplete types will be valid. Note that AcuXDBC can handle incomplete date types, but if you have a complete type and invalid date data, AcuXDBC cannot handle the date." However, if only a partial date mask is specified, the unspecified portion does not default to the correct value. For example, with a date mask of YYYYMM and data of 200810, the field might assume the value 2008-OCT-00 (which is not a valid date) instead of the correct value of 2008-OCT-01. Resolution: This is a known issue and has been fixed in Ver

This article provides information on the location of the vutil error code table and an example of using the table in problem resolution. Problem: When performing a file operation using vutil or vutil32, an error may be encountered. For example, the following vutil command vutil -info MYFILE may result in the following error: MYFILE: File broken (code 69) Understanding what “code 69” means would be helpful in resolving this error. Resolution: Vutil error codes are the same as the Vision file secondary error codes for error 98. The list of error codes may be found in the ACUCOBOL-GT Appendices Version 8.1, Appendix E: File Status Codes, E.3 Vision Secondary Error Codes for Error 98s. For this example, the entry in the list of errors would be: 69 A Vision 4 or 5 index segment is not found during an open. This error code is specific to Vision 4 or 5 files that consist of two parts, a data segment and an index segment. T