Rocket® COBOL

This article addresses a1004 error during Web-to-Host 5.3.1 installation on IE 5.5. Problem: Error 1004 is reported when installing Web-to-Host 5.3.1 on IE 5.5. Why is this? Resolution: This error message indicates the incompatibility with IE 5.5. The solution is to upgrade IE to at least version 6.0 ServicePack 1. Incident Number: 2281571 Old KB# 14835#Rumba#Web-to-Host#OnWeb#ProClient

This article explains how to resolve the Windows Installer Package Error 1721 when installing any Micro Focus product which uses the Microsoft msi installation technology. Problem: When installing a Micro Focus product which uses Microsoft’s msi installation technology you may get the following error message, particularly if you are installing an updated version of a product for which you already have installed on the machine. Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Resolution: Start your computer in safe mode. To do this, follow these steps: Restart the computer. After the BIOS information is displayed, press F8. Use the DOWN ARROW key to select Safe Mode, and then press ENTER. Use the UP ARROW key and the DOWN ARROW key to select your computer, and then press ENTER. Log on to the computer as local admin

This article explains the error message Operand Time-Of-Day is not declared. Problem: During compile of a program which contains a ----move time-of-day to ws-time-of-day--- I receive the error message Operand Time-Of-Day is not declared:#compile: gen400.cbl - 760 lines 486 move time-of-day to ws-time-of-day. * 12-S******************** ( 0)** **   Operand TIME-OF-DAY is not declared Resolution: TIME-OF-DAY is a special register data item. This special register requires the compiler directive OSVS. cob -uvC OSVS pgm.cbl Incident Number: 2352310 Old KB# 14859

This article explains why COBOL compiler returns 8-S Unknown COPY file <file name> specified. Problem: When compiling a COBOL program that contains copybooks that is greater than 256MB, the compiler returns the following error even though the copybook exists and is case sensitive: *    2  copy "<copybook name". *   8-S**************************  (0)** **    Unknown COPY file <copybook> specified Resolution: The reason this is happening is because the total limit for a COBOL program data division is 256MB. The compiler would only have opened the file and read the first x number of bytes. A too large data division would get a clear message indicating that fact. The file is so large the CBL_OPEN_FILE or CBL_READ_FILE has failed and returned a non-zero file status, hence the error. Old KB# 14889

This article explains why the cobrun command displays the message cobrun32: cobol version number invalid, call tech support. Problem: The command cobrun displays an error . The UNIX commands echo $COBDIR , cd $COBDIR run fine and display the directory. If the command mflicense is used to display the deployment licenses , the following message is displayed: {directory of Micro Focus product}/bin/mflicense: line 100: {directory of Micro Focus product}: is a directory What can be done to resolve this? Resolution: It is necessary to verify the value of the environment variable. These messages are displayed when this value is with a trailing space. A trailing space can be created with the following sequence: COBDIR='/opt/microfocus/cobol<space>' export COBDIR Old KB# 14887

This article explains how to use Level 49 Unicode host variables and parameters. Problem: Using a relational database within Microsoft SQL SERVER 2008 where table columns are defined as NVARCHAR. In order to read and to update these columns it should be possible to define and to use these columns as well. How can SQL datatype NVARCHAR be used? Resolution: Net Express 5.1 WebSync4: Beginning with that WebSync4 it is now possible to define and to use those host variables correctly as the following: 01 NVARCHARFIELD. 49 NVARCHARFIELD-L PIC S9(4) COMP-5. 49 NVARCHARFIELD-V PIC N(100) USAGE NATIONAL. Use Level 49 for VARCHARs By default, OpenESQL Assistant generates a host variable as a PIC X(n) field for VARCHAR columns. When data is mapped to the host variable, it is null terminated. However, you can set OpenESQL Assistant to generate the host variable with two level-49 variables; one for the length of the data mapped and one for the actual text data. To enable Le

