Rocket® COBOL

This article explains how to use the facilities provided for tracing file operations. Problem: Is it possible to know the sequence of all I-O verbs of all data files? When the application runs first time, we're not having any problem, but the second time, a file-status is displayed. Resolution: The default filename for the File Handler configuration file is extfh.cfg but you can use a different filename by setting the EXTFH environment variable. For example: set EXTFH=/mydir/test.cfg sets the filename to /mydir/test.cfg It is necessary to use the File Handler configuration parameters TRACE, TRACEFILEEXTEND, TRACEFILENAME [XFH-DEFAULT] TRACE=ON TRACEFILENAME=/trace/XHFTRACE.XFH TRACEFILEEXTEND=ON The name of the file must be XHFTRACE.XFH. The Trace Player, cobfhrepro{n} must be used to read the tracing information file. If the application runs in 64 mode the commands are cobfhrepro3 or cobfhrepro364. If the application runs in 32 mode

When the 64-bit Windows Runtime makes a call to AcuBenchPrint.dll it crashes with “Program missing or inaccessible”. Problem: The application deployment includes AcuBenchPrint.dll which is used to preview and print the html reports from the ACUCOBOL-GT program. This all worked fine with the 32-bit Windows Runtime, however with the 64-bit Windows Runtime the first call to AcuBenchPrint.dll causes a crash with this error:AcuBenchPrint.dll: Program missing or inaccessible. The problem is that AcuBenchPrint.dll is a 32-bit dll so the 64-bit Runtime will not be able to load it. Up to, and including, version 8.1.2 there is no 64-bit AcuBenchPrint.dll. Resolution: There is now a 64-bit version of AcuBenchPrint.dll which is attached to this article. The workaround is to use the 32-bit Runtime which is found in the Program Files (x86) branch. Incident Number: 2433249 AcuBenchPrint64.zipDate: Name: Description of change: Date: Name: Description of change: Attachments AcuBen

This article discusses the slow performance when using AcuServer over a LAN. Problem: We are experiencing slow performance when using AcuServer while using a high speed network (FIOS). Other products seem to be running a lot faster. Equipment was replaced and tested and there was no improvement in the performance. What is happening? Resolution: It was determined that the ISP was indentifying the traffic as a bit torrent. The packet analyzer software being used by the ISP was identifying the traffic between the runtime at the remote store and AcuServer at the main store as torrent data. Due to the amount of bandwidth that was being used for torrents on the network, the ISP had implemented a policy to throttle all torrent traffic from 8am to 5pm so their business customers could take advantage of the high speed FiOS Internet connections. The ISP removed the torrent restriction from the IP addresses used by the stores and performance was improved. Old KB#

Created On:  15 March 2012 Problem: How to install License Server 4.0 with IIS 7.0 or IIS 7.5 on Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2? Resolution: Each operating system comes with its own version of Internet Information Services (IIS). Windows Vista and Windows Server 2008 come with IIS 7.0 while Windows 7 and Windows Server 2008 R2 come with IIS 7.5, which has improved and more features.   IIS 7.x is in fact a complete redesign and rewrite of IIS, so the following instructions on how to install License Server 4.0 are completely different from the ones made for IIS 6.0 running on Windows Server 2003.   1)      Install MF License Server 4.0: Install License Server in a different directory other than the default "Program Files" or “Program Files (x86)” directory, as there is an access restriction which causes problems in the software. Consider installing License Server in C:\\LS4 Note: If the f

This article explains why an error occurs when re-installing Server Express or Server for COBOL version 5.x and above using the install script located in $COBDIR. Problem: When re-installing Server Express or Server for COBOL version 5.x using the install script located in $COBDIR, the following error is returned: Install has already been run against this product directory, this is not a valid operation. Installation aborted. Why is this? Resolution: During the installation of the product, the install script set a number of options. This warning has been implemented as there are certain options during the install that it are now unsafe to repeat. It is quicker and safer to remove the product completely and start the install over using the extracted product. Incident Number: 2428746 Old KB# 14946

This article provides information regarding the Electronic Software Delivery emails. Problem: If you opt to receive your Liant license and product media electronically, you will receive multiple emails from Micro Focus Distribution. This article contains information regarding the content of these emails. Resolution: License Certificate Emails: You will receive one license certificate email for each product that you have purchased. For example, if you purchase the RM/COBOL Development System and a Relativity Data Server, then, you will receive two license certificate emails. The license certificate email will contain an attached license certificate file (*.lic). This file should be saved onto the machine targeted for installation. Product Media Download Emails: Product Media Download Emails contain links to download installation media and installation guides for your purchased product. You will receiv

Compiler flags 801-S External Compiler Module message with DB0109 on host variables that are defined in Linkage Section. Problem: HCO has been provided with Net Express for a certain time, but the DB2 pre-compiler never applied some of the "mainframe emulation" rules until HotFixes release for Net Express 5 WrapPack 3. Host variables are now limited to where they can be defined when pre-compiled with HCO turned on. That is why host variables defined in LINKAGE SECTION are now flagged with the following error messages: * 801-S************ **** External Compiler Module message** DB0109 Data-Item-Name is not a data item. Resolution: If the mainframe emulation is not necessary, it can be turned off by setting environment variable MFHCO=NO. Incident Number: 2355317 Old KB# 14910

