Rocket® COBOL

Problem:When trying to marshall an empty wide string : BAD_PARAM ErrorResolution: Product Name: Visibroker Product Version: VBE 65 Product Component: ORB Platform/OS Version: NA Description: When you run the client, when trying to marshall an empty wide string (not a null string but a one length character string with only 0x00), it may fail with exception: CORBA::BAD_PARAM error. With BES 5.2, it works fine. Answer/Solution: Please issue -Dvbroker.orb.nullstring=true on both the Server and Client side. So CORBA::BAD_PARAM is not thrown. There should not be any impact as long as the client and server tries to transmit a null strings. Please note that if CORBA application do not expect NULL strings then it tries to do some thing erroneous, in which you must add additional checks. Old KB# 15196#ApplicationMiddleware#archive

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

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#

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

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

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

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

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

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

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

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