Rocket® COBOL

This article describes what to do if you get a syntax error when executing a query containing a CASE expression. Problem: Executing a query containing a CASE expression with AcuXDBC Version 8.0.0 results in a syntax error. Does AcuXDBC support CASE? Resolution: AcuXDBC Version 8.1 added support for CASE. For versions prior to 8.1, you may use DECODE to obtain the same results. For example, the following two queries are equivalent: select patient_name, decode (animal_type, 'Cat', 'MEOW', 'Dog', 'WOOF', 'Bird', 'TWEET', 'whatever') as SOUND from pets; select patient_name, case animal_type when 'Cat' then 'MEOW' when 'Dog' then 'WOOF' when 'Bird' then 'TWEET' else 'whatever' end as SOUND from pets; With Version 8.1.0, executing either query against the sample database (created by demo.bat) will return: PATIENT_NAME SO

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 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 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 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 the Memory Allocation Error 105 occurs on an AIX 32 bit program. Problem: We are receiving the error RTS 105, Memory Allocation Error, even after setting user ulimits to "unlimited". The program uses CBL_ALLOC_MEM and/or malloc() to obtain memory which, in total, amounts to more than 256 megabytes. RTS105 occurs when 256 megabyte total program memory usage is exceeded. This is due to an AIX system limitation, not a Micro Focus product limitation. Resolution: AIX allocates 256 megabyte segments to a 32 bit process. Up to fifteen addtional segments are available (total of two gigabytes), if the LDR_CNTRL environment variable is set appropriately. Please note that LDR_CNTRL is an AIX system variable and is not used directly by any Micro Focus component. IBM terminology for use of the additional segments is "Large address space model" or "Very large address space model".

This article tells you what to do if, after a successful install, running runcobol produces the error "cannot restore segment prot after reloc: Permission denied." Problem: After a successful install, running runcobol produces the error "cannot restore segment prot after reloc: Permission denied." Resolution: There are several issues that can cause this error: This message can apparently be returned if SELinux is enabled. Unless you are SELinux experts, we suggest that you disable SELinux (see the URL link) and make sure that the problem no longer occurs. Then try the suggestion given at this URL of using "chcon" to change the security context for the shared objects. Next, you might be having an issue with the permissions on the directories in the runcobol path.All of the directories in the path need to have "execute" permissions. If that doesn't work, you may have to uninstall and reinstall wi

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

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