Rocket® COBOL

This article describes how to resolve a vision file error 98,20. Problem: Vision files are portable, but if they are transferred in ASCII mode you will receive a 98,20 error when the program is run. Example: $runcbl custrpt.acu File error 98,20 on custfile.dat COBOL error at 000016 in custrpt.acu <Ok> File Status 98:Indexed file corrupt. An internal error has been detected in the indexed file. The secondary status code contains the internal error number 20 Non-zero key prefix on first key in node Resolution: Switch the transfer mode to binary and re-transfer the files. Old KB# 14296

This article describes the method for applying a license to an installed Liant product, without, requiring a reinstall of the product. Problem: To apply a new license on your system, you will need to use the License Utility, which installs the new license into the existing license vault. This utility program, licverifyall, is located in the SupportTools subdirectory of the installation directory. Resolution: Note: You may apply a new license while users continue to use the application. Note, however, that for all the changes to take effect, you will either need to restart the application or, for some server-based applications, restart the service or reboot the machine. To apply a new license, follow these steps: Locate the product installation directory. Place the new license, *.lic, into the SupportTools subdirectory and rename it to liant.lic. Execute the licverifyallprogram located in SupportTools, with no parameters. The program will find the new license and the exist

This article explains how to associate an ACUFH configuration file with a NetExpress project. Problem: Database Connectors uses an ACUFH configuration file; how can I associate this configuration file with my NetExpress project so that when the project runs, the ACUFH configuration file is picked up? Resolution: You can use the A_CONFIG environment variable to identify a personal ACUFH configuration file. For example: SET A_CONFIG=directory name\\file name. You can set this environment variable within the NetExpress IDE by following this process: Select Project > Properties. Click IDE. Add the environment variable A_CONFIG, and set its value to the location of your configuration file. Incident Number: 2259200 Old KB# 14283

This articles describes how to remove the NO-TAB graphical control property. Problem: When a screen has several entry fields and the user needs to skip some fields. The program can set the 'NO-TAB' property on the desired fields using 'MODIFY' and it works properly. However, there is no 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 property from a control is to destroy the control and redisplay it without specifying the NO-TAB style. Also, if the purpose is to avoid stopping in an specific control, users can use the ENABLE property. Turning off this property will do the trick. This property can be turned on at runtime with the MODIFY verb. Incident Number: 2221196 Old KB# 14262

Error 1904: failed to register NMSecComParams.dll file Problem: Error 1904.Module C:\\Program Files\\NetManage\\rss\\NMSecComParams.dll failed to register. HRESULT -2147221164. Contact your support personnel Resolution: Disable Data Execution Prevention (DEP) using the steps below: Login as an Administrator on your PC. Go to Start > Control Panel then double click on the System icon. Select the Advanced tab and, under the Startup and Recovery section, click on the Settings button. Click Edit. This will open the Boot.ini file in Notepad. Note: Make a backup of this file before you make any changes. Search for the line that contains the following string: /NoExecute= Change this string to: /NoExecute=AlwaysOff Save the file and reboot the PC. Re-install RUMBA. It should install without the Error 1904 messages. Restore Boot.ini back to its original state. Old KB# 14203#Rumba

This article describes how to set multiple values for Source Code Control options of the ACUCOBOL-GT compiler. Problem: Is it possible to use multiple patterns with –Si and –Sx compiler options? Resolution: To use multiple values, you can repeat the option: Ccbl32 –Si value1 –Si value2 –Si value3 program.cbl Or separate all the values with a semi colon: Ccbl32 –Si value1;value2;value3 program.cbl Incident Number: 2279382 Old KB# 14282

This article explains what you can do when you get this error. Problem: When compiling to ".exe" and attempting to link the new Database Connector EXTFH module, ACUFH.dll, this error is seen: unresolved external symbol _ACUFH. Resolution: The initial release of Database Connectors did not come with a way to link to the ACUFH.dll. Future versions will include ACUFH.lib, the import library for ACUFH.dll, allowing COBOL programs to be linked. In the meantime, use "int" or "gnt" level code for execution. It is also possible to create your own ACUFH.lib by creating a dummy ACUFH.dll with Visual Studio and having a single export (ACUFH). Incident Number: 2279117 Old KB# 14286

