Rocket® COBOL

Problem: An ASP program accesses Vision data through AcuODBC.  After upgrading to AcuODBC 7.2.1 the following error is seen: The specified driver can not be loaded due system error 182 Resolution: There were multiple versions of AcuODBC installed on the server, 5.x, 6.x, and 7.2.1.  The solution was to uninstall all versions then reinstall only 7.2.1. Old KB# 2818

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: 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: Does C$XML support UTF-16? Resolution: C$XML (and AcuXML) don't support UTF-16. You can use only UTF-8. Old KB# 2788

Problem: When executing a "vutil -load" command  to load a sequential file into a Vision file, any records which would create a duplicate key condition are put into a file named filename.rej (Users Guide 3.3.10) What format is the filename.rej created in and how can the records be loaded into a Vision file? Resolution: The filename.rej file that contains the duplicate key records is in sequential file format and may be loaded into a similar empty vision file. Old KB# 2792

Problem: Calling AcuODBC version 7.2 from a .NET application encountered error on select statement: System.Data.Odbc.OdbcException: ERROR [42000] [AcuCorp, Inc.][AcuODBC Driver]Expected lexical element not found: <identifier> expected, ORDER found, near line 1, column 13 Resolution: The error indicates that the syntax error begins at the location of the '^' symbol. In this case, the table name "ORDER" is a reserved word in most database systems, thus it is not allowed as a user defined table name.  Renaming the table to a non-reserved word should avoid this error. Old KB# 2816

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: 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: 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: Adding an XFD to the system catalog using xdbcutil directly or through the addfile script caused the following error: Error: 'GENESIS_COLUMNS': Duplicate key Resolution: The XFD contained a column entitled "NUMBER" which is a reserved word with some SQL systems so AcuXDBC doesn't allow it as a column or table name. To resolve the error add the NAME directive in the FD to rename the column, then regenerate the XFD and try again. Old KB# 2844

Problem: Is there a way to see what version of an ACUCOBOL-GT object is when cblutil is not available? Resolution: If the Unix operating system being used has a magic file then it is possible to add an entry to display the version of the ACUCOBOL-GT object. First locate the magic file ie. $whereis magic $magic: /usr/share/magic.mgc /usr/share/magic /usr/share/magic.mime /usr/share/magic.save /usr/share/man/man5/magic.5.gz In this instance the /usr/share/magic file would be edited to include the following code. # Magic numbers for ACUCOBOL-GT object file #0   string      \\020\\022\\024\\040    ACUCOBOL-GT object file data 0       belong          &nbsp ; 0x10121420      ACUCOBOL-GT >4      beshort     

Problem: Starting AcuAcuXDBC Server from inittab or crontab fails. Resolution: Add the following to inittab or crontab: export GENESIS_HOME=/usr/acuxdbc export LIBPATH=/usr/acuxdbc/bin:$LIBPATH export PATH=/usr/acuxdbc/bin:$PATH Old KB# 2834

Problem: When trying to kill acuxdbcs with the batch file acuxdbcs.bat on a non-default port.  The message displays: C:\\Program Files\\Acucorp\\Acucbl800\\AcuGT\\bin>acuxdbcs -kill -n 20111 Sending 'vtxnetd suicide request' to '-n'. ERROR: HOSTNOTFOUND: Host '-n' not found, gethostbyname returned 11004 Sending 'vtxnetd suicide request' to '20111'. ERROR: SERVNOTFOUND: Service/Protocol 'vtxnet/tcp' not found (errno: 0) Sending 'vtxnetd suicide request' to 'jeeves'. ERROR: SERVNOTFOUND: Service/Protocol 'vtxnet/tcp' not found (errno: 0) The same is true when attempting to use -info on a non-default port.  The following message displays: C:\\Program Files\\Acucorp\\Acucbl800\\AcuGT\\bin>acuxdbcs -info -n 20111 Pinging '-n'.... SORRY: HOSTNOTFOUND: Host '-n' not found, gethostbyname returned 11004 Pinging '20111'.... SORRY: SERVNO

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

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: When using the version 8.x AcuSQL precompiler a syntax error is generated that did not occur in earlier versions when the embedded SQL code uses the "COALESCE" function. An example of this code:            exec sql                select                  coalesce(c_info,'')                  into :the-c-info                  from customer                 where c_number = :c-number            end-exec.     

Problem: Application runs against a MSSQL 2005 database.  It moves high-values to the key, or part of a key, does a START NOT GREATER, then a READ PREVIOUS.  The wrong row is being returned. If run against Vision files containing the same data the expected record is found. For example when the entire key is set to high-values the very last record in the Vision file is returned.  However, with Acu4GL for MSSQL, it returns a row somewhere near the end of the table or even the second to last row, never the last row. Resolution: The problem is that the database collating sequence is not binary. The server's default collating sequence is chosen on installation of MSSQL, however a different collating sequence for individual databases using the alter SQL command can be specified by issuing the follow SQL command: alter database databasename collate SQL_Latin1_General_CP850P_Bin It can also be modified by using the Microsoft

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: 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: 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: After an upgrade to a new server the DISPLAYs are no longer written to the log file.  Programs are executed in the background with: runcbl -b programname > output.log On the old server the DISPLAY statements were written to the log file but now the log file is empty after running the program. Resolution: The programs must be compiled with the -Ca option.Old KB# 2784

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: How to change the order of keys in .xfd file? Resolution: Use -Ck compiler flag: This flag causes the compiler to generate key numbers for indexed file alternate keys in a different order. Key numbers are used internally by the compiler and runtime to identify a key. Normally, you do not need to know the key number for a particular key, or care about the order in which they are generated. By default, the compiler sorts the alternate keys in record order before assigning key numbers. This ensures that the keys are given the same number regardless of the ordering in the file's SELECT. Specifying "-Ck" causes the compiler to assign key numbers in the SELECT order. For most applications, the order in which key numbers are assigned is irrelevant. This option provides compatibility with some other COBOL compilers. This could be helpful when you are sharing data files between ACUCOBOL-GT based programs and programs compiled with these other systems. [2008-07-11

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