Rocket® COBOL

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

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 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 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 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 how to configure the location where target build files are created. Problem: By default when you build a project the int/gnt/exe/dll target files are created in the debug or release folders in the project directory. Is it possible to override this option? Resolution: This is configurable in the Build Types. On the main Net Express menu you use the Project / Types of build menu option. This allows you to override the directory specified. Incident Number: 2422601 Old KB# 14829

This article explains that Net Express 5.1 WS4 for Windows 7 or Server 2008 R2 requires installation of a new cut of the base Net Express 5.1 product before being applied. Problem: Net Express 5.1 has been retooled to support Windows 7 and Server 2008 R2. How does this work? Resolution: To use Net Express 5.1 WS4 on Windows 7 or Server 2008 R2, a re-cut base 5.1, or 5.1 WS1 product must be installed before applying the Websync. To use Server 5.1 WS4 on Windows 7 or Server 2008 R2, the re-cut Server 5.1 GA must be installed before applying the Websync. Once any existing 5.1 product installation has been removed, and the re-cut product installed, WS4 can be applied. Net Express 5.1 GA and Server 5.1 GA can be ordered from your Sales representative. Net Express 5.1 WS1 can be downloaded from the SupportLine website. Old KB# 14830

This article explains the return code from the runtime system for abnormal terminations. Problem: A COBOL program can end "returning numeric-value" which will put a value in the return-code special register, but the COBOL runtime system can terminate abnormally before the program ends and this statement will never be executed. For example, a run time error 114 (memory bounds error) or 173 (called program not found) will cause abnormal termination of the runtime system. What return code one will one see via "echo $?" thereafter? Resolution: If the COBOL runtime system terminates due to an error, for example, program not found, RTS 114, etc., the return code is always 255. If the runtime system terminates because the program terminates ("stop run" or top-level "goback"), the value of the return-code special register is returned. The return code can be tested in a script or from the command line with the echo command. The variable

This article explains the error 000000 000: Illegal command line when attempting to compile in Net Express 6.0. Problem: Having installed Studio Enterprise Edition 6.0 and then activated it with a stand-alone time-limited license with your 16-digit Authorization Code you may encountered error message ‘000000   000: Illegal command line’ when attempting to compile any program in Net Express 6.0.This problem is caused by an error in populating the lservrc.stn file which is found here: C:\\Program Data\\Micro Focus (on Vista/Windows Server 2008) C:\\Documents and Settings\\All Users\\Application Data\\Micro Focus (on XP). When inserting the Authorization Code into the appropriate field in the Studio Enterprise Edition 6.0 product, a hand-shaking process takes place between the client machine and Micro Focus’ license server machine. If all is well, the license server machine issues the client machine a license via the Internet in the form of a license string which is compose

This article provides CBL_OPEN_FILE Documentation clarification. Problem: When opening a file that is, or will, be greater than 4GB using CBL_OPEN_FILE, a file status 181 is returned: Invalid Parameter Error Why is this? Resolution: CBL_OPEN_FILE is used to open an existing file for byte stream operating. When using CBL_OPEN_FILE one of the parameters the routine requires is “access-mode”. The documentation shows the following valid modes: 1. Read only 2. Write only (deny-mode must be 0) 3. Read/write 64  Read/write files greater than 4GB Deny-modes are as follows: 0 Deny both read and write (exclusive) 1 Deny write 2 Deny read 3 Deny neither read nor write Device is reserved for future use (must be zero). When opening a file that is greater than 4GB it looks as if the “access-mode” should be “64”. In actuality you must also pass value 1, 2, or 3 along with the 64. The call to CBL_OPEN_FILE would look

This articles explains how to ensure a Server Express deployment and development environment is licensed properly and ready for use on HP/UX systems. Problem: In Server Express deployment and development licensing is enforced. How can you ensure that the deployment / runtime environment is licensed properly and ready for use? How can you ensure that the development environment is licensed properly and ready for use? Resolution: To ensure the Server Express deployment and development environment is licensed properly and ready for use, you can run the command Apptrack to check deployment license usage. The attached MFLicenseCheck tool will find and report the number and types of installed deployment licenses. It will also analyze deployment license usage for only Server for COBOL/Application Server. It will also report deployment license usage, generated when development licenses are installed. The attached file is for the HP/UX operating system only. To use this

This article explains why the Net Express Startup screen appears, but the IDE will not load. Problem: Net Express attempts to load the last project on startup but for some reason the IDE won't load. Does this mean it is corrupt? Resolution: It may mean the IDE is corrupt, therefore try the following: Open a Net Express Command Prompt. Go to Start > Programs > Micro Focus Net Express 5.0 > Net Express Command Prompt. At the command line enter: mfnetx /n. If this works, you probably have a corrupt project (.APP) file. If the project is corrupt, you will need to recreate your project from scratch. You may want to turn off the feature Reload files and last project on startup by performing the following: Start > Programs > Net Express > Command Prompt. Enter MFNETX /N(no project) which will bring up the Net Express IDE. Select Options > Customize IDE. Select Workspace. Disable Reload Files and Last Project on S

