Rocket® COBOL

Runtime fails to initialize properly. Problem: When trying to execute the 64-bit Windows runtime you would see the following error: The application failed to initialize properly (0xc0150002) Resolution: This is because atermmgr.dll is looking for a 32-bit version of comctl32.dll instead of the 64-bit version. You will need to extract the files in the attached zip archive and replace the existing files in the \\AcuGT\\bin directory Incident Number: 2259559 Old KB# 14204

This article describes the read part record error: "End of File before End of Record", or "file open in wrong mode". Problem: This error occurs when trying to read a control card file within a COBOL program. An example is a one-record parameter file with 9 bytes of data and filler to byte 80. Resolution: This error can occur when the file organization specified in the program does not match the actual file type. If no organization is specified in the program, the default file type for sequential files is record sequential. A file created with a non-Micro Focus file editor will default to an organization of Line Sequential. The resolution is to change the SELECT statement to add the phrase: Organization is Line Sequential Old KB# 14229

This article describes the cause of this compile time warning message and what you can do to resolve the problem. Problem: Compiling a COBOL program using the CREATEXFD directive can result in the generation of the compile time warning message “Field xxx causes duplicate database data.” The condition that causes this compile time warning to be generated is described in the Database Connectors User’s Guide, section "Performance and Troubleshooting." This warning can occur when you compile with the CREATEXFD directive. The XFD will be built and the Connector will operate correctly. However, the warning informs you of a special database situation that is not advisable. This warning means that your record definition should be restructured. Your current definition is set up in such a way that both of the following are true: You have overlapping key fields Both keys must be represented in the database as separate items Data

This article describes what C compiler to use for relinking the runtime with C libraries on Unix/Linux. Problem: You have created your own C libraries or you want to use 3rd party C libraries that will be called from ACUCOBOL-GT programs. Resolution: You need to relink the runtime by using An ANSI 89-compliant C compiler supplied by the vendor of your UNIX system, either included as part of your UNIX system or as an add-on option. Check with your operating system vendor to see if the C compiler is capable of building shared libraries. If it is not, you will need a full version of the compiler to relink the ACUCOBOL library. Please remember than Bundles will not be enough, and a full version of the compiler will be needed for most systems. Detailed information on interoperating with C and C is provided in the manual A Guide to Interoperating with ACUCOBOL-GT, Chapter 6. Incident Number: 2181911 Old KB# 14268

This article explains how to change the port that the Windows Data Server is using. Problem: How do I change the port that the Windows Data Server is using? Resolution: On your Data Server system, stop the Data Server. Do this from the Windows Control Panel's Services utility, available under Administrative Tools. At a command prompt, enter regedt32 to start the registry editor. Navigate to HKLM\\Software\\ODBC\\ODBC.INI\\SimbaServer\\SvrPort. Change the default port number,1583, to either 1584 or some other port number that you know is not in use. Restart the Data Server. Do one of the following: If your system has the Database Administrator version of the Data Client installed: Start the Data Client. Click the entry for the Data Server system; then click Modify. Change the port number to the same number you specified in the registry in step 4 above; then click OK. If your system does not have the Database Administrator

This article describes how to configure the PowerTerm terminal emulator. Problem: Ericom's PowerTerm is a terminal emulator that is shipped with the Micro Focus Net Express product. PowerTerm is used for UNIX and LINUX environments. When executing sde or the Micro Focus license administrator, the windows are not formatted correctly or the line drawing characters are not correctly displayed. As with most emulators you have to configure it so that the line drawing, colors, function keys and overall window display are acceptable. Resolution: To configure PowerTerm: Click Terminal > Setup. On the Emulation tab, click SCO ANSI. On the Display tab, select 80 Columns and 25 Lines Per Screen. On the UNIX/LINUX side: export TERM=ansi If the environment variables COLUMNS and/or LINES are set, be sure they are set to: export COLUMNS=80export LINES=25 Old KB# 14263

How can AcuXDBC Server be set up as a Windows Service? Problem: When the server is rebooted, the AcuXDBC Server is killed and must be restarted manually. How can it be configured to run as a Windows Service? Resolution: AcuXDBC Server does not currently have built-in capability to run as a Windows Service. That functionality may be added in a future release. In the meantime, here is a Microsoft KB article detailing how to set up any .exe file as a Windows Service: http://support.microsoft.com/kb/137890 Such user-defined services cannot run a batch file — it must be an .exe file. Normally, AcuXDBC Server is started from a batch file, acuxdbcs.bat, by issuing the command "acuxdbcs -start". Examining the acuxdbcs.bat file reveals that the "-start" option results in execution of the xdbcsrvr command. The details for this command are found in the section 5.7, "Starting AcuXDBC Server," of the AcuXDBC User's Gui