Problem: Running Windows XP (either Professional or Home Edition) with Service Pack 1 can cause system slowdowns that impact your AcuCOBOL-GT system.For more information, refer to the Microsoft Knowledge Base article: Programs Run Slower After You Install Windows XP SP-1. Resolution: Service Pack 2 contains the fix. Install SP2 or higher. Windows, Performance, slow Date: Name: Description of change: Date: Name: Description of change: Old KB# 14861

The attempt to load XFDs into the system catalog resulted in the message xfd cannot be loaded. Problem: When trying to load XFDs into the system catalog using the addfile.bat batch file, the load failed and I encountered the error xfd cannot be loaded. Resolution: This error message occurs when entering the name of the XFD with the .xfd extension in the batch file. To the load the XFD into the system catalog correctly, type addfile FileName instead of addfile FileName.xfd. System catalog, XFD, addfile Date: Name: Description of change: Date: Name: Description of change: Old KB# 14860

This article describes the reasons and the workaround when C$XML causes a runtime crash with some XML comments. Problem: With some types of comments (in particular, those that end with a newline, as below) would cause the runtime to crash during XML parsing. The type of XML comment that would cause the failure is as follows: <-- This is a comment--> Resolution: This problem was fixed by ecn-3939 in version 8.1.2; but there is a workaround for previous versions which is to modify the XML comments to not end with a newline: <-- This is a comment --> Incident Number: 2288712 Old KB# 14874

This article provides sample COBOL programs that demonstrate how threads interact with other threads by sending messages to stop processing. Problem: Heavy processing inside of an application can slow it down significantly, for example when a grid is populated by a large number of records or when many copying files. Resolution: Use the statements SEND MESSAGE, RECEIVE MESSAGE FROM THREAD, and WAIT FOR THREAD to stop processing if necessary. The attached two COBOL programs show how to use these statements in order to provide the end user the opportunity to terminate processing. Old KB# 14871

This article explains how to fix The system cannot find the path specified error message while compiling a program from AcuBench. Problem: In some rare occasions having pathnames containing spaces in the settings for an AcuBench project, at compiling time we would get the error message: The system cannot find the path specified Resolution: This can be fixed enclosing in quotes the whole path name of the FILE_PREFIX or/and ACUPATH environment variables. Incident Number: 2358220 Old KB# 14878

This article explains the different available choices to deploy a .NET assembly that is called by runtime. Problem: .NET assemblies that are used by a COBOL application can be deployed. Resolution: There are different ways to deploy a .NET assembly: The assemblies can be located in the same directory where runtime is stored or listed in the local machine GAC (Global Assembly Cache). The assemblies can be stored in a personal directory, declaring its path in the FILE-PATH property of CREATE and DISPLAY statements. For example: create "@PasGenProx" namespace is "PasGenProxNS" class-name is "PasswordGeneratorService" file-path is "PasGenPath.xml" handle in hPassGenrator The file declared in the FILE-PATH, PasGenPath.xml, contains these lines: <?xml version="1.0" encoding="utf-8" ?> <FILESPEC> <Assembly>PasGe

This article explains how to create the two directories Microsoft.VC80.MFC and Microsoft.VC80.CRT containing C libraries in order to move the AcuCOBOL-GT bin from its original location. Problem: AcuCOBOL-GT products require Microsoft Visual C libraries to run correctly. Original setup used to install these libraries directly in C:\\Acucorp\\AcucblXXX\\AcuGT\\bin directory. Since the release of version 8.0.0, these C libraries must be located in C:\\WINDOWS\\WinSxS and are strictly connected to the directory in which Acu products have been installed. This means that moving the bin directory from the original path can cause runtime to not start properly. This is a big issue for developers who want to create their own installer and for who is used to locate runtime in a shared directory over a network. Resolution: This may be solved in two ways. Download the Microsoft Visual C 2005 Redistributable Package (x86) from Microsoft's web site.For this solution

