Rocket® RM/COBOL

Created On:  30 June 2010 Problem: While installing the Relativity Data Client version 12 you receive the following error:Activation context generation failed for "C:\\Program Files (x86)\\Liant\\Relativityv12\\reldbsrv.dll".Dependent Assembly Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053" could not be found. Please use sxstrace.exe for detailed diagnosis. Resolution: The Relativity Data Client version 12 requires the Microsoft Visual C 2008 redistributables.  They can be downloaded from here:http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en Incident #2462023 Old KB# 31337

Created On:  29 June 2010 Problem: I need to uninstall a Liant product on a Windows machine. However, I need to perform the uninstall silently without using the GUI uninstaller. How is this done? Resolution: In order to uninstall RM/COBOL v12.02 from a machine you can use the Windows Instrumentation command-line interface (WMIC).  The Windows Instrumentation command-line interface is available on any PC running Windows XP Professional, or later.Below is the syntax for two WMIC functions that are necessary for uninstalling products.-------------------------------------To get a list of installed products:wmic product get nameTo uninstall a product:wmic product where name="application name" call uninstall /nointeractiveWhere, application name, is the name of the program you wish to uninstall (use the exact name provided by the previously generated list).-------------------------------------The following examples demonstrate how to use the Windows Instrumentati

Created On:  16 June 2010 Problem: I need a display that is larger than the default 80 columns by 25 rows. Resolution: You can use the TERM-ATTR "COLUMNS" and "ROWS" configuration keywords to increase the number of columns and rows that the Runtime will display on the terminal.  These configuration records will need to be added to your RM/COBOL Runtime configuration file or placed in a new RM/COBOL configuration file.For example, the following record in your configuration file will yield a screen that is 100 columns wide with 30 rows: TERM-ATTR COLUMNS=100 ROWS=30For more information regarding terminal configuration, please see "Chapter 10: Configuration" in the RM/COBOL User's Guide.  You can obtain the RM/COBOL User's Guide from our web site at:  http://supportline.microfocus.com/Documentation/RMCobol.asp Incident #2457869 Old KB# 31190

Created On:  07 June 2010 Problem: The following error is encountered when attempting to install or upgrade Web-to-Host 6.0:“Error 2753.The File 'nmservicemanager.exe.2E19ED1F_0A9B_43F4_BA8B_60F8E67C8891' is not marked for installation.” Resolution: This problem is encountered when a previous installation of Web-to-Host software on the workstation cannot be uninstalled. Please perform the following steps in order to resolve the issue: • Download and install Microsoft Windows Installer Cleanup Utility on the workstation.• Close all open Web-to-Host sessions.• From the program list, launch Microsoft Windows Installer Cleanup Utility • Remove all detected versions of Web-to-host software and reboot the workstation.• Launch the session to fire off web-to-host install again Microsoft Windows installer utility download link: http://support.microsoft.com/kb/290301/en-us Incident #2456965 Old KB# 31182#Rumba#OnWeb#Web-to-Host

Created On:  15 June 2010 Problem: I am using an ODBC enabled tool that requires an ODBC version x compliant driver.  What version of ODBC does Relativity support? Resolution: What version of ODBC does Relativity support?Relativity is ODBC 2.0 compliant.  However, it does implement some SQL grammar and scalar functions from later versions of the ODBC standard.The following SQL statements are supported by Relativity:CREATE INDEXCREATE TABLECREATE VIEWDELETEDROP TABLEDROP VIEWINSERTSELECTUPDATEThe following SQL clauses and predicates are also supported:AVGCOUNTMAXMINSUMBETWEENHAVINGEXISTSINUNIONUNION ALLGROUP BYORDER BYAdditionally the following ODBC scalar functions are supported:CONCATCONVERTCURDATECURTIMEDATABASEDAYOFMONTHDAYOFWEEKIFLCASELEFTLENGTHLOCATELTRIMMODMONTHNULLQUARTERRIGHTRTRIMSUBSTRINGUCASEUSERYEARFor more information regarding Relativity's supported SQL grammar, please see the Relativity Data Client help file.For detailed information about the arg

  Problem: My current index files are not file version 4. Should I upgrade these index files to file version 4?   Resolution: By upgrading to file version 4 you can take advantage of two very important enhancements. 1.  The ability to create large files (greater than 2GB)2.  Atomic I/O (eliminates most file corruption)Large File SupportThere are several steps to adding support for large files for existing index files: 1. The first step is to make sure that the operating system supports the creation of files greater than 2 GB. This may involve changing the file system, a kernel setting, or even the ulimit associated with a user account shell. Your systems support person will need to accomplish this as each operating system may handle it differently.2. Next, edit the default configuration file (runcobol.cfg) located in the RM/COBOL installation directory (usually /usr/rmcobol). Add the following two records to that file:RUN-FILES-ATTR LARGE-FILE-LOCK-LIMIT=

