Rocket® COBOL

Problem: Using the asql prompt or odbcsql prompt the query entered is not executed.  After pressing 'Enter' the prompt returns but the query is not executed. Resolution: All queries must be terminated by a semi-colon (;). Old KB# 2857

Problem: When attempting to connect to the AcuXDBC driver a user may be prompted to enter the user name and password.  What is the default account for administrative functions and where can this information be located in the documentation? Resolution: For AcuXDBC, the default administration account login information is provided in the AcuXDBC User's Guide, Version 8.0, Section 6.3.2. user name: system password:  manager Old KB# 2849

Problem: Is it possibile to modify list box property UNSORTED, to have a sorted list box? Resolution: Once the listbox style is set to UNSORTED it cannot be reset to the default sorted style. You must destroy the UNSORTED listbox and then rebuild it with the default style. Or you could define two identical listboxes in the same space, give one of them the UNSORTED style, and add items to both. Then using the VISIBLE property, reveal whichever you want the user to see. Old KB# 2772

Problem: Using Thin Client is there a way to cause the runtime on the server to exit when the network connection is lost? When this happens orphan runtimes are left and hold 1 license seat that is not released until the runtime is killed. Resolution: In some circumstances, in a Thin Client environment, the client can be unexpectedly disconnected from the server.  In order to capture this event, the TC_QUIT_MODE server runtime configuration variable was introduced. TC_QUIT_MODE passes a numeric value to stdout when a client PC is unexpectedly disconnected.  This information can then be used by the operating system to perform any needed additional tasks. Here is how it is implemented:        IDENTIFICATION DIVISION.        PROGRAM-ID. CLIENT-DISCONNECT.        REMARKS.    This program demonstrates TC_QUIT_MODE

Problem: Executing a GUI application using a manifest file causes the windows and controls to display with the Windows XP style but the tab controls look bad.  Specifically, the background of labels, radio-buttons and check-boxes doesn't match the tab color. Resolution: The problem is that with XP style the tab is not the same as the window's background color, is not a solid color but graduated (lighter at the top, darker at the bottom) and labels, radio-buttons and check-boxes take their background color from the main window.  The result is an unattractive tab presentation. Setting the transparent property fixes the problem for labels but radio-buttons and check-boxes don't have a transparent property. If one can't avoid placing radio-buttons and check-boxes on tabs a workaround is to place a frame on each tab page and set the frame color and fill to be the same as the main window. The attached program, tabm

Problem: Pprogram has a push-button with a long title to display on two lines but nothing makes it look right.  Embedding the carriage-return in the title it still comes out on one line. Resolution: Define a working-storage item containing the title and use that working-storage name in the push-button's title property.  Make sure to set the multiline property of the push-button. For example, use this working-storage description: 01 ButtonTitle.     05 LINE1 pic x(5) value "line1".     05 LF pic x(2) value x"0D0A".     05 LINE2 pic x(5) value "line2". Then a screen-section description of the push-button:     03 Push-Button,          COL 4, LINE 4, LINES 4 CELLS, SIZE 7 CELLS,          MULTILINE, TITLE ButtonTitle.

Problem: Performance problems are encountered with some computers with Network Interface Cards set to Auto-Detect for both 10M Ethernet & 100M when using Thin Client. Resolution: Configuring the network interface cards to use 100M only and the performance issues are resolved. Old KB# 2803

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: 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: A C# program using ADO.NET to connect to Vision ISAM data through AcuODBC executed the following SQL statement: SELECT MY_FIRST FROM MEMBER WHERE MEMBER.MY_CLUB=481 AND MEMBER.MY_NUMB='D148687     ' This resulted in the following error: System.Data.Odbc.OdbcException: ERROR [S0000] [AcuCorp, Inc.][AcuODBC Driver]Invalid operand for operator: = Resolution: Although the COBOL FD has both MY_CLUB and MY_NUMB defined as PIC 9(3), they have to be passed as string data types  instead of numeric values from the C# program to avoid the error. Old KB# 2817

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: 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 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: 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 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: Connecting to AcuXDBC server resulted in one of the following errors: SQLState: 28000 EXECFAIL: Exec 'acuxdbc04' failed on host 'my_server' (errno: 2) Connection failed: SQL State: 28000 [TOD] [ODBC Driver] EXECFAIL: Exec 'acuxdbc04' failed on host '192.100.1.1' (errno: 0) Resolution: The typical reasons for this problem are related to permissions, e.g. which user started AcuXDBC Server and/or what the permissions are for the files AcuXDBC Server needs. This may be resolved by adding "export PATH=$PATH:/opt/acucorp/nnn/bin" (where 'nnn' is replaced by the correct directory, e.g.: 740 or 800) at the beginning of the acuxdbcs.sh script, that way regardless of which user starts AcuXDBC Server the correct environment settings will be in place. Old KB# 2833

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: 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: 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 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: Is there a way to create a socks level trace when using Acurcl? Resolution: Instructions for performing a socket level trace with Acurcl. On the client side: Depending on how the application is started, add "-t7" to the command line that invokes acuthin;  Ex.      Acuthin.exe -t7 <server-name> <alias-name> This will produce two files on the client.  The first is called "displog" that contains tracing information specific to when controls are created, modified or destroyed, the second is a socket level communication trace named "socks<pid#>.trc". These files will be created in either the current directory, the location specified in the "start in" property of the icon or on the desktop. On the server side kill Acuconnect and restart it adding "-t 16535" at the end of the command string.  Ex.     &nbs

Problem: C$SOCKET with AGS-WRITE works with the Microsoft FTP Service but not when used with Serv-U FTP Server v6.4 for WinSock. The problem is in the command-string, as you can see in the example below, it describes that the string should end with the line feed character x"0A". Example coding: - if parse-command-code = "220"    initialize unix-send-command    move 1 to unix-send-cmd-length    string "USER " delimited by size              unix-username delimited by spaces              x"0A" delimited by size              into unix-send-command with pointer              unix-send-cmd-length    subtract 1 from unix-send-cm

Problem: An application running on Linux attempts to open a large binary sequential file (> 3GB) and receives a file status 30,27. Resolution: An error 30 indicates the issue is on the operating system side.  The secondary error 27 indicates the file is too large, as defined in the errno.h file for the system (/usr/include/asm/errno.h in this particular case): #define EFBIG           27      /* File too large */ The standard file API has a limit of 2 GB. The solution is to add "USE_LARGE_FILE_API ON" to the Runtime configuration file or set it in the environment. Old KB# 2776

Problem: Running acuserve and attempt to kill with     acuserve -kill -nf (port number) The following message appears: Socket error: 10102 Resolution: There is typically an issue with the host name on the server.  Open the host file in etc directory ie more /etc/hosts and verify that the information is correct. Alternatively specify which hostname/IP Address that the acurcl daemon should listen on by setting the AcuConnect configuration variables SERVER_IP and/or SERVER_NAME. For further information about them see the AcuConnect documentation. It is also possible to specify which hostname the -info or -kill command should be sent to by specifying the hostname on the command line.  For example: acurcl -info {servername} acurcl -kill {servername} Old KB# 2804

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