Rocket® COBOL

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

Problem:Adding a New Task to a Line ItemResolution: Product Name: Tempo Product Version:6.x/Tempo 2007 Product Component: Task Platform/OS Version: All Question: How do I add a New Task to a Line Item? Answer: (a). Adding a New Task to a Line Item: Double-click the?the relevant Item (e.g. Inventory Optimization System) In the "Take Action" section, select "Add a new Task:" Complete the Task details as required. Note: In this example, user admin is logged in, and assigns the task to user Carl CIO: To view this Task (and any other Tasks created),right-click on the Item, and choose "Work Breakdown Structure:" ..which displays as follows: Author: Bridget McGilloway Old KB# 14970

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 explains why an RTS 166 Error occurs when COBOL CALL an ENTRY point that is defined in the main source file. Problem: The main source file pmain.cbl is as follows: PROGRAM-ID. PMAIN. PROCEDURE DIVISION. CALL “sp01”. STOP RUN. ENTRY “sp02”. EXIT PROGRAM. The called source file sp01.cbl is as follows: PROGRAM-ID. SP01. PROCEDURE DIVISION. CALL “sp02”. If the application runs in Intermediate Code, or if the compiler directive RECURSECHECK is used to generate ( -N RECURSECHECK ), the error 166 is displayed. Resolution: In fact , if you want to have a recursive environment , you can down this as follows and compile again: PROGRAM-ID. PMAIN IS RECURSIVE . Or PROGRAM-ID. PMAIN. LOCAL-STORAGE SECTION. PROCEDURE DIVISION. However , be aware of the initial status of all data involved in that case at run time , refer to Pro

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 resolves an RTS 173 error that occurs on the application name. Problem: When attempting to animate a 64-bit application from the Net Express command line using the following command mfnetx /debug:progname.exe an RTS error 173 occurs on the application name. Resolution: This is because a new switch “debug64” has been added to the mfnetx command and needs to be used whenever a 64-bit application is to be loaded. Use the following when animating a 64-bit application: mfnetx /debug64:progname.exe Incident Number: 2434379 Old KB# 14914

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: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 extract error message text from an OLE Exception object. Problem: We need a way to extract text from an OLE Exception object. A Net Express program reads an Excel spreadsheet using OLE. It works great until it encounters an error of some sort. The exception manager is set up to do a call back. The call back works and displays the Excel error message. The question is instead of displaying the error message, how can the error text be moved to a COBOL data item? The following is the callback code which is copied from a Net Express example: callback section. entry "onOleException" using by reference lnkErrorObject by reference lnkErrorNumber by reference lnkErrorText. display "Excel had returned an error..." display "The COBOL exception number was: " lnkErrorNumber invoke lnkErrorObject "display" display "

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

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

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

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

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

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