This article describes how to translate French Characters between a Windows UI screen Character set and the Oracle Database Character Set. Problem: Using a graphical interface on Windows, the data you recover is not stored properly on your Oracle database using ProCOBOL, and you are losing special characters like "éàù". Resolution: Set up the following environmental variable before executing the runtime: Export NLS_LANG=FRENCH_FRANCE.WE8MSWIN1252 This tells the PROCOBOL code you have in your application that the IO with the COBOL program will be made with this Character set and that the data should be transformed before being stored on the database (to whichever Character set the database is set at). Your UI will now handle the standard Windows French characters properly and translate them when communicating with the Database. Old KB# 14259

Fileshare server cannot be started. The error message is “A CCINAMPU listen call failed, please re-try with fewer active connections.” Problem: The Fileshare Server cannot be started. The following error message appears: FS148-I CCI return-code (function 07) = 00000009CCINAMPU-0030E A CCINAMPU listen call failed, please re-try with fewer active connections. This error occurs only when using the “named pipes” communication protocol, that is, ccinampu. The error does not occur when using the ccitcp communication protocol. Resolution: For named pipes protocol (-cm ccinampu), Fileshare will create a FIFO in /usr/spool/uucppublic/.CCI named .servername (where .servername is the name specified when starting Fileshare). It is necessary for the directory /usr/spool/uucppublic to exist. If this directory does not exist, the error will occur. Some UNIX or Linux machines do not include a directory named /usr/spool/uucppublic. If this directory does n

This KB article demonstrates how to replace trailing spaces in an alphanumeric variable with low-values or other characters. Problem: You have an alphanumeric variable with trailing spaces and you want to change them to low-values or to another character. Resolution: Simply use the following syntax from the INSPECT verb: INSPECT WS-ITEM REPLACING TRAILING SPACES BY LOW-VALUES. Old KB# 14260

This article describes how to modify AcuXDBC table ownership with the provided batch files. Problem: Some ODBC front-end applications have trouble with the "public.tablename" format that is the default for AcuXDBC when it adds table information to the system catalog.  Frequently, when using Microsoft Access for example, an application cannot interpret the owner.tablename syntax, so an application error results.  Removing the "public" owner from the table specification is necessary for the desktop application.The AcuXDBC manual (section 5.3.1) indicates to use the -o "<space>" option of the XDBCUTIL script.  An example of how to automate the process when using script, demo.bat is provided below. Resolution: Here is a quick way to use the batch files provided with the software to make this change. In the bin directory, locate addfile.bat and open it in a text editor. There are two lines, which need to be edit

This article discusses a case that causes a checker error and provides a method to work around the error. Problem: Compiling a program with the CREATEXFD compiler directive that uses the VAR_LENGTH XFD directive on a file description results in the following compiler error (once for each time the source includes the VAR_LENGTH directive): COBCH1508E Unknown XFD directive: '' : "test.cbl"(63,21) However, the section Using XFD Directives in your Database Connectors User's Guide states that VAR_LENGTH is a supported directive. Resolution: Install Net Express or Server Express 5.1 WS2 HF 4 or later when it becomes available. Until this version is available, however, you can use the following work-around: Change the underscore character in VAR_LENGTH to a hyphen: VAR-LENGTH. Incident Number: 2266175 Old KB# 14265

This article describes the cause of this compile time warning message and what you can do to resolve the problem. Problem: Compiling a COBOL program using the CREATEXFD directive can result in the generation of the compile time warning message “Field xxx causes duplicate database data.” The condition that causes this compile time warning to be generated is described in the Database Connectors User’s Guide, section "Performance and Troubleshooting." This warning can occur when you compile with the CREATEXFD directive. The XFD will be built and the Connector will operate correctly. However, the warning informs you of a special database situation that is not advisable. This warning means that your record definition should be restructured. Your current definition is set up in such a way that both of the following are true: You have overlapping key fields Both keys must be represented in the database as separate items Data