Sometimes it is necessary to make the process-ID (PID) available to the program. This article describes several ways to do so. Problem: There are several ways to read the process-ID. Some of them are provided by Micro Focus within the Runtime-System, but they do not work in all versions. Resolution: Version 6 and before: Process-id cannot be read. Versions 7 and 8: Use the C$GETPID library routine. This routine is documented In the ACUCOBOL-GT Appendices manual, Appendix I. Note: When called from a non-UNIX runtime, C$GETPID returns a PROCESS-ID of "0". This behavior should not be used for system identification. Use ACCEPT ... FROM SYSTEM-INFO instead (see the ACUCOBOL-GT Reference Guide, Chapter 6). Summary: Version 7 can only read on a Unix-RT, Version 8 from Unix or Windows. Other workarounds to read the PID: set environment "dll-convention" to "1" call "kernel32.dll" c

This article describes the Perform Stack Overflow error message and provides a resolution to the associated problem. Problem: During a program run, the error message Perform Stack Overflow occurred. Resolution: This error message normally indicates that an AcuCOBOL-GT program exceeded the number of levels PERFORM statements can be nested within paragraphs or sections. A PERFORM statement is nested if the statement contains a PERFORM statement against another paragraph/section. This error can occur if a PERFORM statement did not exit properly. By default, the amount of nesting allowed by the runtime is set to 128. That is, 128 PERFORM againstg a paragraph/section that contains a PERFORM statement against another paragraph/section. This value can be increased by setting the runtime variable PERFORM_STACK to a higher value in the configuration file. If a paragraph/section is not exited correctly, the perform stack will not clear down properly. Normally the end of