This article describes a method of generating a memory hex dump from the runtime debugger. Problem: There are times when it would be desirable to have a hex dump generated to assist with debugging and troubleshooting, but there is no documented method of obtaining a memory hex dump. Resolution: There is an undocumented feature in the ACUCOBOL-GT runtime that facilitates the generation of a memory hex dump. This feature is available on Windows and UNIX. To obtain the hex dump, type “x” at the debugger prompt followed by a space and the name of the dump file. The file will contain a snap shot of the hex values in memory at the time the command is executed. Attached to this article is a sample hex dump from running our sample program newftest.cbl. Old KB# 14908

Problem:DB Schema (Tables) Definitions Used for Naming ServiceResolution: Product Name: Visibroker Product Version: All Product Component: Naming Service Platform/OS Version: All Description: List?the different tables used?by Naming Service and their purpose. Answer/Solution: There are 4 tables that are created by Visibroker for Naming Service The tables are as follows: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> VBINS_NAMEMASTER_CTX_TBL ( CTX_INDEX INTEGER, CTX_TYPE INTEGER ); This table stores the information for each context that gets created. Each context gets assigned a unique index value. Column CTX_INDEX stores this unique index value. Column CTX_TYPE stores the type of the context such as root context, normal context, or cluster context type. A new row gets added to the VBINS_NAMEMASTER_CTX_TBL every time a new context gets created. >>>>>>>>>>&

Problem:OTS migration HeuristicRollbackException: exception org.omg.CosTransactions.HeuristicHazardResolution: Product Name: BES6.6 and VBE7.0 Product Version: 6.6 and 7.0 Product Component: OTS Platform/OS Version: All Problem Description: Customer migrating OTS service from BES6.5 to BES 6.6 (VBE7.0) version, throwing a following exception: javax.transaction.HeuristicRollbackException: exception org.omg.CosTransactions.HeuristicHazard While the same application used to work well in the BES6.5 environment why it is broken in the BES6.6 version? Answer/Solution: There was some changes in transaction layer from 6.x to the 7.0 version, so by setting vbroker.its.its6xmode=true in the vroker.properties, would enable the old behaviour to be retained in the 7.0 version. Hence the exception would go away and the application should start up fine without any exception. Please refer VBE7.0 release notes to find more information on the OTS changes made in the 7.0. Old KB# 15195#

Problem:Documentation Error - Erroreounously stated that "GK Load Metrics data is available on request"Resolution: Documentation Error- Erroreounously stated that "GK Load Metrics data is available on request" Product/ Environment Description Product/Component Name: Borland Enterprise Server Version: 6.5 and earlier Component: Gatekeeper Platform: All Documentation Error Inappropriate statement included in Help Documentation provided with BES versions 6.5 and earlier. For example following is the statement from Gatekeeper performance related documentation as stated on page http://info.borland.com/techpubs/bes/v6/html_books/vb_gate/gkscenario.html. Cite: "GateKeeper stress/load metrics? The ORB performance study is conducted by the Borland Quality Assurance department, therefore comprehensive statistics can be obtained on special request either from Borland"s Professional Services Organization, Customer Support, or Quality Assurance. The information is available for specific p

Problem:How to add a meaningful description for BES65 Windows ServiceResolution: Product Name: AppServer Product Version: 6.5 Product Component: scu Platform/OS Version: Windows XP Problem Description: How to amend/edit the service "description" when the customer running a BES65/BAS66 as a Windows Service in the Windows Control panel -> Administrative Tools -> Services -> BES65 (properties of BES65 Service) Answer/Solution: When the user starts the BES as a windows service by running >scu -install BES65, this would start a BES as the Windows Services but however the customer cannot amend the service description as the way they want. In order to have a more meanful service description, go to regedit HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\BES65, adding a string value "Description", with the description you want to put it then it would appear in the Control panel BES service description. I"ve attached two screen shots to show you how it looks l

This article explains the Service Error 5 message when starting an AcuODBC service. Problem: After installing and attempting to start the AcuODBC service an error message “Service Error 5” is displayed. Why is this? Resolution: According to the System Errors list from Microsoft an error 5 means "Access is denied". This error is a permission problem. Since Windows service manager uses system permissions, the directory where AcuODBC is located should be enabled for system account. The issue can be resolved by changing permissions on Acucobol directory to allow full access for Everyone. AcuODBC runs under the (implied) local SYSTEM user. Another possible solution is to uninstall, and reinstall the service. During installation, there are registry entries that are made regarding locations of the AcuODBC executables that will be deleted then correctly made during re-installation. Incident Number: 2428262 Old KB# 14897