This article explains how to bind a compiled application with a DB2 collection ID of greater than eight characters without truncating the collection ID. Problem: Bind fails for a compiled application, and the collection ID truncates at eight characters. For example: SQL0061W The binder is in progress. SQL30104N Error in BIND or PRECOMPILE option "LANGLEVEL " with value "". SQLSTATE=56095 SQL0082C An error has occurred which has terminated processing.SQL0092N No package was created because of previous errors. SQL0091N Binding was ended with "3" errors and "0" warnings. Resolution: Compile and bind your application as follows: At a UNIX command prompt, enter the following to compile the application using the DB2(UDB-VERSION) compiler directive: DB2(UDB-VERSION=version) Where version is one of the following: Version Description V8 DB2 version 8.x V9 DB2 version 9.1 V95 DB2 version 9.5

Do the extend products work on multi-CPU machines taking advantage of the multiple CPUs or multiple cores in a CPU? Problem: Do the extend products work on multiple CPU machines? Or take advantage of multi-core CPUs? Resolution: The extend products do not take advantage of multiple CPUs or multi-core CPUs. Any processor or other load balancing assignment is handled by the Operating System on which the extend products are being executed. There are no plans to enhance the extend product line to implement this type of functionality. There have been no issues reported using the extend products on multiple CPU or multi-core CPU machine that are specific to operating in those environments. Old KB# 14231

This article describes how to set up RUMBA to enable users to enter non-numeric characters into Mainframe numeric fields. Problem: Does RUMBA support the Numeric Override feature? Resolution: The standard 3270 host applications allow the definition of data input fields as either numeric only or alphanumeric. If a user tries to enter a non-numeric character into a numeric field, 3270 applications do not accept the input. RUMBA Mainframe display supports a Numeric Field Override feature to allow for non-numeric characters to be entered into numeric fields. By default, this option is disabled in RUMBA. Perform the following steps to enable this option: Launch a RUMBA Mainframe Display session. Click Options > Edit > General. Check Numeric Field Override; then click OK. This enables the Numeric Field Override option, and enables users to enter non-numeric characters into numeric fields. Old KB# 14235#Rumba

EXAMINE WSVAR TALLYING UNTIL FIRST "Y". produces compiler error Problem: EXAMINE WSVAR TALLYING UNTIL FIRST "Y". produces compiler error Resolution: Use compiler directive dialect(OSVS) or consider using the following INSPECT statement         INSPECT WSVAR TALLYING count1 For Characters Before "Y" where count1 is declared as pic s9(9). Old KB# 14248

When compiling the following program within the IDE, a 163 error differing from that generated from the command line results: $SET CHECKNUM IDENTIFICATION DIVISION. DATA DIVISION. WORKING-STORAGE SECTION. 01 N PIC 9(8) VALUE 0. 01 M PIC X(8) VALUE " ". PROCEDURE DIVISION. MOVE SPACE TO M. MOVE M to N. DISPLAY M. DISPLAY N. GOBACK. its error message is displayed as Object Code error : file 'a' error code: 163, pc=0, call=1, seg=0 163 Illegal character in numeric field (in D:\\anken2\\7800\\7848\\demo\\a.cbl, line 9) When the same program is built from the command line and run the message is: Object Code error : file 'a' error code: 163, pc=87, call=1, seg=0 163 Illegal character in numeric field Why is there a difference? Problem: When compiling the following program within the IDE, a 163 error differing from that generated from the command line results:       $SET CHECKNUM        IDE

This article explains how to successfully install EnterpriseLink version 5.0.5 on Windows Vista when the setup program returns an error. Problem: When attempting to install the base version of EnterpriseLink version 5.0.5 on Windows Vista, the setup program returns an error message indicating that you do not have the required 2.1.2.4202.3 or later prerequisite version of the Microsoft Data Access Components (MDAC) installed. This happens because Vista no longer includes MDAC; it has been replaced with Windows DAC, which has the same version number as the Windows version number (in this case, version 6.0). Resolution: You can force EnterpriseLink to install on Vista without checking for a valid version of MDAC by entering the following at a command prompt in your EntepriseLink installation directory: setup.exe /IGNORE_MDAC Note: /IGNORE_MDAC must be in upper case. Old KB# 14276#EnterpriseLink#Rumba