This article explains that under certain circumstances the error 9d,104 can occur when running AcuServer. Problem: Why does an AcuServer error 9d,104 occur when running AcuServer? Resolution: An AcuServer error 9d,104 means that the client can't find the TCP/IP layer (sockets). If this happens in the middle of a run instance and during this runtime's execution the AcuServer was killed and restarted, then this error will occur. This can be fixed by using config variable C$DISCONNECT (since version 5.2.1). This issue can also occur because at some point the Linux kernel goes into a busy loop, blocking all executables from running (including the runtime and acuserver). During this looping, the AcuServer socket times out and drops the connection, causing the AcuConnect runtime to return the error to the client runtime. This is a problem with the Linux kernel, and not with the software. To resolve this, you can ignore such time lags (sometimes the runtime c

This article explains how to resolve an installation failure that is the result of an error from SetMFFM. Problem: The Relativity Data Manager and Data Server installer can fail with the following message: Operating System Error 0x2 (The system cannot find the file specified.): SetMFFM failed. This error will cause the installer to terminate. It is the result of the installer examining the registry and finding a Micro Focus Net Express entry. The installer will then attempt to verify that the registry entry for the Micro Focus file manager is correct by locating the physical file that is referenced. This verification is performed so that the installer can "pre-check" the Micro Focus file manager check box during the install. Resolution: To resolve this issue, you will need to temporarily remove the Micro Focus registry entries during the Relativity installation. Below are the steps to this procedure: Start the Windows Registry utility (regedit.exe)

This article explains how to resolve an Index File Recovery Utility 24,02 COBOL I/O Error. Problem: When using the RM/COBOL Index File Recovery Utility with a large file, it can fail with a COBOL I/O Error 24,02. This error indicates that there is not enough room left to write to the file. How is this resolved? Resolution: This error is caused by the fact that the Index File Recovery Utility opens index files in binary sequential mode. Therefore, in order to resolve this issue, you will need to create a configuration file that enables the use of large sequential files (over 2 GB). The steps to create the configuration file are as follows: Create a text file named runcobol.cfg in the same directory as the Runtime executable (runcobol). Add the following configuration record: RUN-SEQ-FILES USE-LARGE-FILE-LOCK-LIMIT=YES Save the file. The configuration file will be loaded automatically and will allow you to successfully recover your index file. Inc

This article explains the difference between file status 37 and 9/37. Problem: File status 37 is "An OPEN operation has been tried on a file which does not support the open mode specified in the OPEN statement." File status 9/37 is RTS error 37, "File Access Denied". How do you distinguish between the two? Resolution: File status 37 consists of the characters "3" and "7" (hexadecimal 3937). File status 9/37 is the characters "9" and "7" (hexadecimal 3937). Note: There is no file status "97" with which to confuse the latter. File status 37 is usually a programming error, such as OPEN EXTEND of an indexed file. File status 9/37 is usually a run-time error caused by a conflict between file and/or directory permissions and user access rights. Old KB# 14888

This article explains an undefined terminal 191 error when running a job in the background. Problem: When running a job in the background we receive the error 191 (Terminal Type Not Defined) returned. Why is this? Resolution: On UNIX when running a job in the background there isn’t a terminal present, so you cannot executes any COBOL DISPLAY statements. If the COBOL program does not contain any DISPLAY statements then remove the CONSOLE IS CRT statement from the ENVIRONMENT DIVISION. The CRT clause causes the runtime to attempt to initialization a terminal. Old KB# 14837

This article explains that the addition of support for Java 1.6 in Websync 4 requires the version of AIX to be updated. Problem: After installation of Server Express 5.1 WS4 on AIX 5.3, the following error occurs when compiling: rtld: 0712-001 Symbol __pthread was referenced from module cobchecker32(), but a runtime definition of the symbol was not found. Resolution: As a result of new support for Java 1.6, the reference environment on AIX has been changed. In order to use Server Express 5.1 WS4 on AIX 5.3 users must upgrade their operating system version to AIX 5.3 TL10. Old KB# 14831

This article contains information on how to resolve a COBOL procedure error 213 when loading a non-Cobol subprogram library. Problem: When loading a non-COBOL (C or C ) subprogram library with the RM/COBOL Runtime, you receive a COBOL Procedure error 213. Resolution: This error normally occurs when the RM/COBOL Runtime is unable to locate the non-COBOL library’s dependent modules. The Runtime relies upon the operating system to load and locate dependent modules. Therefore you must properly configure your operating system’s environment in order to located dependent modules. The following is a list of operating systems and their dependent module search method. Windows: - PATH environment variable and the current working directory. AIX: - LIBPATH and /usr/local/lib HP-UX: - SHLIB_PATH and /usr/local/lib Intel UNIX System V Release 4, Linux, SCO OpenServer 5, SCO System V Release 5 (UnixWare 7.1.1 or later and SCO OpenServer 6), and Sun Solaris SPARC an

This article explains how to verify the status of an EnterpriseLink migrate operation. Problem: Prior to EnterpriseLink v5.0 WS12, there was no log that documented the status of a migrate operation. How is this done? Resolution: With version 5.0 WS12 and higher you can now view the complete status of the migrate command in a new migrate.log file which will be located in your EnterpriseLink\\Logs directory. Old KB# 14840#Rumba#EnterpriseLink

This article will explain how to speed up the EnterpriseLink Pattern Matching process. Problem: It can take a long time for EnterpriseLink to find a page in the repository if it has to go through its Tertiary Matching process. Is this also true if you have multiple screens with page transitions? Resolution: If you do not need to have EnterpriseLink use the tertiary matching process, there is now a way to disable it in EnterpriseLink version 5.0 WebSync13. In the Admin Page, under Configuration/Pattern Matching, there is a new checkbox called “Disable Tertiary Pattern Matching” which will completely bypass this step for you. Old KB# 14842#Rumba#EnterpriseLink

This article explains what to do if Java Errors ocurr when trying to start EnterpriseLink Loader. Problem: I am getting errors when trying to start the EnterpriseLink Loader. The following errors might appear in the java console window: java.lang.NoClassDefFoundError Resolution: Make sure that you have a dot “.” (which stands for the current directory) in your CLASSPATH environment variable. For example: .;c:\\dir1\\dir2:c:\\dir3\\dir4 Old KB# 14843#Rumba#EnterpriseLink