Rocket® COBOL

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 identify installed licenses and serial numbers. Problem: I am trying to identify which licenses and serial numbers are installed. How can this be done? Resolution: To find the serial numbers and the license keys installed on a machine for Server Express Developer Licenses, take the following steps: Go to the installation location for the LMF License Manager. If the location is unknown it can be found using one of several methods. Execute the command $COBDIR/lmf/lmfgetpv and if the License Manager is running its location will be reported. From Server Express 4.0 ServicePack 2 and later, execute the command $COBDIR/bin/mflicense, which is a utility that allows you to use the LMF administration tools, assuming that you possess Super User privileges. Execute the command: find / -name mflmfdb\\* -print. The results of the find command should point to the proper location. To identify the Server Express Developer key

This article explains how to use shared objects on UNIX. Problem: I would like to know more about using shared objects on UNIX. Do you have any information toward this? Resolution: Callable shared objects (CSO), self-contained callable shared objects (scCSO), COBOL shared libraries, shared libraries are all examples of what UNIX thinks of as shared objects. There is no architectural difference between a shared object and shared library[1]. There are simply different conventions about their naming and use. Most third party code, for example Oracle, is supplied as one or more shared objects. Only one copy of the text (code) of a shared object is present in memory, no matter how many processes and executables reference it. This code sharing makes shared objects efficient and attractive. Shared objects save disc space, as there is only one copy of the code on disc. Shared objects also allow old programs to pick up fixes without the need for recompilation or relinking.

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 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 the Pipe Create Error and how to resolve it when starting License Manager. Problem: We are receiving the following error message when attempting to start the License Manager and we don't understand Pipe Create Error: Starting MFLM License Manager MF-LMF:Thu Aug 14 08:58:35 2008: LMF Starting MF-LMF:Thu Aug 14 08:58:35 2008: Pipe Create Error MF-LMF:Thu Aug 14 08:58:35 2008: ENOENT(2): No such file or directory MF-LMF:Thu Aug 14 08:58:35 2008: LMF Closing Down Resolution: License Manager uses named pipes as temporary files and creates them in the location defined by the UNIX operating system setting of P_tmpdir. This is typically /tmp. You might want to relocate the named pipes. When License Manager is launched it creates one long-lived named pipe, called LMF-common, which exists until License Manager is closed down. While it is running, it also creates a number of transient named pipes that exist only for a short time. You might wa

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

This article describes how to use F11 or F12 on a Windows application. Problem: You want to configure the runtime so you can recover the keystrokes F11 or F12 from your keyboard on your Windows graphical application. Resolution: Set the KEYSTROKE runtime variable in the configuration file to return the exception expected for those keys. This is done by adding the EXCEPTION keyword to this variable and setting its value. For example: KEYSTROKE EXCEPTION=11 U1KEYSTROKE EXCEPTION=12 U2 In this example, F11 returns exception value 11 and F12 returns exception value 12 when used. Your next step is to write the code to use those two values. The KEYSTROKE variable (including its keyword options) is described in detail in section 4.3.2.2 of your ACUCOBOL-GT User's Guide. Incident Number: 2180699 Old KB# 14104

This article explains what happens when COBDIR/aslmf/apptrack option 6 is entered. Problem:Using AppTrack to reinitialize the COBOL AppServer with option 6, are there some files being overwritten or created? If so, what file(s) get updated or created when COBDIR/aslmf/apptrack option 6 is entered? Resolution: No files are reinitialized by $COBDIR/aslmf/apptrack option 6. Instead, the shared memory segments that are used by AppTrack are reinitialized based on the database/var/mfaslmf/mfasdb To view the memory seqments used by AppTrack use 'ipcs -mob'. Look at the shared memory segments that are 6 bytes in size. These are aslmf segments (they will have segment keys commencing 0x741cc1... ) The NATTCH column shows how many processes are holding are holding aslmf licenses. Each attach represents one license unit. These segments are reinitialized automatically when you add or remove a license. Old KB# 14018#COBOL#ServerExpress#Licensing#netexpress

This article provides a resolution to the RTS 164 error. Problem: RTS 164 load error file cobdirect64.so.2 error code 164 pc=0 seg=0 cobdirect64.so.2 resides in $COBDIR/lib COBMODE=64 LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 set to $COBDIR/lib Resolution: Unset LD_LIBRARY_PATH_64 Old KB# 14033

