Rocket® COBOL

Problem: Program is generating an error 97 (using DG error codes) "too many files open" when opening a file via AcuServer.  The runtime configuration file already has MAX-FILES set to a number larger than is necessary for the number of files that will be opened, but the error is still generated. Resolution: The MAX-FILES configuration variable needs to be set in the AcuServer configuration file as well.  The formula for determining what value it needs to be set to for AcuServer is: total number of files a user can ever have open * total number of users who will ever be accessing files simultaneously Old KB# 2819

Problem: Is it possible to use the "@[DISPLAY]:" prefix to delete a file on the PC using the C$DELETE routine or use CBL_DELETE_FILE routine to delete the file when running Thin Client? Resolution: At this point this is not possible to use the C$DELETE or CBL_DELETE_FILE routines to perform actions on a client machine. However it is possible to create a batch (.bat or .cmd) file on the client machine which uses the DOS delete command and execute it using the C$SYSTEM library routine with the CSYS-DESKTOP parameter. Old KB# 2808

Problem: Is there a way of testing AcuXDBC's connection with AcuXDBC Server without using a 3rd party application? Resolution: This is possible.  On the client machine open a command prompt and navigate to the AcuGT\\bin directory.  Type: odbcsql.bat -d "DSN-NAME" where DSN-NAME is the name specified for the dsn in the Data Source Administrator. This directly queries AcuXDBC Server that the DSN-NAME points to.  Assuming that the sample data was used during the creation of the system catalog, at the odbcsql prompt type in a query to the database: select * from pets; This should return all of the rows from the sample pets table. Old KB# 2835

Created On:  1 July 2011 Problem: Which versions of Microsoft SQL Server are compatible with versions of Acu4GL? Resolution: Acu4GL Versions SQL Server 6.x , 7.x 2000 7.x, 8.x, 9.x 2005 8.x, 9.x 2008 9.x 2008 R2 Old KB# 2828

Problem: Does C$FILEINFO support the @[DISPLAY] syntax to retrieve information from a file residing on the client machine? Resolution: This functionality is implemented in version 8.0.0.  Earlier versions do not support the @[DISPLAY] syntax for C$FILEINFO library routine. For earlier versions there is a workaround involving calls to Windows API functions in MSVCRT.DLL and KERNEL32.DLL to get the desired information. The attached COBOL programs, TESTIT.CBL and TCFILEINFO.CBL, are an example of how to implement the functionality with Thin Client versions 7.x and earlier. Please note the sample programs are provided "as is".  They may be freely modified and distributed, but have no warranty of functionality or support. Attachments: TESTIT.CBL Old KB# 2811

