Rocket® COBOL

This article addresses the possible ASLMF errors encountered with HP-UX 11.11/i operating system. Problem: Hewlett-Packard has introduced some new twists on shared memory usage with the introduction of the HP-UX 11.11/i operating system.  Some of these HP enhancements required similar changes in Micro Focus Application Server runtime licensing, as well as the runtime licensing for Server Express Developer.  This article will cover these changes. Resolution: As more HP customers migrate their COBOL applications to HP-UX 11.11/i from older HP operating systems, which are no longer supported, Micro Focus SupportLine has recorded more cases of ASLMF memory failures.  Here are two that are particular to this environment and are easily resolved: ASLM 1025 Due to misuse reboot is required This error may not be solely caused by the change to HP-UX 11.11/i for shared memory windows but the problem persists in all Server Express 2.0.10, 2.0.11, 2

This article explains Server Express and Application Server licenses. Problem: When done infrequently, installing of license keys can be confusing because of the different types of licenses, license utilities, and ways in which licenses can be installed and uninstalled. The following should help with your understanding of the processes involved. Resolution: Server Express comes packaged two ways. One is called Server Express, the other is called Application Server. Server Express is the development product. It allows users to write, compile, test, and debug COBOL applications. Application Server is a deployment execution subset of Server Express, intended for the production or end user environment where COBOL programs are run and no development activity takes place. In order to use Application Server in a production environment, it is necessary to create COBOL programs on the same version of Server Express, then port (copy) them to the production system. Howev

This article addresses an "Invalid license key. License not installed" error during a reinstall of Application Server. Problem: A reinstall of Application Server resulted in a license is not accepted "Invalid license key. License not installed" error message. How is this resolved? Resolution: To resolve this licensing message simply uninstall Application Server and delete the registry key hkey_local_machine > software > micro focus > aslmf . Then reboot the machine and reinstall Application Server with the serial number and license key provided with the product.Old KB# 14134#Licensing#ServerExpress#COBOL#netexpress

This article explains why a runtime error occurs after a program successfully compiles. Problem: The program (pgmfind.cbl) has compiled successfully, but is giving run time error as follows. Why is this? Execution error: file '/export/home/S127059/Pgmfind.int' error code: 164, pc=C7, call=1, seg=0 164 Run-Time subprogram not found (in CBL_LOCATE_FILE) Resolution: The problem with the routine is because a bad parameter is passed in on user-mode. Without MF"10" user-mode is initialized to x"20" (i.e. space) but with the directive it is x "00" and hence works. Try changing it to: 1 user-mode pic x comp-x VALUE 0. Old KB# 14163

