Rocket® COBOL

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

After upgrading from a previous version the following error message "wrun32.exe - Entry Point Not Found" may be seen. Problem: After a user upgrades, they may encounter the following error message: "wrun32.exe - Entry Point Not Found" when doing a version check or running a program. Resolution: Open the Windows control panel, select the system icon, click on the Advanced tab, then on the Environmental Variables button. Remove the path to the old installation of Acucobol software and set the path to the current Acucobol that is being used. Incident Number: 2259025 Old KB# 14183

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 articles explains how to configure Apache so the CGI runtimes find the appropriate configuration file. Problem: You are using a CGI application, but do not know how to set up a configuration file correctly. Resolution: The configuration file for Apache is the httpd.conf file. Add the following line into the file: SetEnv A_CONFIG c:\\tmp\\cblconfig Once you have done this restart the Apache server and you are set, the CGI runtimes started by the Apache server will look for this configuration file. Old KB# 14185

This article describes an Acurfap error, which may appear when trying to run a program from within AcuBench. Problem: Click on "Execute" to run a program from within AcuBench. An error like this appears in the Output window: --------- Compiling Program1.cbl ------------------- Compile options = -o acurfap://myserver:5632:/@.acu -x -GaCopying object file to serveracurfap://myserver:5632:/Program1.acu: The system cannot find the file specified.Program1.acu - Completed: 0 Error(s), 0 Warning(s). Resolution: The "Use Thin Client" button has been incorrectly activated. This causes the runtime to search for a remote object to run. Deselect "Use Thin Client" button to run a locally compiled object. Incident Number: 2263553 Old KB# 14184

This article describes how to make modifications to the SDE menu. Problem: Is it possible to change the defaults on the SDE menu screens so that the user doesn't have to type in overrides for every session? Resolution: Yes, follow these steps and commands: Invoke the following commands as root, to backup the existing SDE: mkdir $COBDIR/etc/safe mv $COBDIR/etc/tbox.mnt $COBDIR/etc/safe cp -p $COBDIR/etc/tbox.mnu $COBDIR/etc/safe Copy the SDE menu file into a local working directory: cp $COBDIR/etc/tbox.mnu . Make edits as required. Rebuild the menu file - this will create "tbox.mnt" in the current directory: cobrun chkmenu tbox As root, copy the updated menu files back to the etc directory under COBDIR: cp -p tbox.mn? $COBDIR/etc Invoke SDE and you will see the updates. Incident number: 2258832 Old KB# 14176

This article describes how to ensure that certain fields on a form accept only upper or lower-case text, without modifying the program. Problem: The default behavior on a screen form is to type data in the form using lower-case and upper-case text at the same time. In some cases, it is necessary to force the use of upper-case (or lower-case) only. Resolution: Adding the UPPER (or LOWER) property to the definition of a screen control is one method of accomplishing this. However, this requires the program to be recompiled. An alternative solution that does not require compiling is to configure several environment variables. For character screens, use this environment variable: KEYBOARD case=lower or KEYBOARD case=upper For graphical screens, the KEYSTROKE environment variable allows you to remap lower-case to upper-case, or vice versa. For example: KEYSTROKE data=65 97 <- this will transform the edited 'a' in 'A'KEYSTROKE

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

Executing the ACUCOBOL-GT application gives the error "Thread did not ask for message after accept terminated by one". Problem: When running the ACUCOBOL-GT application, after an indeterminate period of time, the Runtime halts with the following error: "Thread did not ask for message after accept terminated by one" Resolution: Generally this message is due to a coding error. When coding "SEND message to all threads" there must be an "ACCEPT... allowing messages..." coded in every thread, along with "if crt-status = 95 then RECEIVE message...". If the RECEIVE is missing, the message queue will become full, because of the SEND to all threads. That's when this error can be seen. If this message is seen in a version prior to 7.2.2 and the threads are coded correctly, there is a possibility that the Runtime encountered a problem where under certain rare circumstances it fails to clear an internal flag related to thread messaging. T

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

Attempting to rebuild a Vision file with vutil32 results in the error "invalid function parameter". Problem: Attempting to rebuild a corrupted Vision file using vutil32 -r filename gives the following error message: "invalid function parameter". What does this mean? How can the file be rebuilt? Resolution: This message is seen when the file is broken in a way that causes the rebuild to fail. The file may be broken in a way that it will not be possible to recover any records at all. However there are a couple of things to try. Specify a key to rebuild on:vutil32 -rebuild -k 0 filename for the primary key. If that fails try: -k 1 for the first alternate key (if there is one), and so on for each alternate key. If all of those fail it may be possible to programmatically recover the records. Set the Runtime configuration ERRORS_OK to "ON" which should allow the OPEN of the corrupted file to succeed. Then START at the begi