Problem: Attempting to link a table with Microsoft Access or Excel fails with the error: ODBC--call failed.  [TOD][ODBC][GENESIS]WORM: Cannot open 'GENESIS_XCOLUMNS',Too many open files (#-3) Resolution: The problem can be fixed by setting MAX_FILES to a higher number in the AcuXDBC configuration file.  The system catalog is a set of Vision files and each open can use up to 16 files. The default is 32, so opening up 2 DSNs causes the MAX_FILES default setting to be exceeded resulting in the error. Old KB# 2843

Problem: When using AcuConnect Thin Client and peforming an ACCEPT SYSTEM-INFORMATION from SYSTEM-INFO the STATION-ID variable does not return the client information as is done when using a standard runtime. Resolution: In the Thin Client environment the STATION-ID variable will contain the TTY assigned to the runtime on the server.   The ACCEPT should be changed to an ACCEPT from TERMINAL-ABILITIES and the CLIENT-MACHINE-NAME variable will contain the necessary information. Old KB# 2809

Problem: When the tour.cbl sample program from the Acucorp distribution is compiled and executed via AcuThin installed on a Windows client and AcuConnect Thin Client version 7.2.1 is installed on an AIX server, labels and entry-field text are not displayed. If the program is executed directly on the Windows client or AcuConnect Thin Client is installed on a server other than AIX, labels and entry-field text are displayed as expected. Resolution: Upgrade to version 7.2.2 or higher. Attachments: Thin_Client.JPG Old KB# 2806

Problem: How to read client environment variables through Thin Client Resolution: You can use C$SYSTEM to run this command line: echo %GENESIS_HOME% > NAME.TXT > 2>&1 After that, you have to copy NAME.TXT to the server, and then you can read it as a normal input file. Old KB# 2802

Problem: Migrating from Vision files to using a database to house data, a significant decrease in performance was experienced. The DBA found that temporary tables of  600,000 rows are being created for each START that is done in the COBOL program. Tuning of the database has had some positive effect, but not enough to bring performance into an acceptable range. Resolution: Programmatically implementing the use of the WHERE CONSTRAINT dramatically increased performance. Documentation of the WHERE CONSTRAINT can be found in the Acu4GL User's Guide, Chapter 9: Performance and Troubleshooting, section 9.1 Performance Issues. Old KB# 2826

Problem: Runtime reports an error: wrun32 .2lc is missing Resolution: This message indicates that AcuSQL was installed, but there is no llicense file (wrun.2lc).   Solution is it uninstall AcuSQL and only install the products that are licensed. Old KB# 2825

Problem: The program executes a VB program using a call to C$SYSTEM.  This works fine when running directly on Windows, but when run via Thin Client the program does not execute. Resolution: The C$SYTEM library routine accepts a "flags" value.  The various flags are described in the page for C$SYSTEM in Appendix I of the AcuCOBOL-GT documentation. There we see a flag named CSYS-DESKTOP with a value of 128.  This flag tells the Runtime to execute the command on the client PC when running in a Thin Client environment.  This flag value is ignored if not running via Thin Client. The solution is to add the CSYS-DESKTOP value to whatever flag value is already being used. Old KB# 2777

Problem: How to use the run-time profiler within thin-client? Resolution: To use the profiler with the Thin Client, you have to specify the "-p" flag on the acuthin command line. You cannot put it as part of the alias in the acurcl.ini file. The command line should look like the following: acuthin myserver -p myalias This will cause the runtime to create a file called "acumon.xml" in the Working Directory that you have specified when creating the alias. Old KB# 2800

Created On:  1 July 2011 Problem: Which versions of Oracle are compatible with which versions of Acu4GL? Resolution: Acu4GL Versions ORACLE 6.0.x & 6.1.x 7.x 6.0.x & 6.1.x 8.0* 6.0.x & 6.1.x 8i* 6.2.x, 7.x, 8.x, 9.x 9i* 7.x, 8.x, 9.x 10G* 8.x, 9.x 11G*(* 32 bit and 64 bit) Incident #24909 Old KB# 2827

Problem: The .bat and .sh files provided with AcuXDBC contain a "-z" switch in commands to xdbcutil, xdbcsrvr, xdbcping, and xdbckill that appears to be undocumented. Resolution: The "-z" switch is used to suppress the banner that may displayed when the scripts are executed on some systems. Old KB# 2842

Problem: Question is: Do you have to be ROOT when you start AcuConnect Resolution: Only the installation has to be done as Root. AcuConnect can be started from any user with appropriate permission Old KB# 2807

Problem: When trying to run an Acuconnect process, the "Wrong license for this type" error message appears in server trace file. Resolution: There are two types of Acuconnect services: Thin Client and Distributed Processing.  If the correct type of license is not available, the error will be generated. Activating the correct Acuconnect license resolves the issue. Thin Client license:                         acurcl.alc Distributed Processing license:   acurcl.clc Old KB# 2796

Problem: Invalid cursor state message after performing FETCH after 2nd OPEN statement.  Can the cursor be reopened? Resolution: To perform additional FETCH operations, the cursor must first be closed and then prepared again. Old KB# 2823

Problem: Is there a way using Acurcl -info to only show ClientUsername/Host/PID/StartTime on one line per process running? Resolution: On Unix the command line below will show the lines with the ClientUsername / Host / PID / StartTime. If acurcl is started on a port other than the default change the line to reflect the correct port number: acurcl -info -n 5632 2>&1 | egrep -v "^Client |^Server |^  Directory|^  Command|^ *$|^ " Old KB# 2799

Problem: After upgrading from 7.4 to 8.0 on a UNIX server version 7.4 AcuXDBC Server is running fine on the default port, 20222.  When version 8 attempts to start it just spins and eventually maxes out the CPU. Version 8 is started on port 20223 with:  acuxdbcs.sh -start -p 20223 Resolution: The acuxdbcs.sh script uses -n for specifying the port.  The -p was ignored so Version 8.0 was trying to start on the default port, 20222, which was already occupied by 7.4.  This caused Version 8.0 to spin and consume the CPU. Using this command resolved the problem:  acuxdbcs.sh -start -n 20223 Old KB# 2838

Problem: An AcuODBC front end application fails with: ODBC - call failed [AcuCorp, Inc.][AcuODBC Driver]Out of range Col: 14 Hex Value: 3230303030393200(#1011) Resolution: Change the "Invalid Numeric Data" option on the Advanced tab for the DSN in the ODBC Data Source Administrator to "Zero". Old KB# 2815

Problem: With a "read/write" license for ODBC Server (as opposed to "read-only"), running a query results in 'Vision Mode Clash" error dialog. Resolution: In addition to installing the license, the DSN must be "Read/Write", not "Read Only". Note that this applies to both AcuODBC and AcuODBC Server. Old KB# 2814

Problem: The actual names of most of COPY library-names (file-names) are lower-case.  The files reside on AIX (IBM Unix) which is a case-sensitive OS.  The programs are compiled via AcuBench and a compiler on a Windows PC.  The COPYPATH includes a reference to the production COPY directory on AIX via a mapped drive using Samba. According to all of the documentation found for Versions 7.0 and above (User Guide 2.5/2,6 and Reference Manual 2.4.1), lower-case library names need to be placed in quotes: Note: User-defined words are always treated as uppercase on machines where file names are case-sensitive [UG 2.5]. However in Version 7.0.1, it appears making the library-names uppercase in the Cobol source code is acceptable.  No compile errors are generated using upper-case or lower-case names with or without quotes.  However, uppercase in the "OF" clause does NOT work whether or not it's in

Problem: Is it possible to use the SQL.ACU COBOL program when accessing ORACLE and MS SQL environments during the same run execution? Testing has shown that with both 4GL products included in the runtime SQL.ACU always defaults to the Oracle connection and will not access Microsoft SQL Server. Resolution: SQL.ACU calls the I$IO library routine using the EXECUTE opcode.  This opcode takes as its first parameter the file system to execute the SQL on. The way that SQL.ACU gets that information is to look at a configuration variable SQL-TARGET, which should name the file system desired (as listed in filetbl.c)e.g: ORACL or MSSQL would need to be specified before the call to SQL.ACU. Without that information, SQL.ACU will execute the SQL on the first non-vision file system (Oracle appears first in filetbl.c so would be the connection used). Another option for you is to write the sql commands to a file from the COBOL program and then u

Problem: When using AcuConnect ThinClient version 7.0.1, and Web Thin Client, a problem occurs when AcuConnect Server(acurcl) and Web Thin Client(acuthinax.ocx) run on the same PC: The dialog states there is a sharing violation of zlib.dll. The problem seems to be just a warning, since after clicking the "OK" button, the application runs without any problem. Resolution: When embedding the runtime DLLs as resources in the web runtime and the web thin client in version 8.0, Acuconnect now performs a version control check of the dlls (if already present) to ensure version compatibility. This was however not correctly done for external lib zlib.dll.  The work around for previous versions is to use a resource tool, like the one available in Microsoft Visual Studion, to set the zlib.dll version to match the actual ACU version. Old KB# 2801