Rocket® COBOL

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

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 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: 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: When shutting down the AcuConnect service the user receives the following prompt to the kill command: unix1:/opt/acucorp/800/bin # ./acurcl -kill Shutting down AcuConnect on: unix1 There are 0 child processes on: unix1 Do you really want to shutdown AcuConnect ? This is not a issue when running interactively, but when running from a script the prompt can be problematic. How can the prompt be avoided when running a script? Resolution: AcuConnect User's Guide Version 8.0 Chapter 8: Managing the System > 8.2 Managing the System: UNIX > 8.2.1 The acurcl Command > 8.2.1.6 acurcl -kill Unless the "-f" option is specified, AcuConnect prompts for confirmation before the halt action is executed. The following is an example of using the "-f" option to halt AcuConnect. Example: unix1:/opt/acucorp/800/bin # ./acurcl -kill -f Shutting down AcuConnect on: unix1 There are 0 child processes on: unix1 Ac

Problem: In some instances it is desirable to be able to use the file command to determine the version of a Vision file.   Resolution: If the Unix operating system is being used has a magic file then it is possible to add an entry to display the version of the Vision file. First locate your 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. # Vision 2 file 0       ulong          0x10121416     Vision >4      ushort         2              2 data file # Vision 3 file 0       ubelong  

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: Is there a way to access a Microsoft SQL Server table with AcuSQL using a variable to set the table name? Resolution: This can be done using dynamic SQL.  The following link to an article by Nigel Rivett has an example of how to do this: http://www.nigelrivett.net/SQLTsql/TableNameAsVariable.html Excerpts from the article provide a detailed explanation: This is a simple problem to solve but has a number of consequences. It is often because you wish to pass a table name to a stored procedure perhaps processing all tables in a database. Of course select * from @TableName will not work as the variable will not be resolved as containing the name of a table. The method used here is dynamic SQL - executing a built string. Create procedure s_ProcTable @TableName varchar(128) as declare @sql varchar(4000)             select @sql = 'select rows = count(*) from

Problem: After a while waiting for the server there comes a timeout message. This time (default=20 seconds) can be changed Resolution: Referring to manual: TC_SERVER_TIMEOUT This variable lets you determine how many seconds (from 0 to 32767) the client waits for a response from the server. If the client receives no response from the server in the specified time period, the following message box appears: The remote host is not responding. Press OK to close this program. Press Cancel to wait another %s seconds. where "%s" is the value of TC_SERVER_TIMEOUT. The default value is "20". Old KB# 2805

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

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: 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: 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: 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: 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: 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: Opening a table with Microsoft Access caused the following error: [TOD][ODBC][GENESIS]VISION: Too many columns 291 (max: 256) Resolution: Increase the MAXIMUM_COLUMNS setting on the Advanced tab of the DSN. The default value is 256. The allowable range is from 1 to 1024. Old KB# 2845

Problem: Installing an update from Microsoft has impacted Acucorp's Thin Client performance. What can be done? Resolution: It is possible that the patch installed changed the TCP/IP settings. Software such as Dr.TCP or TCPOptimizer can be used to tune TCP/IP settings. Setting the TCPReceiveWindow to 1500 on WinXP SP2 and Win2000 SP4 has proven to improve Thin Client speed when working with a Aix 5.2 5L PowerV host, along with other Unix boxes. This setting is not intended to be the "definitive" answer, but just a start from where to begin tuning TCP (and Thin Client) performance.  After any change a reboot is needed in order to see the effects. Using these settings can also solve other performance issues after installing SP2 on WinXP. Old KB# 2793

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: Using the supplied script, acuxdbcs.bat (acuxdbcs.sh on UNIX), AcuXDBC Server won't start on a non-default port. The start command used is: acuxdbcs.bat -start -p 20225 But it always starts on the default port, 20222. Resolution: Refer to the comments inside the script for proper usage:   rem =  Usage:   rem =      acuxdbcs -help   rem =      acuxdbcs -info [-n port] [server]   rem =      acuxdbcs -kill [-n port] [server]   rem =      acuxdbcs -start [-n port] [-l] Note that the AcuXDBC Server scripts accept -n to specify an alternate port, rather than -p. This command will work:  acuxdbcs.bat -start -n 20225 Old KB# 2840

Problem: The  AcuXDBC User's Guide Version 8.0, chapter 5, section 5.5.2, suggests that rather than having to set up system catalogs for each of your companies individually, you can do one of two things: 1) You can use wildcards and substitution characters (defined in the configuration file) to identify which company file to access. 2) You can assign table ownership to the different companies, then issue a single query to access all the data files. Current users of AcuODBC Server that are transitioning to AcuXDBC Server may prefer a method that allows for closer correspondence between the client DSN and filename prefix. Resolution: Current users of  AcuODBC Server are used to having different DSNs to point to particular file paths. This can be similarly accomplished by creating multiple configuration files and creating DSNs on client machines that each pointed to different configuration files. Since all configuration files

Problem: When running AcuConnect Thin Client on a Windows Server sometimes the number of client connections is limited to say 26 even though the license allows significantly more users.  The 27th attempt will receive an error "connection refused". Resolution: The Windows Desktop Heap configuration on the server is probably limiting the number of connections.   Here is the link to the Microsoft article with the info on Desktop Heap: http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q184/8/02.asp&NoWebContent=1 The pertinent information is under "Cause 2". The Heap management is complex and some customers have resolved the issue by increasing one parameter while others decreased another parameter. Testing different settings will be required. Remember to make a backup of the registry prior to making any changes. Old KB# 2794

Problem: Acu4GL for Oracle has been running on one server with no errors.  On a new server with Oracle 10g an Oracle error 600 occurs on various inserts. Resolution: ORA-00600 is a catch-all for Oracle meaning the error doesn't fit in any other specific error code.  The exact meaning of the error is determined by Oracle support personnel who examine the parameters within square brackets that follow the ORA-00600.   If the first parameter is [kpofdr-long] this is an error other Acu4GL users have encountered.  It is caused by bug #3612581 in Oracle 10g. Oracle has a patch that can be downloaded to fix it. If that first parameter is something other than [kpofdr-long] send the information to Oracle for interpretation. Old KB# 2832

Problem: After upgrading the server OS from AIX 5.2 to AIX 5.3 the screen display performance with Thin Client was seriously impacted. No changes had been made to the COBOL side of the equation so an AIX support consultant was called in to check networking parameters, but could find no serious problems. Are there any known performance issues with Thin Client and AIX 5.3? Resolution: The resolution to this particular problem was changing the network interface setting "large_send" to "no". The "large_send" network interface setting is new in AIX 5.3 (did not exist in AIX 5.2). A Google search of "aix large_send slow" turned up the following information links: This article from Symantec support site is dated March 2004: http://seer.entsupport.symantec.com/docs/266020.htm and this article from the "IBM AIX Discussion List" is dated April 2004: http://unix.derkeiler.com/Mailing-Lists/AIX-L/2004-04/02