This article explains how to create a multi-threaded runtime Problem: How does one create a multi-threaded runtime? Resolution: To create a multi-threaded runtime, include the -t flag when you build the RTS. For example, to create an RTS with an open entry point: cob -xvte "" -o MyThreadedRts Note: There is one already supplied with the product. Use cobrun_t progname to use it. Old KB# 13990

This article describes an error caused by the SMP kernel when debugging Server Express 4.0. Problem: When debugging in Server Express 4.0 (up to ServicePack2) running Linux RedHat, the following errors occur as a result of the SMP kernel. How can this be resolved: Execution error : file '/usr/microfocus/cobol/dynload/animchr.lbr/dispatch.gnt' error code: 114, pc=0, call=1, seg=0 114 Attempt to access item beyond bounds of memory (Signal 11) Resolution: Using a non-SMP kernel will work, however, this problem has been solved in FixPack 40.03_62 for Server Express 4.0 SP2 running Linux which was released 16 July 2006. Old KB# 13979

This article provides a solution for Server Express File Handler reading one byte at a time. Problem: When reading from a pipe, Server Express File Handler reads only one byte at a time. Resolution: The following functionality is added with Server Express WebSync 3 product level: pipe_buffer_size Set the size of the buffer used by the run-time system when reading information from a pipe. Syntax: >>-----set pipe_buffer_size=---integer------><> Parameters: integer Any positive integer value indicating the size of the pipe buffer maintained by the run-time system. Properties: Default: 0 Setting: None Old KB# 14016

This article describes various temporary files created by RTS to provide certain functionality. Problem: The RTS creates various temporary files to provide certain functionality. These files are created in $TMPDIR (if set) or /tmp, /usr/tmp or /var/tmp depending on the UNIX platform. If any temporary files are left lying around then it is because the RTS could not run its cleanup code, for example, if kill -9 is used or when exiting early from a C debugger. Temporary files created by the RTS have the following prefixes: cobdi Created during compilation cobhp CBL_VFILE_ heaps - mainly used by the checker cobru CBL_EXEC_RUN_UNIT inheritance information - removed by child cobsm Shared memory lock cobxi Embedded source code file names - created during compilation and removed by cob/editor/cmenu cobdb/cobdc Debugging cobdf/cobdt Mixedlangdebug debugging cobcg/cobsv Cross session debugging coban Created (and removed) by cobanim Reso

This article explains why the RTS 173 error on 'cdi2' ocurrs when trying to run cobprof. Problem: In Server Express v5.0, you might get the following error when trying to run the Profiler (cobprof): Load error : file 'cdi2' error code: 173, pc=0, call=1, seg=0 173 Called program file not found in drive/directory Resolution: This is a known issue and is fixed in Server Express v5.0 Websync 4 (WS04) Old KB# 14004

This article explains how to share files in the same run unit using COBOL. Problem: My application is made with COBOL modules that open the same physical file and all modules are included in a same run unit. For some reason, the file status 9/065 is displayed during the running of some modules. Why is this? Resolution: This is happening because it is necessary to modify the values of options on the File Handler Configuration file. echo "[XFH-DEFAULT]" > my.cfg echo "RUNITLOCKDETECT=OFF" >> my.cfg echo "OPENINPUTSHARED=ON" >> my.cfg EXTFH=./my.cfg export EXTFH Old KB# 13988#COBOL#netexpress#AcuCobol#ServerExpress#RMCOBOL

This article explains how to recover an AppTrack password. Problem: We are unable to get into the  $COBDIR/aslmf/apptrack utility. The password is unknown. What should we do? Resolution: Micro Focus SupportLine can recover the AppTrack password. Follow these steps: Open a SupportLine incident at supportline.microfocus.com Change directory to /var/mfaslmf, using the command "cd /var/mfaslmf" Then issue the command "tar -cvf mfasdb.tar mfasdb". This will create a file mfasdb.tar. Transfer the tar file via binary to the PC then attach it to the incident. The password will be returned by return email or telephone depending on the urgency. Old KB# 14000#COBOL#Licensing#ServerExpress#netexpress

This article explains how to remove a license from the Server Express development license database. Problem: How do you remove a license key from the Server Express development license database (LMF)? Resolution: To uninstall a Server Express development license, follow these steps: Change directory to the /opt/microfocus/mflmf directory. Note: Your mflmf may be in a different path Use the command ./mflmadm to start the License Management utility. Enter /2 to bring up the license entry screen. Put the serial number on the first line up to and including the "AI " Tab to the next line and enter the full license key. Note: The fields are not case sensitive and you may enter the spaces or not as you choose. Press /4 to un-install the license. Press /7 to refresh the license database. Press Esc then "y" to exit. Old KB# 14025#ServerExpress#COBOL#Licensing