This article explains how to change the port that the Windows Data Server is using. Problem: How do I change the port that the Windows Data Server is using? Resolution: On your Data Server system, stop the Data Server. Do this from the Windows Control Panel's Services utility, available under Administrative Tools. At a command prompt, enter regedt32 to start the registry editor. Navigate to HKLM\\Software\\ODBC\\ODBC.INI\\SimbaServer\\SvrPort. Change the default port number,1583, to either 1584 or some other port number that you know is not in use. Restart the Data Server. Do one of the following: If your system has the Database Administrator version of the Data Client installed: Start the Data Client. Click the entry for the Data Server system; then click Modify. Change the port number to the same number you specified in the registry in step 4 above; then click OK. If your system does not have the Database Administrator

This article describes what C compiler to use for relinking the runtime with C libraries on Unix/Linux. Problem: You have created your own C libraries or you want to use 3rd party C libraries that will be called from ACUCOBOL-GT programs. Resolution: You need to relink the runtime by using An ANSI 89-compliant C compiler supplied by the vendor of your UNIX system, either included as part of your UNIX system or as an add-on option. Check with your operating system vendor to see if the C compiler is capable of building shared libraries. If it is not, you will need a full version of the compiler to relink the ACUCOBOL library. Please remember than Bundles will not be enough, and a full version of the compiler will be needed for most systems. Detailed information on interoperating with C and C is provided in the manual A Guide to Interoperating with ACUCOBOL-GT, Chapter 6. Incident Number: 2181911 Old KB# 14268

Runtime fails to initialize properly. Problem: When trying to execute the 64-bit Windows runtime you would see the following error: The application failed to initialize properly (0xc0150002) Resolution: This is because atermmgr.dll is looking for a 32-bit version of comctl32.dll instead of the 64-bit version. You will need to extract the files in the attached zip archive and replace the existing files in the \\AcuGT\\bin directory Incident Number: 2259559 Old KB# 14204

When using a WSDL to generate a Web Client, an error is shown "Error: Cannot find type information" Problem: When accessing Services > Generate Client > using WSDL , the following error is received: Error: Cannot find type information for:'optInStatus' of'CPNI' of'accountSummary' of'GetAccountSummaryReturn 'The header of the WSDL being used:<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions targetNamespace="http://simulation.testspace.com/omnia" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://simulation.testspace.com/omnia" xmlns:intf="http://simulation.testspace.com/omnia" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"xmlns:xsd="http://www.w3.org/2001/XMLSchema"><!--WS

*1041-E Data item has zero size, or group not yet completed. Value of 0 assumed. * 27-S Number too large Rebuild complete with errors 01 ADDR. 05 ADDRS. 10 ADDR-LINE PIC X(20) OCCURS 6 INDEXED ADDR-IDX. 78 FIND-STRT VALUE LENGTH OF ADDR-LINE. 78 FIND-LEN VALUE LENGTH OF ADDRS - LENGTH OF ADDR-LINE. 01 ANOTHER-RECORD. Problem: *1041-E Data item has zero size, or group not yet completed. Value of 0 assumed. *  27-S Number too large Rebuild complete with errors 01 ADDR.    05  ADDRS.      10  ADDR-LINE       PIC X(20) OCCURS 6 INDEXED ADDR-IDX. 78 FIND-STRT         VALUE LENGTH OF ADDR-LINE. 78 FIND-LEN  VALUE LENGTH OF ADDRS - LENGTH OF ADDR-LINE. 01 ANOTHER-RECORD. Resolution: The 1041-E Data item has zero size, or group item is not yet completed, value of 0 assumed, and the 27-S Number too large error a

This article describes what to do when Vision files are created without permissions on Linux. Problem: Vision files are created with no permissions on a Linux server in a thin client environment. Files look like this: ---------- 1 user group 1024 Feb 10 16:49 filmografia.vix---------- 1 user group 2048 Feb 10 16:49 filmografia Resolution: Vision files created via thin client assume permissions depending on the UMASK value set inside the AcuAccess file. The default UMASK value is 002, which means that Vision files will be created in this manner: -rw-rw---- 1 user group 1024 Feb 10 16:49 filmografia.vix -rw-rw---- 1 user group 2048 Feb 10 16:49 filmografia If UMASK has been modified, persmissions will be set accordingly with the value provided. Setting UMASK to 777 causes files to be created with no permissions. Incident Number: 2266524 Old KB# 14285