Rocket® COBOL

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

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

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 describes how to avoid DB0108 and SQL0088N errors by fully qualifying host variables. Problem: Compiling an SQL program from Net Express or Server Express using the DB2(QUALFIX) directive could result in a DB0108 error using DB2 UDB Version 8 or an SQL0088N error using DB2 LUW when the same variable is defined in more than one structure in a program. For example, compiling the following program under DB2 UDB Version 8 results in an error: $set db2(db=sample udb-version=8 QUALFIX) 01 ws-structure-1. 05 ws-var-1 PIC X(10). 01 ws-structure-2. 05 ws-var-1 PIC X(10). procedure division. MOVE 5 TO ws-var-1 OF ws-structure-1 *> this works MOVE 5 TO ws-var-1 OF ws-structure-2 *> this works too EXEC SQL SELECT EMPNO INTO :ws-var-1 FROM EMP WHERE EMPNO = '200010' END-EXEC goback . > * Micro Focus

This article explains the internal logic error when trying to animate a process-id. Problem: When trying to animate a process-id, during session one when running the COBOL program, the program waits for input from an Accept statement. In session two, the process-id of session one is found (ps -u<user-name>, and then animated using anim <process-id>. When the Accept was satisfied in window one, the following error is displayed: rts64: Fatal Error while attempting to process error 200 Resolution: Animating a process-id is called Unsolicited Dynamic Attachment Debugging or Attaching Animator to a running COBOL application process. The RTS 200 error is a catch-all error meaning that the run-time system has stopped as a result of an internal logic error from which it cannot recover and a more specific error code can not be determined. One possible cause for this error is that the environment variable COBDIR is pointing to the Server Express directory, but

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

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 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 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 explains why the 164 Run-Time subprogram not found error occurred. Problem: Why are we encountering the following runtime error? Load error : file 'cobmffh64.so.2' error code: 164, pc=0, call=1, seg=0 164 Run-Time subprogram not found Resolution: This error occurred because the UNIX/Linux command sudo was used to submit the programs. sudo (super user do) is a program that allows users to run programs with the security privileges of another user (normally the superuser). Each command is logged. It also initializes the environment, leaving TERM unchanged, setting HOME, SHELL, USER, LOGNAME, and PATH, and unsetting all other environment variables. The LD_LIBRARY_PATH must be set in order for the Run-Time system to be able to find the subprogram file cobmffh64.so.2. The COBOL programs are called from a job submission system using wrapper scripts. The error is resolved by exporting LD_LIBRARY_PATH=$COBDIR/lib in the script. Old KB# 1

This article is specific to ACUCOBOL-GT and describes how to write a menu handling routine that creates menus dynamically by reading a file. Problem: You need to write menus that will change (dynamic menus) if you change the content of a file, without recompiling the program. Resolution: Attached to this KB article is an AcuBench demo project that contains sample code for creating dynamic menus, and a sample file for testing. The important parts of the code are described below. Read a file and create the level and the branches needed for your menu. The demo project uses the following code to accomplish this: Screen1-Aft-Initdata. open input filemenu/* Create a new menu */ call "w$menu" using wmenu-new giving menu-handle if menu-handle = zero go to acu-menudina-mn-1-exit end-if move low-values to filemenu-exception start filemenu key is greater than filemenu-exception

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 the correct Language C to resolve an error 114 message. Problem: What is the message Error 114 encountered during finalization when the main module is writen in Language C and calls COBOL modules? Resolution:One reason this error is displayed is because cobinit function is used and cobtidy() is not used. The Language C must be as follows: main( int argc , char *argv[]) { .. cobinit(); ........... cobtidy(); } Old KB# 14057

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

This article explains that in SQL, character literals should be enclosed with single quotes, rather than double quotes. Problem: This SQL statement returned an ORA-00904 error (invalid column name): EXEC SQL       SELECT COL1       INTO :HOSTVAR       FROM TABLENAME       WHERE COL2 = "VALUE" END-EXEC Resolution: In SQL, character literals should be enclosed within single quotes, rather than double quotes. The above statement should therefore be changed to read: EXEC SQL       SELECT COL1       INTO :HOSTVAR       FROM TABLENAME       WHERE COL2 = 'VALUE' END-EXEC Old KB# 14045

This article describes how to set up the ACUCOBOL-GT configuration file so that an application can use the F10 key on Windows. Problem: You are working on a graphical application on Windows and you want to be able to use the F10 key in your program. Resolution: Set the F10_IS_MENU runtime configuration variable to "0". By default F10_IS_MENU is set to "1", which does not allow you to use it inside your program. When set to "0" you will be able to recover the control of the key in your program. Incident Number: 2180697 Old KB# 14106

This article explains that the RTS 173 on _mF7801 error is due a change in the control routine support library. Problem: After an upgrade from Application Server for Server Express 2.0.11 to Micro Focus Server 5.0, generated code gives the following error message: Load error : file '_mF7801' error code: 173, pc=0, call=1, seg=0 173 Called program file not found in drive/directory Resolution: The RTS173 on _mF7801 is due a change in the control routine support library between two versions of Server Express. GNT code created with Server Express 2.0.11 or earlier will not work with Server 5.0. The solution is to either deploy intermediate code (INT) created with the older version of Server Express or upgrade Server Express and regenerate the GNT code using the new version. Old KB# 14038

This article explains what to do when invoking a series of Object COBOL classes is producing an apparent memory leak. Problem: We are running a mainline COBOL application which loops calling / invoking a series of Object COBOL classes is producing an apparent memory leak. What should we do? Resolution: The most common cause of memory management problems associated with classes is a failure to finalize objects before exiting the program. The cause of the performance problem is a memory leak, the amount of memory allocated to the running process grows continually and in small incements on every iteration of the processing loop. The memory leak is occuring because there is one (or more) object invoked that is not finalized or deleted. To test for this condition do the following: - Added the 'Behaviour class to the first class invoked i.e. Behavior is class "behavior" - Insert the following code j

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

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

Environment Server ExpressServer for COBOLApplication Server for ServerExpressApplication Server for NetExpress Situation When running ./lmfgetpv or ./mflmman the following message is displayed: [root@servername lmf]# ./mflmman MF-LMF:Tue Mar 15 15:56:17 2022: LMF Starting MF-LMF:Tue Mar 15 15:56:17 2022: Unable to open License Key database MF-LMF:Tue Mar 15 15:56:17 2022: LMF Closing Down [root@servername lmf]# Cause Corrupted license database. Resolution Log in as root and try the operation again.If it does not work, the license database will need to be reset.Development License DB:/lmfdbrecover located in opt/microfocus/mflmf.Re-start License Manager../mflmman                                                      &nbsp

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