Skip to main content

Rocket® COBOL

Browse all forums dedicated to the Rocket® COBOL product family.

10000+ Discussions
Dominique Sacre
Dominique SacreRocketeer
 Rocket® RM/COBOL
How to safeguard against idle sessions when users do not logoff from the OnWeb Server

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

40
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® RM/COBOL
Dominique Sacre
Dominique SacreRocketeer
 Rocket® RM/COBOL
Unable to install EnterpriseLink on Windows Vista

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

60
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® RM/COBOL
How do I change the port for Relativity Data Server?

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

120
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
PowerTerm configuration

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

100
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® ACUCOBOL®
AcuXDBC server as a Windows Service

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

100
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® ACUCOBOL®
Translating French characters from a Windows UI character set to an Oracle database using PROCOBOL

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

110
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® RM/COBOL
Error 1904: failed to register NMSecComParams_dll file

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

60
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
License limit exceeded error message at logon

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

120
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
UNC path from a mapped network share's drive letter

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

40
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
187 Run-time system not found on $COBDIR path

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

50
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
Response Key Error: Internal error, please restart machine and try again

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

80
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
Development environment menu modification

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

40
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® ACUCOBOL®
Profiler utility for helping to improve performance

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

120
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
ASLMF errors when running on Hewlett-Packard operating system

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

150
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
Default behavior of how a runtime system looks for objects to run

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

50
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
RTS 173 when calling Functions belonging to shared library loaded with dlopen

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

50
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® Net Express/Server Express
Rebuilding the default runtime

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 &

80
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® ACUCOBOL®
C$JAVA Gives Error: Java dynamic init failed

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

110
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® ACUCOBOL®
Thread did not ask for message after accept terminated by one error

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

40
Dominique Sacre
Dominique Sacre
Dominique SacreRocketeer
 Rocket® ACUCOBOL®
AcuXDBC Version 8.0.0 Gives Syntax Error on CASE Query

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

10
Dominique Sacre
Show more activity

Recent badge winners: Your name could be next!

Explore all badges
Terms & ConditionsAccessibility statement