Rocket® COBOL

This article provides a matrix describing which versions of IBM DB2 are compatible with which versions of Acu4GL. Problem: Which versions of IBM DB2 are compatible with which versions of Acu4GL? Resolution: Acu4GL Version Compatible DB2 Versions 6.0 6.1, 7.1, 7.2, 8.0, 8.1 6.1.0 6.1, 7.1, 7.2, 8.0, 8.1 6.2.0.1 6.1, 7.1, 7.2, 8.0, 8.1 7.0.0 8.1, 8.2 7.2.0 8.1, 8.2 7.2.2 8.1, 8.2 8.0.0 8.1, 8.2, 9.0 Old KB# 14071

This article explains an error that occurs on AIX systems, with Server Express running in 64-bit mode. Problem: When running a COBOL program compiled to .gnt or executable, the following error occurred on an AIX system, with Server Express running in 64-bit mode: Symptom: error 114 in module "mFFH" when running a COBOL program compiled to .gnt or executable. The error 114 occurred while running an end-user application program, but could be reproduced using nearly any COBOL program, including the demonstration program pi.cbl provided with Server Express, for example: mkdir /tmp/testcd $COBDIR/demo/debugcp pi.cbl /tmp/testcd /tmp/testcob -x pi.cbl./pi The symptom did not occur when running .int code. Also, it occurred only in 64-bit mode, not 32-bit mode. Note: The mode in which Server Express is currently operating can be revealed using the cobmode command. Additionally, when attempting to debug using Animator, or using system debuggers such as &quot

The ACUCOBOL-GT Runtime halts with file status 94,10 even after increasing MAX_FILES to the maximum. Problem: When executing a particular application, the ACUCOBOL-GT Runtime halts with file status 94,10, Too many files open by the current process. The runtime configuration MAX_FILES was increased to its maximum of 32767; however the same error occurs. The application opens less than 50 files which reside on a separate server and are accessed via AcuServer. Resolution: The MAX_FILES setting was made in the Runtime configuration file. The files are being served by AcuServer which is governed by a MAX_FILES setting of its own. MAX_FILES must be set for both the Runtime and AcuServer. The solution is to stop AcuServer, add a MAX_FILES setting in the a_srvcfg configuration file, and then restart AcuServer. As noted in the MAX_FILES documentation, the operating system may limit the number of files open per process. You might need to also adjust the appr

This article explains what to do if a License Key database is unusable due to copying, restoration or tampering. Problem: What do we do when getting a "License key database unusable" error while trying to fire up the License Manager? Does this message mean the license database has become corrupted for some reason, for example copying, restoration, or tampering? Resolution: Yes, this error will ocurr if there has been a problem with the database. To circumvent the problem, take the following steps: Change directory to */*/mflmf. Type the command ./lmfgetpv k to shut down the License Manager process. Remove the directory mflmf and its contents. Change directory to $COBDIR/lmf. At the DOS command prompt type ./lmfinstall. Change directory to */*/mflmf.. Type sh mflmcmd (prompt I (capital "i") in order to install). Insert the serial number and the license key. Type mflmman to restart the License Manager process. Type./lmfgetpv to ping the License Manager in order to ve

This article explains a Load error 173 on 'cobchecker64' when compiling a COBOL program in the runtime environment. Problem: We are experiencing a Load error 173 on 'cobchecker64' when tyring to compile a COBOL program in the runtime environment: Called program file not found in drive/directory on cobchecker64 Why is this? Resolution: Ensure that the compiler product Server Express is installed on the development machine. Note: The compiler is called Server Express and the runtime product is called Server for COBOL (this latter product was also known as Application Server for Server Express in versions 4.0 and earlier of the product). Old KB# 14055