Created On:  14 June 2010 Problem: I am unable to connect more than ten WOW Thin Client sessions to my Linux server. Resolution: This issue is caused by a change to the xinetd service daemon defaults on some Linux distributions.The "per_source" attribute specifies the maximum number of instances allowed to a single source IP address.  On some Linux variants this default is set to a value of 10. In order to address this issue you will need to modify your "rpcplus" xinetd configuration file ( /etc/xinetd.d/rpcplus ) and add the "per_source" attribute.  For example: service rpcplusper_source  = UNLIMITEDYou will need to restart the xinetd daemon after making these changes.  Please check your Linux distribution's manuals for information on how to restart xinetd. Incident #2447770 Old KB# 31178

Created On:  2010-04-22 Problem: Customers may have file or library names that contain the “.” character in the name.  When attempting to download a library name that contains the “.” character the following SQL error is encountered: [Micro Focus] [RUMBA Data Access]  Syntax error or access violation. SQLSTATE   = 42961[ : The relational database is not the same as the current server.  SQLCODE=  -114.  :  Relational Database XXXX                 SSSSSSSS is not the same as server.    In the above example error XXXX would be the characters preceding the “.” character in the library name and the SSSSSSSS would be the system name. If attempting to download both a file name and library name that contain the “.” character the following SQL error is encountered: [Micro Focus] [RUMBA Data Access]  Syntax error or access violation. SQLSTATE&n

Created On:  2009-04-24 Problem: Does RUMBA 8 support a Single Sign-On connection to an iSeries via Kerberos? Resolution: Yes, with its support for Kerberos, RUMBA 8 provides SSO capabilities for AS/400 and iSeries offering streamlined client authentication which reduces administrative costs.  To enable SSO for the AS400 Display follow these steps: 1.  Bring up the AS400 Display and choose Connection/Configure.2.  On the General tab, choose TN5250 and fill in the appropriate destination information3.  On the Security tab, click the Security Button4. Check the Kerberos box under Active Security Protocols 5. Choose Ok and you may now Connect Please note that there has been a change in Kerberos authentication on Windows 7 and Windows 2008 Server R2 requiring configuration on the client side. See http://technet.microsoft.com/en-us/library/dd560670(WS.10).aspx for details. Old KB# 31074#Rumba

Created On:  2008-09-30 Problem: Under UNIX, you need to manually configure EnterpriseLink to have its Repositories reside in an ODBC Database. Resolution: You will need to download and install the 32bit ODBC drivers for the database you are trying to connect to. After that, you need to edit the env.sh file located in the Elink config directory to add any environment variables that might be needed to be able to load these ODBC drivers. For example, using the EasySoft MS-SQL ODBC Drivers on AIX, you would need to provide the LIBPATH variable pointing to the lib directories where the EasySoft shared libraries are located: LIBPATH=/usr/local/easysoft/lib:/usr/local/easysoft/unixODBC/libexport LIBPATH Add the appropriate entries in the EnterpriseLink.cfg file located in the Elink config directory.For example if using the EasySoft MS-SQL ODBC Drivers on AIX: [ODBC Drivers]SQL Server = Installed [ODBC Data Sources]ELRepository = 0SQL Server [SQL Server] Driver &nbs

Created On:  2010-04-23 Problem: When capturing screens in EnterpriseLink Loader, I am unable to navigate from field to field using the TAB key. Resolution: This is a limitation of the Loader, you must use the mouse and click on the field you want to edit. Old KB# 30985#EnterpriseLink#Rumba

Created On:  2010-02-25 Problem: The following error is encountered when attempting to execute the distribution packager utility that is packaged with Web-to-host version 6.0:“This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem.” Resolution: The Microsoft Visual C 2008 Redistributable Package (x86) is required to run this utility. To resolve this issue, download and install the Microsoft Visual C 2008 Redistributable Package (x86) from the following location:http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en   Incident #2433262 Old KB# 30924#OnWeb#Web-to-Host#Rumba

Problem:IPSec configuration for host-host communicationsResolution: Product Name: AppServer Product Version: All Product Component: TIBCO 4.4.3 Platform/OS Version: All Setting up IPSec for host-host communications between Solaris-Solaris and Solaris-Windows XP: IPsec protects IP packets by authenticating the packets, by encrypting the packets, or by doing both. IPsec is performed inside the IP module, below the application layer. Therefore, an Internet application can take advantage of IPsec while not having to configure itself to use IPsec, whereas the use of TLS/SSL or other higher-layer protocols must be incorporated into the design of applications at that level. IPsec uses the following protocols to perform various functions: A. Internet key exchange (IKE and IKEv2) to set up a security association (SA) by handling negotiation of protocols and algorithms and to generate the encryption and authentication keys to be used by IPsec. B. Authentication He

Problem:gatekeeper as root - security issueResolution: Product Name: Visibroker Product Version: VBE 65 Product Component: Gatekeeper Platform/OS Version: UNIX Description: When running the gatekeeper as root, that means the port number is below 1024 on UNIX box then you have root rights. Then, You may see that GET request on gatekeeper can expose the sensitive data where the Gatekeeper is running, which is a security issue. This security issue is not seen when used with VBJ 3.x. Answer/Solution: To fix this security issue please use the property "vbroker.se.exterior.scm.ex-hiop.servlet.orb.GET=false". Basically this property is documented under the gatekeeper properties in gatekeeper guide, but it does not document that this property can be used in such above situations. Old KB# 15197#ApplicationMiddleware#archive

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

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.

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

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

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

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