This article explains how to show that testing has been performed and produce a report to illustrate the extent of test coverage. Problem: Development teams often need to show that they have performed testing which has covered all logical paths through a program. How is this done? Resolution: Using the test coverage utility, they can produce a report to illustrate the extent of test coverage, and can promote this report along with the source code at the various stages of the development lifecycle. While a program is running in test coverage mode, code execution is logged for each program and sub-program that has been compiled with the TESTCOVER directive set. The information stored in the results file depends on how you configure test coverage. As the results file is a binary file, it has to be formatted to produce a text or HTML report file. You can create a report file using the reporting utility

This article describes how to obtain the correct Microsoft assemblies for use with the Version 8.1.2 ACUCOBOL-GT Runtime for Windows. Problem: The application is deployed with a copy of the ACUCOBOL-GT bin directory included, or the Runtime was installed on a server and the client PCs map a drive to the bin directory to execute it. This can result in an error when the client PC is missing the Microsoft C Redistributables. With Version 8.1.0, adding the two assemblies, Microsoft.VC80.CRT and Microsoft.VC80.MFC enabled the Runtime to execute in this fashion without error. However those same assemblies do not work with newly released Version 8.1.2. Resolution: It is likely that Microsoft updated those two assemblies or parts of them after the 8.1.0 release. The 8.1.2 release was built with, and depends on, different specific versions of those assemblies, or their parts. Attached is an archive, 8.1.2RedistFiles.zip, containing the two assemblies for u

This article addresses how to solve the *** File system error value = 11 ****** Micro Focus Lock table missing ***>>>file status = 9D,11 when updating to Acu4GL/MSSQL 8.1.2 . Problem: Updating from any pre 8.1.2 version of Acu4GL for MSSQL, we get the following error the very first time we try to access a MSSQL data base that it was working with an earlier version. *** File system error value = 11 ****** Micro Focus Lock table missing ***>>>file status = 9D,11 The reason is that with the purpose to standardize Data Base Connectors and Acu4GL products; now Acu4GL is looking for a new locking table named AcuLocks1, instead of the former AcuLocks. Resolution: Repeat steps 2, 3 and 4 mentioned in our Acu4GL User's Guide > Version 8.1.2 > Appendix B: Acu4GL for Microsoft SQL Server Information > B.2 Installation and Setup > B.2.1 Installing on a Client Machine. A summary of

This article explains what to do if you get an error after a reboot saying the EnterpriseLink Packet Driver fails to start. Problem: The following error appears in the Windows Event Viewer from the Service Control Manager:The EnterpriseLink Packet Driver service failed to start due to the following error:The system cannot open the file. Resolution: The EnterpriseLink Packet Driver is not required under Windows 2003 Server. You can safely remove it from the registry to keep the message from reappearing each reboot. From the Windows Command Prompt, type regedit. Open the key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services. Scroll the window until you see eltcpacket. Right-Click with the mouse on eltcpacket and select Delete Key. The packet driver will be removed from your Windows 2003 system. This is not required for correct operation of the EnterpriseLink Cluster Server.

In the AcuBench Screen Designer the screen background color is set to dark gray, but comes out black at runtime. Problem: The screen was built in AcuBench using the Screen Designer. The background color was set to dark gray (and looks dark gray in the Screen Designer) but at runtime it is black. Resolution: There is a problem with the AcuBench Screen Designer implementing the gray/dark gray colors which is resolved in version 8.1.2. For earlier versions there is a fairly easy workaround involving modifying the color palette. Here's how: In the screen's Color property select a background color other than gray or dark gray, use dark blue for this example (make sure it is a color that is not used anywhere else in the application). Right click on the screen in the Screen Designer and select Change Color Palette. In the Color dialog select the dark gray color in the Basic colors section. In the Screen designer color palette: s

This article provides details for setting up an AcuXDBC database as a MSSQL Linked Server. Problem: There is a need to access the AcuXDBC database through MSSQL Server. How is that accomplished? Resolution: One method is to import the data using the MSSQL Server Data Transformation Services (DTS). However, the preferred method is to set up a Linked Server, which provides access to the live data rather than the snapshot created by importing. Important: Restart MSSQL Server after installing/configuring AcuXDBC. This is to ensure that MSSQL picks up the correct environment for AcuXDBC, specifically, the GENESIS_HOME and PATH settings. In some cases rebooting the server may be necessary. After installing and configuring AcuXDBC and/or AcuXDBC Server and setting up a system DSN, set up the MSSQL Linked Server as follows: (These instructions are specific to MSSQL Server 2005 and may be slightly different for other versions. The basics are the same

This article provides information on how to set the directories where the RM/COBOL Runtime will search for COBOL object, data, and library files. Problem: When deploying an application it is sometimes necessary to place COBOL objects, data, and library files in different directories. Since, by default, the Runtime only searches the current working directory for files, you will need to configure the file search path (RUNPATH) in order to instruct the Runtime to search alternate directory paths. Resolution: There are three ways to configure the RUNPATH for the Runtime. UNIX/WINDOWS: Create an environment variable named "RUNPATH", and, set it equal to the directory path(s) where your files are located. On Windows platforms, separate the directory paths with a semicolon (;). On Unix platforms separate the directory paths with a colon (:). WINDOWS ONLY: Create a synonym named RUNPATH using the RM/CO

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