This article explains how to recover a corrupt aslmf database prior to Server Express 2.2 Service Pack. Problem: Prior to Server Express 2.2 Service Pack 2, the recovery utility aslmdbrecover was not available. How do you recover a corrupt aslmf database if you get the following message: Error Message: License Key database is corrupt The License Manager detected corruption in the license database. The license database may have been tampered with. Therefore, the License Management Facility terminated execution of the licensed product. Resolution: For Server Express 2.2 Service Pack2 onwards, you can use $COBDIR/aslmf/aslmfdbrecover. Refer to the Deployment License Management Guide, Chapter 2. Installing and Administering Micro Focus Server Licenses, Recovering from a Corrupt License Database. As aslmf uses cached data you need not stop anything. Remove or rename the /var/mfaslmf directory Go to $COBDIR su to root and run ./aslmf/aslmfinstall ( the tail end of th

This article explains the error message "LMF 010: Unable to contact License Manager". Problem: The message "LMF 010: Unable to contact License Manager" is returned when Server Express is unable to contact the License Manager. Then the License Management Facility terminates execution of the licensed product. Why is this error occurring? Resolution: Normally the License Manager runs continuously and does not require any manual intervention. It communicates through the console, reporting status and activity, and is a free-standing process which runs as a daemon. If for some reason this process terminates, you will encounter this particular error. To confirm that the License Manager is running: Log in as root. Go to the directory in which License Management Facility is installed (by default it /usr/lib/mflmf or /opt/lib/mflmf depending on the operating system. Enter the command: ./lmfgetpv In this scenario, the License Manager is probably not running (hence the error) so it is necess

This article is specific to ACUCOBOL-GT and describes how to show your own icon (as opposed to the standard icon) on the task bar when your application is executed. Problem: Your application shows the standard icon on the task bar and on the left top corner of the screens. You want to display your own icon. Resolution: In the ACUCOBOL-GT runtime configuration file, set the ICON variable to the path where the .ico file that contains a 16-bit icon for your application resides. For example: ICON c:\\test\\myicon.ico Old KB# 14108

This article is specific to ACUCOBOL-GT and describes how to deal with an Error 35 on Suse 9.1 - kernel 2.6.5. Problem: An OPEN OUTPUT statement produces an error 35, even if PATH and permissions are correctly set. The error mainly happens on the Operating System Suse 9.1 - kernel 2.6.5 (IBM POWER PC). Resolution: The error is the result of a known bug in the Suse Operating System. The provider suggests upgrading the Operating System to SLES9 Service Pack (SP) 1 or upgrading the kernel to version 2.6.9-rc4. Incident Number: 2260365 Old KB# 14107

This article explains how to recover a corrupt LMF database prior to Server Express 2.2 Service Pack 2. Problem: Prior to Server Express 2.2 Service Pack 2, the recovery utility lmfdbrecover was not available. How do you recover a corrupt LMF database if you get the following message: Micro Focus LMF - 002: The license database is corrupt. The License Manager detected corruption in the license database. The license database may have been tampered with. Therefore, the License Management Facility terminated execution of the licensed product. Resolution:For Server Express 2.2 Service Pack 2 onwards, you can use $COBDIR/lmf/lmfdbrecover. Refer to the Development System Licensing Guide, Chapter 2, Administering the License Management Facility, Recovering from a Corrupt License Database. For older products, you will have to reinstall the License Manager component to reinstate the database with the correct structure. The steps are: Determine where the live license

This article describes how to work around the fact that Microsoft Windows doesn't allow more than 68 runtime sessions at a time. Problem: acurcl appears to "hang" when users attempt to start more than 68 runtime processes at the same time using Micro Focus Thin Client version 7.2.2 on Windows 2000. Resolution: Investigation revealed that this problem is the result of a Microsoft Windows limitation. A Microsoft Knowledge Base article, #814802, describes this issue. The article provides information about modifying the registry to allow more runtimes to run.  However, this modification may adversely affect other services running on a server, so we strongly suggest that users read and understand that article before attempting to modify the registry entry. The registry entry to modify is HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Control\\Session Manager\\SubSystems and the value to modify is "Windows". The default value

Configuring the AcuXDBC DSN fails with system error code 126. Problem: While AcuXDBC appears to be working because the data from the linked tables appears in MS Access, the following error occurs when you try to configure the existing AcuXDBC DSN in the Windows ODBC Data Source Administrator:The setup routines for the Acucorp AcuXDBC ODBC driver could not be loaded due to system error code 126. Also, the Drivers tab of the Windows ODBC Data Source Administrator shows the Acucorp AcuXDBC Version and Company as Not marked. Resolution: Access can still see the data because the path to the AcuXDBC driver is stored in the registry entry for the DSN itself. That registry entry is not corrupted. However the registry entries used by the Windows ODBC Data Source Administrator are corrupted. To resolve this: Start the registry editor and navigate to HKEY_LOCAL_MACHINE > SOFTWARE > ODBC > ODBCINST.INI > Acucorp AcuXDBC. Edit the Driver and Setup keys as necessary to reflect the

This article addresses the use of "down-level licensing" for Micro Focus products, which is the practice of running applications compiled with earlier versions of software such as Net Express, on earlier versions of Application Server, but using a license for the current version of each. Problem: Does the Net Express 5.1 Application Server License support down-level licensing? For example, if a Net Express 5.1 Application Server (Server for COBOL 5.1) license is installed on a machine, is it possible to run applications compiled with Net Express 4.0 using the 4.0 Application Server running on the 5.1 Application Server License? Resolution: The Micro Focus support policy regarding the Development tool (Net Express), Application Server (Server for COBOL) and licensing is that all three must always be synchronized by release number; for example, Net Express 4.0 applications run on Application Server 4.0 with 4.0 licensing. Micro Focus does not support down

This article explains how to resolve a License Server error indicating that the License Server is unable to load a license DLL. Problem: The License Server returns an error stating that it is unable to load license DLL. When you try to rectify the LS4.arc file, you are directed to a page stating that the LS4.arc file does not exist. Resolution: Windows Security patches might cause a License Server DLL to become corrupt. Running the repair tool from "Programs and Features" or "Add or Remove Programs" should restore all original DLL files. Incident Number: 2257534 Old KB# 14099#Licensing#MainframeExpressandMFE#Enterprise

This article describes the differences between the Model 1 and Model 2 UNIX runtime licenses. Problem: Historically all UNIX runtime licences were Model 1, however from Server Express 4.0 ServicePack 1 and onwards, Model 2 licenses were issued by default to new Micro Focus customers. What is the difference between a Model 1 and a Model 2 license? Resolution: For the purposes of this article, please note that from Server Express 5.0 onwards the runtime product changed its name from 'Application Server for Server Express' to 'Server for Server Express'. Model 1 Licenses Model 1 licenses are the old form of licenses (pre Server Express 5.0). Although Model 1 licenses are no longer supplied, if you have Model 1 licenses from an earlier product, you can continue to use them with Micro Focus Server. There are three types of Model 1 licenses: Standard License - this is the normal Application Server license required to run an application. It includes the five free Applicati

This article explains what to do if a license database cannot be created and how to retrieve the correct installation with Net Express 4.0 Application Server. Problem: When removing Net Express 4.0 Application Server, and performing a manual clean of the Windows registry and installation folder, we reinstalled it onto the same server machine without typing in the serial number and license key while running the install. APPTRACK was used to complete the task, but we are receiving the message License database cannot be created. We checked that the license key fits the product. How do we get a correct installation? Check if the environment variable ASLMFNET was set erroneously, because it is intended to use ASLMFNET for local machines only, not for a networking license database on a server machine itself. Set the ASLMFNET environment variable to point to the location of the network license database, as follows: set ASLMFNET=r:\\license-db-dir Where: r: is the net

This article explains why a new license is attached to the repertory /opt/cobol/d40SP3 and not attached to /opt/cobol/d50. Problem: When I use the following script file and install a new license, it attaches to the repertory /opt/cobol/d40SP3 and not to /opt/cobol/d50. Why is this? AA=/opt/cobol/d50 export AA PATH=$AA/bin:$PATH export PATH LD_LIBRARY_PATH=$AA/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH $AA/aslmf/apptrack Resolution: The reason this is happening is because AppTrack reads the environment variable $COBDIR to define the repertory of the new license, therefore the command echo $COBDIR must display /opt/cobol/d40SP3.Old KB# 14089#COBOL#ServerExpress#Licensing#netexpress

This article explains how to resolve the Load error : file 'mfjsub' error code. Problem: How can the following error be resolved: Load error : file 'mfjsub' error code: 173, pc=0, call=1, seg=0 173 Called program file not found in drive/directory Resolution: The program mfjsub is an internal Server Express program. To ensure every Micro Focus program can be found at runtime the library path must be set correctly for the Operating system and Server Express product: AIX - LIBPATH=$COBDIR/lib:$LIBPATH HP/UX - SHLIB_PATH=$COBDIR/lib:$SHLIB_PATH all others -LD_LIBRARY_PATH=$COBDIR/lib:$LD_LIBRARY_PATH Ensure the environment variable is exported to the shell. Old KB# 14050

This article explains how to produce a core file for every error. Problem: Is it possible to produce a core file for every error? Resolution: With Server Express 4.0 ServicePack2 and Server Express 5.0, the core file can be created for every error. echo '123456 01 Z1 PIC 9(4).' > prog.cbl echo '123456 add 1 TO Z1.' >> prog.cbl cob prog.cbl echo 'set core_on_error=2' > my.cfg COBCONFIG=./my.cfg export COBCONFIG cobrun prog.int In this way a core file is created . Old KB# 14043

This article explains that the option -N FASTCALL can be used to decrease the time taken when the verb CALL is used often. Problem: In my application , the verb CALL is used very often . Is it possible to reduce the time? Resolution: Yes, the option -N FASTCALL can be used to decrease the time. However, if it is generated with -N FASTCALL, a module can't be a main program and any module called by this module must be generated with -N FASTCALL . Old KB# 14044

This article provides the ability to create a log file of License Manager activity showing users and processes. Problem: How can a License Manager activity log file be created? I would like to know the number of used development licenses and, at times, the process that uses a development license. Resolution: To achieve this, you need to: Stop the License manager by the command ./lmfgetpv k. Start the License manager by the command sh mflmman TRACE. The log file is MF-LMF.log. However, do not use this option by default, because the log file can become very large. Old KB# 14048#Licensing#ServerExpress#COBOL

This article explains that a difference in Classic versus ANSI C runtime creates linking issues. Problem: We are experiencing linking issues after upgrading to advanced versions of C/C on HP-UX. Why is this? > aCC -V aCC: HP ANSI C B3910B A.03.37 C/C advanced versions requires libCsup_v2 & libstd_v2 ldd -r libcobccsupport.sl /usr/lib/libc.2 =>     /usr/lib/libc.2 /usr/lib/libdld.2 =>     /usr/lib/libdld.2 /usr/lib/libc.2 =>     /usr/lib/libc.2 /usr/lib/libcl.2 =>     /usr/lib/libcl.2 /usr/lib/libisamstub.1 =>     /usr/lib/libisamstub.1 /usr/lib/libdld.2 =>     /usr/lib/libdld.2 /usr/lib/libm.2 =>     /usr/lib/libm.2 /usr/lib/libCsup.2 =>     /usr/lib/libCsup.2 /usr/lib/libstream.2 =>    &nbsp

The AcuThin client must be installed on the Windows client PC, but it is not available on the installation CD. Problem: The UNIX server products were installed from an archive downloaded from production. To install the AcuThin client piece, you need access to the atcinst.exe file. This file should be located on your Micro Focus installation CD in the Redist directory; however the file is not there. Resolution: Download the attached atcinst.zip file, extract atcinst.exe, and execute it on your target client PC. This installs AcuThin Version 8.1.0. atcinst.exe Date: Click here to enter a date.Name: Description of change: Date: Click here to enter a date.Name: Description of change: Jean FarnsworthOld KB# 14096

This article explains how to set a runtime switch when executing a program that calls a web service. Problem: If we are using the following to set a runtime switch when executing a program that does not call a web service, then how do you set the switch if you are running a web service? export COBSW=-F cobrun -F cobol-pgm-name Resolution: To set the switch for a program that calls a web service, in the Server Properties there is a box called Configuration Information. Enter the following: [ES-Environment] COBSW=-F Anything under the [ES-Environment] (case is important) will be set in the server's environment. Old KB# 14039

This article explains how to recover a corrupt Development (LMF) and Runtime (ASLMF) database. Problem: How do I recover corrupt Development (LMF) and Runtime (ASLMF) databases? I am getting the following error message: Micro Focus LMF - 002: The license database is corrupt. License Key database is corrupt. Resolution: You should refer to Recovering from a Corrupt Database in the chapter Installing and Administering Licenses in your Deployment Licensing Guide. With Server Express version 4.0 ServicePack1 onwards, there are utilities to assist with database recovery. For Deployment License Database (Application Server), if the license database is deleted or damaged, you can recover it using the utility aslmdbrecover and then reinstall the license. This utility deletes the license database and any system associated files and recreates the database. It starts the AppTrack utility and prompts you to reinstall the licenses. To recover from a corrupt database: Run th