On SCO UnixWare 7.1.4 the call to C$JAVA fails with this error, seen in the runtime trace: Java dynamic init failed. Problem: The ACUCOBOL-GT application calls Java programs via the C$JAVA library routine. On Windows and Linux platforms there is no error when running the application. However, when running the same application with the same configuration on SCO UnixWare 7.1.4, the call to C$JAVA fails with the error: Java dynamic init failed. Resolution: On SCO UnixWare 7.1.4 (and possibly some other platforms) there are additional steps and configurations necessary to enable the C$JAVA library routine to function properly. Here's what must be done: In the ACUCOBOL-GT 8.1.0 lib directory copy "Makefile" as "Makefile-java". Modify Makefile-java as follows: Locate the two Java lines, uncomment them, and set them like this: JAVA_HOME = path to main java directory]JAVA_LINK_FLAGS = -L $(JAVA_HOME)path to directory containing lib

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

Read-only entry fields no longer change background/foreground colors with 8.1.0. They are shown only in gray. Problem: Read-only Entry Fields used to allow their foreground or background colors to be modified. The Runtime version 8.1.0 stops this behavior, and leaves the read-only field gray. Resolution: This change was made to follow Windows standards and was implemented with ECN-3699 released in 8.1.0. You can turn this behavior off so that your applications will not be affected by this change. Set the following configuration variable in cblconfi:ECN-3699 0 The value "0" turns the ECN off, value "1" activates the ECN and entry-fields remain gray. This configuration variable has been introduced in ECN-3848, available in the future release of ACUCOBOL-GT 9.0. Incident Number: 2131301 Date: Name: Description of change: Date: Name: Description of change: Old KB# 14120

This article addresses the ASLM 2046 semaphore error message "rerun as root" on HP-UX. Problem: We have received the following error message on HP-UX: ASLM: Semaphore failure. Rerun as root ASLM: Errno 2046 Resolution: The error number indicates that this is a locking problem.      /* System record lock table was full */ Try raising the system limit for the number of locks to resolve this problem. The parameter "nflocks" is the tunable which controls the maximum number of file locks. Raise the system limit on this parameter. Sizing the system record lock table limit (nflocks) depends upon the workload type in the user's environment.  The number of record locks the system requires is highly dependent on the activity in the system at any point in time.  Monitor this over a period that would be using the most locks and then set nflocks appropriately.  The error occurs when other activities in the system causes

This article provides a solution for several problems that can prevent AcuServer from starting. Problem: When starting AcuServer, it appears to start successfully (see output below), but it will fail on either a –info test or if a program tries to access it. [root@oprtest etc]# ./acuserver -start acushare: opening '/dev/console' for error outputacushare: installation complete! acushare: already running. AcuServer started [root@oprtest etc]# cd ../bin [root@oprtest bin]# ./acuserve -info AcuServer is not running on: sparky [root@oprtest bin]# ./acushare -info acushare: already running. Resolution: If a machine has multiple network cards or if themachine name is not unique on the network, the following configurationvariables must be set in the a_srvcfg:# For servers with multiple Network InterfaceCards, this variable will# determine which address to use when listeningfor connections. The# default value is blank, which will use thefirst address found.#SERVER_IP# If you have

This article describes how to resolve error ld: 0711-596 SEVERE ERROR. Problem: Creating an executable from a mixture of COBOL source and pre-compiled C objects results in an error "ld: 0711-596 SEVERE ERROR." A command line example would look like this:cob -x myprog.cbl cprog.o Error message: ld: 0711-596 SEVERE ERROR: Object cprog.o An RLD for section 2 (.data) refers to symbol 22, but the storage class of the symbol is not C_EXT or C_HIDEXT. Resolution: The problem is with the C object file. In this case, the cause is a corruption in the object file, possibly from FTP-ing it between systems in ASCII rather than BINARY mode. Incident Number: 2262147 Old KB# 14177

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 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 helps understand the difference between two similar file status messages. Problem: How do you distinguish between the following similar file status messages? File status 37 is: An OPEN operation has been tried on a file which does not support the open mode specified in the OPEN statement. File status 9/37 is an RTS error 37: File Access Denied Resolution: File status 37 consists of the characters "3" and "7" (hexadecimal 3937). File status 9/37 is the characters "9" and "7" (hexadecimal 3937). Note: There is no file status "97" with which to confuse the latter. File status 37 is usually a programming error, such as OPEN EXTEND of an indexed file. File status 9/37 is usually a runtime error caused by a conflict between file and/or directory permissions and user access rights. Old KB# 14116

This article explains that an RTS error 173 occurs if the flag RTLD_GLOBAL of dlopen API is not used. Problem: When a program loads a shared library with dlopen API and later loads functions belonging to this library the following error occurs: RTS error 173 (Called program file not found in drive/directory) Why is this happening? Resolution: This RTS error 173 occurs if the flag RTLD_GLOBAL of dlopen API is not used. This RTS error 173 is normal in regards to the definition of RTLD_GLOBAL flag. RTLD_GLOBAL allows symbols in the module being loaded to be visible when resolving symbols used by other dlopen calls. These symbols will also be visible when the main application is opened with dlopen(NULL, mode). dlopen API: http://publib16.boulder.ibm.com/doc_link/en_US/a_doc_lib/libs/basetrf1/dlopen.htm The demonstration attached just reproduces the RTS 173 described here. In funct