For MF COBOL to work across NFS-mounted file systems, NFS must be configured to handle locks correctly. This C program tests the NFS configuration. Problem: NFS-mounted file systems may cause file access errors when used with MF COBOL. Problems may occur, not only at runtime involving indexed files and data files, but also when compiling or using the Animator. When opening a file, even a flat ASCII file such as a COBOL source file (.cbl), Micro Focus uses the UNIX system call fcntl() to establish a file lock.  This is to prevent other processes or programs from opening the file for "exclusive" access. NFS-mounted file systems are sometimes configured such that the UNIX system call fcntl() does not work.  This is not the fault of COBOL, though it can result in a hang or an error reported by the COBOL system. Resolution: The following C program tests whether an NFS-mounted file system is configured to handle the UNIX system call fcntl() correctly. The progr

This article explains an error that occurs when attempting to execute an application. Problem: When attempting to execute an application, the following error message was received: Dependent module libfhutil.2.0.a(shr.o) could not be loaded Resolution: The error libfhutil.so.2.0: open failed is normally due to the fact that this library file, used in the old file handling utility (fhutils), was dropped in OCDS 4.1.40 and support for it was removed in all successive versions of the product and all versions of Server Express. It was replaced by the Rebuild utility which is capable of the same functions with better performances and the ability to handle larger files. Having been replaced with the Rebuild utility, it will be necessary to recompile and relink all the object and executable files. This error message may indicate that there is an executable that was built using Object COBOL V4.1.xx and that you are attempting to run the executable using a Server Express

This article provides information on how to improve the performance of mfsort. Problem: The results from testing mfsort with the same input data over many successive runs shows variance in the sort times. The data records in the test are large, circa 3K. How can the performance be improved and the results stabilised? Resolution: Mfsort works by storing only the key data up to 1K of data in a structure which is then sorted. If SORTSPACE is large enough, this structure is held in memory rather then paged to disk, improving overall perfomance. As sort only stores key data 1K record data, for larger records the original data needs to be accessed when returning data from the sort, resulting in slower performance. More data can be forced into memory by adding an additional key to the sort. As a guide, this additional key must be "record length - 1024 bytes" in size to ensure the whole record is held. The benefit of this approach will

This article explains how to keep AppTrack from continually asking for a password. Problem: When running AppTrack for the first time, a password wasI established. Subsequently, AppTrack is asking for the password every time it is used. How can this be avoided? Resolution: With Server Express version 4.0 or higher, you can remove AppTrack and do a fresh install of the AppTrack system and the Application Server licenses. Before beginning, you should have your Application Server licenses available (both the serial numbers and the license keys) because you will need to re-enter them. This procedure can be completed easily within a few minutes. Log in as root. Set the COBDIR environment variable to the location where the COBOL product is installed, and make sure it is exported. Change directories to $COBDIR/aslmf: cd $COBDIR/aslmf Run the script "aslmdbrecover": ./aslmdbrecover At the end of this script, you will be taken into the AppTra

This article aims to aid in the improvement of performance when accessing indexed files. Problem: This purpose of the configuration option INDEXCOUNT is to aid in the improvement of performance when accessing indexed files. Resolution: The default value for INDEXCOUNT should be suitable for most files. However, for files where the depth of the tree is greater than 4 or where there are a number of alternate keys defined for the file, increasing INDEXCOUNT can dramatically improve performance. The information required to make this calculation can be gained by using the rebuild tool to validate the file (rebuild -f filename). A general guide to setting INDEXCOUNT is as follows: INDEXCOUNT = (Tree Depth * No Keys) No Keys This parameter is put in the External File Handler configuration file pointed to by the EXTFH environment variable. See the File Handler documentation for specific instructions for using the Externa

This article explains that the thread model used on AIX systems has changed and can create a dynamic linker error. Problem: Programs compiled on an AIX 5.2 system and then deployed on a production system running AIX 5.3 fail with the dynamic linker error: 0712-001 Symbol not found _pth_init Resolution: The thread model used on AIX systems has changed in AIX 5.3. AIX uses the thread model M:N. This makes programs compiled with earlier versions of the operating system incompatible. In order to deploy executables to an AIX 5.3 system the application must be compiled on AIX 5.3. Old KB# 14013