This article describes which processors are supported for native code Problem: Not all processors are supported for native code. To increase the performance it can be necessary under certain circumstances to determine which processor will be supported and how the code can be implemented. Resolution: ACUCOBOL-GT supports several options that cause it to generate and execute object files that contain native instructions for select families of processors. These options may not be combined with other options into a single option. For example, it is an error to specify "-nv"; you must specify "-n -v" instead. The compiler uses cblutil to produce the native-code object file. cblutil is installed in the same directory as the compiler by default. The compiler searches the execution path if it cannot find cblutil in its own directory. You run a native-code object module just like a portable-code object module. You may mix native-code obje

This article explains how to create a application with an Acu COBOL module and a Micro Focus COBOL module. Problem: We would like to use an Acu module and a Micro Focus module in the same application. How is this done? Resolution: The document attached to this article explains how to create an application with an ACUCORP module and a Micro Focus module. Prerequisites : AcuCobol-GT version 8 with shared libraries for UNIX Platforms. Server Express version 5.0 or earlier. Old KB# 14628

This article provides a sample COBOL routine to display the HEXA value of COBOL variables. Problem: How can you retrieve and display the HEXA value of COBOL variables? Resolution: The routine named HEXAutil.cbl attached to this article will sh you how to retrieve and display the HEXA value of COBOL variables. Following is a sample COBOL program: ... linkage section. 01 aCobolVar pic x ANY LENGTH. procedure division using aCobolVar.... The test program callHEXAutil calls the routine HEXAutil: working-storage section.78 HEXAUTIL value "hexautil".01 anInt pic s9(9) comp-5 value 123456789.01 aStr pic x(40) value "0123456789abcdefghijklmopqrtsuvwxyz".01 aComp-2 comp-2 value 123456789.01.01 aComp-3 pic 9(9) comp-3 value 123456789. procedure division.working-storage section.78 HEXAUTIL value "hexautil".01 anInt pic s9(9) comp-5 value 123456789.01 aStr pic x(40) value "0123456789abcdefghijklmopqrtsuvwxyz".01 aComp-2 comp

Problem: When using the compiler directive RM"ANSI" to enable support for RM/COBOL source programs the default behavior of the ACCEPT statement is to sound an audible BEEP. This is the default behaviour for RM/COBOL programs and we would like to turn it off, how can this be done? Resolution: The BEEP can be prevented in two ways: Add the NO BEEP option to the ACCEPT statement. This is tedious for large programs. Use the (currently) undocumented compiler directive RM(NOBEEP), i.e. $set RM(NOBEEP) Incident Number: 2349342 Old KB# 14613

This article provides examples on how to handle SOAP Exceptions in Web Services Client consuming Web Service deployed on Enterprise Server. Problem: It can be quite interesting to catch SOAP Exceptions and get more details about this SOAP Exception when it occurs. How is this done? Resolution: The attached sample and .zip file explain how to proceed. The sample attached will only work with a service generated by Net Express 5.1 WebSync3 or higher (Net Express 6.0). The .ZIP file attached contains: A Net Express Project that contains a sample legacy code named LEGACY from which a service of type Web Service was created with Interface Mapping toolkit (IMTK). Attachments NET-51-20090918.zip Old KB# 14624

This article explains if WS-I Basic compliant WSDL can be generated by the IMTK. Problem: Net Express is being used to create Web Services and a WSDL file is being generated.The WSDL file generated is not compliant with WS-I standards. Is there any way to generate the WSDL file so that it is WS-I compliant? Resolution: The WSDL files generated by the IMTK (Interface Mapping Toolkit) first become compliant with WS-I Basic Profile 1.0 in Net Express 5.0 GA release. The WSDL files were not compliant in any earlier releases like 4.0. Incident Number: 2155191 Old KB# 14612

This article provides an example for importing Namespaces within a COBOL project in MS Visual Studio. Problem: It is convenient to have imported namespaces in a COBOL project within MS Visual Studio so you can use classes belonging to a namespace without to specify it. How is this done? Resolution: On the COBOL project, right click, select Properties, then choose References and choose namespace(s) you would like to import. As an example, in the example code attached to this article, System.XML namespace was imported so you can directly use taking per example XmlDocument instead of System.Xml.XmlDocument leading to the COBOL .NET syntax to be lighter. A .ZIP is also attached to this article containing a Visual Studio solution with two COBOL projects: 1st project: named CobolImportNAmespaceNo and the namespace System.XML was not imported n the project 2ndproject: named CobolImportNAmespaceYes and the namespace System.XML was imported n the project