This article addresses two runtime tunables with default values. Problem: Can you explain the default behaviour of the runtime system (how it finds objects to run) and whether the behavior could be modified? Resolution: There are two runtime tunables that can affect this, both which have default values. The tunable program_search_order changes the order of locations in which the runtime system searches for program files. It can have the value 1 (the default), 2, 3 or 4. The values mean: 1 Uses the following search sequence: The runtime system is checked to see if the program is loaded or statically linked. If it is, the search ends. If the COBPATH environment variable is set, the paths specified are searched in order. Otherwise, the current directory is searched. The path in which the calling program was loaded is searched. If the COBDIR environment variable is set, the $COBDIR/dynload path specified is searched. Otherwise, /usr/lpp/cobol/dynload (on AI

This article describes what to do when encountering the error "Invalid Key". Problem: When entering the license key in AppTrack the error "Invalid Key" appeared. Why is this? Resolution: Ensure that when entering the key Application Server Licenses are those that use AppTrack. If you get the above error you are most likely trying to enter the key in the wrong license database. A developer license should be entered in the Licence Manager database. By default this is similar to /usr/bin/mflmf or /opt/lib/mflmf. Old KB# 14147#ServerExpress#COBOL#Licensing

This article explains how to relink the RTS, or runtime system. Problem: Is it possible to rebuild the default runtime? When I used 'rebuild' or 'RTS' in the Product Documentation Index, I could not find the relevant topic. Resolution: The topic can be found in the User Guide Chapter 8 Linking to System Executables. This contains the following information, under the heading Creating an Executable RTS: "An executable RTS is a system executable file that requires the first entry point to be specified at run-time. In Object COBOL V4.1 and earlier, an executable RTS was required when you needed to link C and C programs into your application. However, C and C programs can now exist within callable shared objects; therefore it is no longer necessary to create an executable RTS for this. See the chapter Callable Shared Objects for more details. If required, you can create an executable RTS using cob. For example: cob -xo rts.new subprogs.c -e &

This article explains that the license limit message is a UNIX operating system error. Problem: We are receiving a "License limit exceeded" error message when we logon to a Cobol application. User profiles start a Cobol application immediately upon logon and there seems to be a sufficient supply of correctly installed Application Server licenses, for example 50 licenses, but only a lower number of users, such as 10, are actually able to logon. There are no log entries in /var/mfaslmf/USERLOG which show failure to obtain a Micro Focus license. What is happening? Resolution: The error message is actually not the Micro Focus Application Server license limit message.  The UNIX operating system license limit is what is being exceeded.  Even non-Cobol users cannot log on. Most enterprise-scale UNIX systems are not license-limited, but it is possible.  This problem was last observed on a SCO Openserver system, but it could occur on other plat

This article provides a resolution to Oracle error ORA-01801 (9D,1801) when running Acu4GL. Problem: This problem appears upon upgrading from runtime/Acu4GL Version 6.1 to Versions 7.x and 8.x. With Acu4GL Version 6.1, empty dates were converted in Oracle with a value of 00-DECEMBER-00. Although this behavior was fixed in release 6.2, it’s possible that old values are still stored in Oracle tables, so when runtime/Acu4GL Version 7.x or 8.x tries to read these date fields, an Oracle error ORA-01801 appears. ORA-01801 means that the date format is too long for the internal buffer. Resolution: One solution is to alter the Oracle session, calling the Acu tool sql.acu before opening an Oracle table, as shown here:CALL "sql.acu" USING "ALTER SESSION SET NLS_LANGUAGE='AMERICAN'". CALL "sql.acu" USING "ALTER SESSION SET NLS_TERRITORY='AMERICA'". OPEN INPUT table-name However, this method makes fields "read only." If you tr

This article explains what to do if an error occurs after installing Application Server and executing a program. Problem: After installing the Application Server product, the following error occurred when a program was executed: cobrun32: cobol version number invalid Resolution: This error may be occurring because the environment variables have changed or were not set up correctly in the first place. It may also be the result of mixing two different product environments where different COBOL versions co-exist. Check to ensure the following environment variables are set correctly: COBDIR=Server Express/Application Server base directory PATH=$COBDIR/bin:$PATH LD_LIBRARY_PATH=$COBDIR/lib:$LD_LIBRARY_PATH Note: On AIX, this will be LIBPATH, on HP, SHLIB_PATH Ensure that no other scripts or 3rd party (client) applications changes the environment variables which were already set in the beginning of the session. Old KB# 14137

This article discusses three possible causes for the Shell error. Problem: From within a COBOL program the "system" command is executed to run a program, but the program is not being executed at all. Before it can execute an error is being generated: sh: 0403-057 Syntax error at line 1 : `(' is not expected. There is no bracket in the shell program so what is the problem? STRING "sh myshell.sh" DELIMITED BY SIZE PRTNAME DELIMITED BY SIZE " " PRINT-SERVER DELIMITED BY SIZE " " PRINT-QUEUE DELIMITED BY SIZE INTO SYS-PARAM. DISPLAY SYS-PARAM. CALL "system" USING BY REFERENCE SYS-PARAM. Resolution: In short, there are three possible problems here: Missing null terminator on command string. Not initializing the command string space prior to STRING statement. Not us

This article provides information on a fix for and workarounds for applications that produce a mismatched external data error when compiled after upgrading to ACUCOBOL-GT 8.0. Problem: After upgrading to ACUCOBOL-GT Version 8.0, some applications compiled with -Dw32 that compiled cleanly under previous versions halt with the error mismatched external data even when the programs were not changed. Resolution: This problem is fixed in ACUCOBOL-GT version 8.1.0. Upgrade to this version to resolve the problem. However, you can also try any one of the three following workarounds with version 8.0: Compile with both -Dw32 and -Z72. Compile with neither -Dw32 nor -Z72. This might not be the best solution in some cases. Edit the lib/direct.c as follows; then relink the runtime. In direct.c, add two lines of code by changing this block of code: *************** *** 39,45 **** --- 39,47 ---- #endif /* ACU_SOURCE_FILENAME */ #define ACU_SOURCE_FILEN

This article helps troubleshoot messages such as This is an OSX license, This is an Application Server license, or This is a development license. Problem: What should we do if we encounter The license key entered is not valid or other possible error messages such as: This is an OSX license This is an Application Server license This is a development license Resolution: First, ensure that the serial number has been entered correctly. All Server Express licenses and later Object Cobol Developer Suite licenses have two letters and a plus sign (" ") at the end for licensing purposes. All fifteen characters (twelve numeric digits, two uppercase letters, and the plus sign) must be entered as the serial number. Second, look at the type of license. If it says "Application Server" or "Enterprise Server" go to "AS" below. If it says only "Server Express" or has the word "developer" or "development" or says "Object Cobol Developer Suite" go to "DEV" b

This article explains what to do if the error message "No license key detected" occurs. Problem: We are receiving the following error message: Error - no license key detected. Application Server requires a license in order to execute. Please refer to your application supplier. Resolution: When this error occurs check the tail of /var/mfaslmf/USERLOG to see the captured error message. One of the components on the line will be the value of COBDIR. For example: Thu Sep 8 21:28:14 PDT 2005:No license AS /usr/microfocus/cobol This is the setting of the user environment variable $COBDIR. Run $COBDIR/aslmf/apptrack and choose option 1 License List Example: 2006/02/10 10:52:30 Installed Application Server licenses: 00001 /usr/lib/cobol Version of Server Express 64-bit Edition License units: Unlimited CPUs: 001 Ensure the COBDIR in the USERLOG matches one of the directories listed in AppTrack. If there is no matching COBDIR, change the user profile to export the

This article addresses the recommendations from IBM on performance issues with indexed files on AIX 5.x. Problem: Compiling legacy code with Server Express and running on AIX 5.x can incur singificant performance degradation with respect to same code compiled on older Micro Focus products (Object Cobol Developer Suite) on AIX 4.x. This performance degradation occurs when the system is using a JFS file systems. Resolution: Version 5 of IBM's AIX operating system can benefit from application of certain tuning parameters to JFS file systems. The following are general recommendations from IBM. The effect upon a specifc system may vary. Additional tuning may be required. AIX 5.1 vmtune -c 4 This tuning command will not be retained across a reboot. Therefore, a small shell scirpt with this command should be executed from /etc/inittab at boot time. AIX 5.2 and 5.3 ioo -p -o numclust

This article explains how to resolve an execution error. Problem: We are receiving the following error messages: Execution error : file '/opt/microfocus/cobol/dynload64/animchr.lbr/dispatch.gnt error code: 115, pc=0, call=1, seg=0" 115 Unexpected signal (Signal 4)"AIX 5.3 and Server Express 4.0 SP2 Resolution: The problem is due to the following version of - 5.3.0.30bos.rte.libpthreads. IBM has created a fix for this problem which can be downloaded from: http://www-912.ibm.com/eserver/support/fixes/fixcentral/psearch. The reference is:APAR Number IY80008 However, the problem will soon be fixed in version 5.3.0.40 SP3 of bos.rte.libpthreads by applying IBM apar IY80008 Old KB# 14158

This article demonstrates the minimum configuration needed to make Java call COBOL using the CVM class on Linux. It also discusses how to overcome an "Exception caught loading CVM: null..." error when performing such a call. Problem: You want to test the interoperability between Java and COBOL using the CVM class on a Linux machine. Your call fails, and you receive an "Exception caught loading CVM: null..." error. Resolution: You need a shared library version 7.0.1 or higher of ACUCOBOL-GT. You will also need a Java JRE version of 1.4.2 or higher. Accompanying this article is a zipped file containing test.cbl and test.java, which you can use for testing purposes. Set up PATH, LD_LIBRARY_PATH, and CLASSPATH as environment variables. For example:export PATH= /usr1/products/acu/acu720sh-linux/bin:/usr/java/jdk1.5.0_06/bin:$PATH export LD_LIBRARY_PATH= /usr1/products/acu/acu720sh-linux/lib:$LD_LIBRARY_PATH export CLASSPATH=/usr

This error occurs when trying to run a compiled program Problem: When trying to run a compiled program, we are receiving this error: 187 Run-time system not found on $COBDIR path (Fatal) Resolution: This error occurs because the environment is not set up properly. When installing the product, ensure that the environment is set correctly to point to the product and its drivers and, where appropriate, set other environment variables as follows: On IBM® RS/6000® and Power PC systems running AIX®: COBDIR=/opt/microfocus/cobol export COBDIR PATH=$COBDIR/bin:$PATH export PATH LIBPATH=/usr/lib:$COBDIR/lib:$LIBPATH export LIBPATH On HP® 9000 Series running HP-UX®: COBDIR=/opt/microfocus/cobol export COBDIR PATH=$COBDIR/bin:$PATH export PATH SHLIB_PATH=$COBDIR/lib:$SHLIB_PATH export SHLIB_PATH LD_LIBRARY_PATH=$COBDIR/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH On all other systems: COBDIR=/opt/microfoc

This article explains how to install the Net Express run time and APPTRACK keys silently. Problem: You may want to install the Net Express run time and APPTRACK keys silently, perhaps as part of your own software installation. Because Net Express Studio Server (the new name for Application Server) uses the Microsoft installer, you need to do this with the use of command line flags rather than a script as was previously used for Application Server. Resolution: In order to install the Net Express run time and APPTRACK keys silently, here is a command example: C:\\Server_setup\\SETUP>start /wait srp3250000248.exe /s /v" /qn /l*vx C:\\SETUP_LOG\\INSTALL.LOG ADDLOCAL=DOTNET SERIALNUM=NXDEVAS5 LICENSENUM=012801078005C04D5E0955C0 DATABASEDIR=C:\\STUDIODB This particular command can be packaged as a .bat file and will install the .NET run time, create a setup.log file in c:\\setup_log\\install.log, install the 30 day development runtime license key and serial number,

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 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 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 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 why an RTS 114 error occurs when compiling the Web Service client programs with directives like: DIALECT(ENTCOBOL) or similar. Problem: Compiling the Web Service client programs with directives like DIALECT(ENTCOBOL) or similar may lead to 114 errors. Why is this? Resolution: When using mainframe dialects some data types have an internal representation different to the default. The solution is to compile the -proxy.cbl programs with the default directives, and compile the -app.cbl main program with the required mainframe directives, taking care that the parameters past between both programs are compatible. Old KB# 14042

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