Error 1904: failed to register NMSecComParams.dll file Problem: Error 1904.Module C:\\Program Files\\NetManage\\rss\\NMSecComParams.dll failed to register. HRESULT -2147221164. Contact your support personnel Resolution: Disable Data Execution Prevention (DEP) using the steps below: Login as an Administrator on your PC. Go to Start > Control Panel then double click on the System icon. Select the Advanced tab and, under the Startup and Recovery section, click on the Settings button. Click Edit. This will open the Boot.ini file in Notepad. Note: Make a backup of this file before you make any changes. Search for the line that contains the following string: /NoExecute= Change this string to: /NoExecute=AlwaysOff Save the file and reboot the PC. Re-install RUMBA. It should install without the Error 1904 messages. Restore Boot.ini back to its original state. Old KB# 14203#Rumba

This article explains how to successfully install EnterpriseLink version 5.0.5 on Windows Vista when the setup program returns an error. Problem: When attempting to install the base version of EnterpriseLink version 5.0.5 on Windows Vista, the setup program returns an error message indicating that you do not have the required 2.1.2.4202.3 or later prerequisite version of the Microsoft Data Access Components (MDAC) installed. This happens because Vista no longer includes MDAC; it has been replaced with Windows DAC, which has the same version number as the Windows version number (in this case, version 6.0). Resolution: You can force EnterpriseLink to install on Vista without checking for a valid version of MDAC by entering the following at a command prompt in your EntepriseLink installation directory: setup.exe /IGNORE_MDAC Note: /IGNORE_MDAC must be in upper case. Old KB# 14276#EnterpriseLink#Rumba

This article describes how to set up RUMBA to enable users to enter non-numeric characters into Mainframe numeric fields. Problem: Does RUMBA support the Numeric Override feature? Resolution: The standard 3270 host applications allow the definition of data input fields as either numeric only or alphanumeric. If a user tries to enter a non-numeric character into a numeric field, 3270 applications do not accept the input. RUMBA Mainframe display supports a Numeric Field Override feature to allow for non-numeric characters to be entered into numeric fields. By default, this option is disabled in RUMBA. Perform the following steps to enable this option: Launch a RUMBA Mainframe Display session. Click Options > Edit > General. Check Numeric Field Override; then click OK. This enables the Numeric Field Override option, and enables users to enter non-numeric characters into numeric fields. Old KB# 14235#Rumba

How to safeguard against idle sessions when users do not logoff from the OnWeb Server. Problem: Session resources are not cleaned up when users close their browser without logging off. Resolution: If you have chosen to customize your OnWeb application web pages or html code, you can ensure user sessions are properly terminated by adding the autologoff function to your HTML code.  For example: <SCRIPT language="JavaScript" src="kbhandl.js"></script> And then merge this into your BODY tag: <BODY onUnload="autoLogoff()"> This will clean up the sessions when the users close their browsers without logging off. The autoLogoff() function is implemented in kbhandl.js, which is included in the sample templates for OnWeb Server. Old KB# 14215#Rumba#OnWeb

After my iSeries has been restarted, how can I auto start my OnWeb server? Problem: Older versions of OnWeb Server for iSeries do not have the capability to auto start. Users have to manually start OnWeb Server every time the iSeries restarts. Resolution: With OnWeb Server 7.2.5 and above, customers can edit their QSTRUP program on the iSeries to automatically start the OnWeb Server. Example code for a default installation that used the naming convention ONWEB: /* Start ONWEB Server */ ADDLIBLE LIB(ONWEB) MONMSG MSGID(CPF0000) STRSBS ONWEB MONMSG MSGID(CPF0000) OnWeb Server and the Apache Web Server will be started automatically via the addition of STRSBS ONWEB. Incident Number: 2262363 Old KB# 14216#OnWeb#Rumba

This article describes how to translate French Characters between a Windows UI screen Character set and the Oracle Database Character Set. Problem: Using a graphical interface on Windows, the data you recover is not stored properly on your Oracle database using ProCOBOL, and you are losing special characters like "éàù". Resolution: Set up the following environmental variable before executing the runtime: Export NLS_LANG=FRENCH_FRANCE.WE8MSWIN1252 This tells the PROCOBOL code you have in your application that the IO with the COBOL program will be made with this Character set and that the data should be transformed before being stored on the database (to whichever Character set the database is set at). Your UI will now handle the standard Windows French characters properly and translate them when communicating with the Database. Old KB# 14259

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