Rocket® COBOL

This article describes how to deal with a response key error: “Internal error, please restart machine and try again” Problem: When typing in the Response Key for a full license an error displays "Internal error, please restart machine again". The license is not accepted despite rebooting the machine and trying again. Resolution: This problem can be caused by a number of things. For example, a virus attack may penetrate a customer’s machine and corrupt the Net Express license which then needs to be reset. Follow this sequence of instructions and steps to resolve the error: Ensure that the Net Express installation has all the latest fixpacks/wrappacks installed and also the latest license protection fixpack (as of this article's publication date, the latest fix is clu12all.exe). Open a Net Express DOS command prompt and type the following command:protcfg /force_reset This brings up the window "MICRO FOCUS License Management System Configuration". select Net

This article describes getting a UNC path from a mapped network share's drive letter. Problem: You need to get a UNC path from a mapped network share's drive letter. Resolution: Use the Microsoft API WNetGetConnection. This function retrieves the remote name of the network resource associated with a local name. You can obtain this API from here: http://msdn.microsoft.com/en-us/library/aa922031.aspx Example (code is also provided as an attachment to this article) COPY "windows.cpy". identification division. SPECIAL-NAMES. call-convention 74 is STDCALL call-convention 66 is cc66. working-storage section. 78 SZ value 25. 01 lpLocalName pic x(5). 01 lpRemoteName pic x(SZ). 01 lpnLength DWORD value sz. 01 proc-pointer procedure-pointer value NULL. 78 MPRdll value "MPR.dll". 01 retDWORD DWORD. *> DWORD = pic 9(9) comp-5 proced

This article describes how to use a different path name (file) with a copied table. Problem: There is a facility to create a copy of a table; however, the underlying data file (path name) is shared between the two tables. So changing the path name for the copied table also changes the path name for the original table. More often than not this is not the desired setup. Resolution: Open the copied table and click Use the Edit Connections. Highlight the table name and click Delete Table Connection. Select the table definition (even if it's highlighted select it again) and click the Add Table Connection. You will be presented with the Add Table Connection dialog box; set the Path Name accordingly and click Add Connection. Click Save Changes. The copied table now uses the path name (data file) set above without changing the path name in the original table. Old KB# 14179

This article better explains the License List (menu pick #1) in AppTrack. Problem: The License List (menu pick #1) in AppTrack is informaton-rich, but can be confusing. Can you please explain? Resolution: Below is an annotated sample display with notes of explanation. 2006/08/13 09:54:52 Installed Application Server licenses: ---------------------------------------------------------- 00001 /product/default Note: This is an Application Server license (CPU license, unlimited user count) tied to the product in /product/default. The latter is the COBDIR value when the license was installed via AppTrack. Version ___ of Server Express 32-bit ES MTO Note: The version is blank because Server Express licenses are not tied to a particular version. For example, when a product is updated from 2.2 to 4.0SP2, the existing license is valid and therefore will not be reissued or supplied with the updated product. License users: Unlimited CPUs: 100 Duration: U

This article explains which entry point names may cause error messages to occur. Problem: When compiling or running the following program with no special options, we receive the below error codes. IDENTIFICATION DIVISION.PROGRAM-ID. ROGERW.ENVIRONMENT DIVISION.DATA DIVISION.WORKING-STORAGE SECTION.01 ALLP PIC X.PROCEDURE DIVISION.CALL 'csort' USING ALLP.STOP RUN. error code: 161, pc=2B, call=1, seg=0 161 Illegal intermediate code Resolution: The problem is that csort is an entry point in the Micro Focus runtime library. There are a few more to be aware of as entry point names with the following prefixes: "_" "mF" "MF" "mf" "CBL" "cob" "CEE" "ADIS" "STRIPE" "fs" "FS" "CEE" "CCI" "oo" "STRIPE" "PARSE" "XML" "Invoke" "scum" (stands for Sooty Co

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 describes how to use the ACUCOBOL-GT built-in Profiler to identify processing times of specific program paragraphs so that you can determine if code changes would improve performance in your batch applications. Problem: You have a batch application that currently takes a certain amount of time to complete. You want to determine if there are any coding changes you could make that would significantly reduce the program's processing time. Resolution: Use the Profiler to create a report that shows the processing time being spent on each paragraph in your program. Examine those paragraphs where the most time is spent to determine if coding changes could reduce processing times. The Profiler is available in version 7.0.0 or higher of the ACUCOBOL-GT runtime. To use the Profiler, follow these simple steps: Compile programs with debugging symbols. UNIX Example Windows Example ccbl -gy test.cbl ccbl32 -gy test

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 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 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 that corrupted shared memory segments may cause error A147. Problem: Why are the TXSeries transactions abending with error code A147? Message "/var/mfaslmf/nolicense [24] : date : not found.   Resolution: When checking the console.msg created by TXseries region, it showed that some shared memory segments were corrupted: *** [tofas8]/var/cics_regions/PL4LOT2> cat con*msg ASLM: shm (pvc) attach fail ASLM: A shared memory area used by Apptrack licensing has been corrupted or deleted, and your system will need to be rebooted before this application can run. *** After rebooting, the error will disappear. Old KB# 14164

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