Rocket® COBOL

Created On:  14 July 2011 Problem: Executing programs in EXE outside of the Net Express IDE fail with a Semaphore Failure. The problem, however, does not occur if the program is linked with the static run-time or dynamically bound shared run-time. Here is the exact error message:   ASLM: Semaphore failureASLM: Errno 1000 Resolution: This error occurs when the application is using or picking up an older version of the run-time. For example, this error occurs if an application that was built with Net Express version 5.1 is executed with a Net Express version 4.0 run-time. There is no reason to run an application with an older version of the run-time, and unexpected errors may then occur when old run-time files are found in the PATH environment variable. Incident #2267278 Old KB# 14356

This article explains an ASLM 1013 semaphore failure when attempting to run a COBOL program or when using Application Server without world writable permissions for /var/aslmfsem. Problem: Without world writable permissions for /var/aslmfsem, the following error gets displayed when running an application: ASLM: Semaphore failure. Rerun as root ASLM: Errno 1013 What is the file for, and is there a way to remove the world writable permissions and still have an application run? The same ASLM 1013 semaphore failure also happens when attempting to run a COBOL program. Resolution: The message is normally caused by the missing semaphore file in /var/aslmfsem or the permissions on the file are incorrect. The aslmfsem file has a zero length so it can be created by using the following command: touch /var/aslmfsem The file permission should be rw_rw_rw_ (or R/W) for all and should be owned by root. If the file is present with the correct permissions the check the permiss

It's often a requirement to use arguments entered on the command line during the execution of a COBOL application; here’s a technique for capturing a varying number of arguments. Problem: How to capture a varying number of command-line arguments while executing a COBOL application. Resolution: ARGUMENT-NUMBER and ARGUMENT-VALUE are functions that can be defined in the SPECIAL-NAMES paragraph of a COBOL program. These functions can be used to retrieve the numbers and values of command-line arguments entered when the program is executed. The attached sample program demonstrates the use of these functions. These functions work in combination with the ACCEPT and DISPLAY COBOL verbs: DISPLAY UPON ARGUMENT-NUMBER establishes which argument should be manipulated, and ACCEPT FROM ARGUMENT-VALUE returns the contents of the command-line argument identified in ARGUMENT-NUMBER. ACCEPT VARIABLE FROM ARGUMENT-NUMBER returns the number of command-line a

This article resolves the message Load error: file 'lmfnewdb' when installing License Manager. Problem: When installing licence manager this error was displayed: Load error : file 'lmfnewdb' error code: 173, pc=0, call=1, seg=0 173 Called program file not found in drive/directory Resolution: The most likely cause for this error is that the environment variable COBPATH is set. Unset the COBPATH variable using the command unset COBPATH and run sh lmfinstall again. If this does not work, reinstall the License Manager database using lmfdbrecover. See the Development System Licensing Guide, Chapter 2, Recovering from corrupt Database. Old KB# 14317

This article addresses how to perform manual installs on client machines, specifically a silent install using the Windows group policy. Problem: It can be tedious to perform manual installs on client machines. Using the group policy it is possible to "push" the runtime to client machines silently, without prompts. Resolution: Follow these instructions to use the Windows group policy to perform a silent install: Put the runtime.msi and the liant.lic file on a network share available to the users who are supposed to get the software. E.g. \\\\<servername>\\NETLOGON (this is actually C:\\WINDOWS\\SYSVOL\\sysvol\\<domainname>\\scripts) Apply read rights for those users. Start the Group Policy Management program from the Administrative Tools in the Configuration Panel. Expand Domains. Expand your domain. Expand Group Policy Objects. Create a new Policy or select the policy you like to edit. Select Edit... from the Action menu

This article explains why a “Fail to open file: ncg.ops” error occurs in a Net Express project at link time, and what to do when this happens. Problem: A “Fail to open file: ncg.ops” error occurs when rebuilding a Net Express project. The Output window shows that the error occurs when Net Express invokes the CBLLINK command to link the program. Resolution: This problem occurs when the environment variable COBDIR is overridden in the project. Net Express uses COBDIR to find its own run-time files, so users have to be cautious when setting this environment variable in Net Express. Environment variables can be set in Net Express from the Project Properties under the IDE environment. The best practice is always to append a value to the existing value of COBDIR that can be represented by %COBDIR%. If users wish to append X:\\DIR to COBDIR, they should set COBDIR with the value: %COBDIR%;X:\\DIR Incident Number: 2278384

This article explains the impact of -g on performance when creating animatable executables. Problem: In order to have the ability to animate executable object formats such as .gnt or .so or executable, the "-g" flag must have been specified on the "cob" command when the objects were created. However, will the "-g" flag cause objects to run more slowly? Can you place the executables into production on a busy server, and run most often without animating, still preserving the ability to animate if necessary? And will the performance be acceptable? Resolution: When the -g cob flag is specified during the generation of .gnt or shared library or executable files, the extra debugging information is saved in the separate ".idy" file. The resulting executable does not increase in size. In actual fact, there is a small increase that is not substantial. With the debugging information saved separ

This article describes the method for applying a license to an installed Liant product, without, requiring a reinstall of the product. Problem: To apply a new license on your system, you will need to use the License Utility, which installs the new license into the existing license vault. This utility program, licverifyall, is located in the SupportTools subdirectory of the installation directory. Resolution: Note: You may apply a new license while users continue to use the application. Note, however, that for all the changes to take effect, you will either need to restart the application or, for some server-based applications, restart the service or reboot the machine. To apply a new license, follow these steps: Locate the product installation directory. Place the new license, *.lic, into the SupportTools subdirectory and rename it to liant.lic. Execute the licverifyallprogram located in SupportTools, with no parameters. The program will find the new license and the exist

This article describes what you should do if the Liant installer fails on Windows with the error message "The application failed to initialize properly (0x0000005)". Problem: The Windows RM/COBOL installer (setup.exe) can fail and return the following error in a Windows message box: "The application failed to initialize properly (0x0000005). Click on OK to terminate the application." Resolution: There is no single cause to these types of system configuration issues, but here is some guidance as to how you can diagnose these types of problems: Disable any anti-virus software while performing the install. Delete all of the files in your Windows temporary directories. The following link provides information on how to determine where your temporary directories are located: http://consumerdocs.installshield.com/selfservice/viewContent.do?externalId=Q108334&sliceId=1 This might be an issue with Windows Data Execution Prevention: In your Control Panel, open the

There are two options for installing RM/COBOL in a networked environment: 1. Perform a "Standard" or "Custom" installation of RM/COBOL on all of the PCs that will execute the COBOL application. 2. Perform an "Administrative" installation on a network share, then, perform a "Network" install on all of the desktop PCs. Below is an excerpt from page 54 of the RM/COBOL User's Guide in regards to the "Network" installation of RM/COBOL on client machines. This excerpt contains a short summary of the network installation process: -----------------------------------  Installation of RM/COBOL on Network Client Machines The RM/COBOL installation process for CodeWatch, Runtime, Recover1, and Compiler supports users who wish to install RM/COBOL on a network server machine and then install RM/COBOL on multiple client machines using the RM/COBOL installation on the server. First, install all of the RM/COBOL components that you need ont

When running a UNIX script (for example acuxdcbs.sh) the user may encounter the “syntax error near unexpected token” error. Problem: When running a script in either a Linux or UNIX environment, the user may encounter the “syntax error near unexpected token” error. Example: $ acuxdbcs.sh -start /acucobol810/bin/acuxdbcs.sh: line 50: syntax error near unexpected token `' /acucobol810/bin/acuxdbcs.sh: line 50: `show_usage ()' Resolution: This is typically caused by editing the file on Windows, or if the file is transferred in binary mode rather than ASCII. Run the dos2unix command on the script and then rerun the script. Example. $dos2unix acuxdbcs.sh dos2unix: converting file acuxdbcs.sh to UNIX format ... Incident Number: 2277959 Old KB# 14294

This articles describes several causes for an application that receives file status 35 on an OPEN OUPUT of a disk file. Problem: The application runs on a Windows XP client PC and occasionally receives file status 35 (File Not Found) on OPEN OUTPUT. The statement is creating a new disk file on a Windows 2003 Server which is accessed by the client via a mapped drive. The error happens unpredictably and is not reproducible at will. Resolution: There are many reasons why an OPEN OUTPUT of a new disk file may produce file status 35 (or 94,20 if you’re using 74 status codes). The following items may apply not only to Windows, but to any operating system. The SELECT uses a variable file name and the data item is blank when the OPEN OUTPUT is executed. The directory does not exist. Security settings are preventing the OPEN OUTPUT from creating the file. The file system is out of space. Antivirus, antispyware, or backup software is run

This article describes how to enable a disabled tab page at runtime. Problem: The tab control’s TabEnabled property controls whether an individual tab (page) on the tab control can be selected at runtime.  Using the WOWGetProp and WOWSetProp functions allows the enabled state of the tab to be set or retrieved at runtime.  Before getting or setting the TabEnabled property value, the CurTab property must be set to the zero-based index of the desired tab. However the CurTab property cannot be set to a disabled tab page so it’s not possible to enable a disabled tab page using the TabEnabled property. Resolution: You can use the WOWSetIndexProp function to set the TabEnabled property to true, for example: Call WowSetIndexProp Using Win-Return tab1 "tabenabled" win-true 1. Incident Number: 2278101 Old KB# 14344

This article tells you how to associate a function key with a button so that it executes the same code whether you press the function key or click on the button. Problem: Once a push button is defined, it is necessary to associate the appropriate code with the button so that when a function key (such as F7) is pressed, or when a mouse clicks on the push button, the proper response results. Resolution: Associating the exception value of the function key to be used with the push button enables the proper response when the key or button is pressed. For example, the value to associate with F1 is "1", and for F2 is "2", and so on. When using AcuBench, you make this association by modifying the exception value property for the button.  If you are not using the AcuBench IDE, you'll need to add the following code (with "7" representing a value) to the button definition: EXCEPTION-VALUE 7 Here's an AcuBench co

This articles describes how to remove the NO-TAB graphical control property. Problem: When a screen has several entry fields and the user needs to skip some fields. The program can set the 'NO-TAB' property on the desired fields using 'MODIFY' and it works properly. However, there is no way to reverse the 'NO-TAB' setting without exiting the screen. There is not an ON/OFF or TRUE/FALSE setting for the NO-TAB property. Resolution: The only way to remove the NO-TAB property from a control is to destroy the control and redisplay it without specifying the NO-TAB style. Also, if the purpose is to avoid stopping in an specific control, users can use the ENABLE property. Turning off this property will do the trick. This property can be turned on at runtime with the MODIFY verb. Incident Number: 2221196 Old KB# 14262

This article explains how to associate an ACUFH configuration file with a NetExpress project. Problem: Database Connectors uses an ACUFH configuration file; how can I associate this configuration file with my NetExpress project so that when the project runs, the ACUFH configuration file is picked up? Resolution: You can use the A_CONFIG environment variable to identify a personal ACUFH configuration file. For example: SET A_CONFIG=directory name\\file name. You can set this environment variable within the NetExpress IDE by following this process: Select Project > Properties. Click IDE. Add the environment variable A_CONFIG, and set its value to the location of your configuration file. Incident Number: 2259200 Old KB# 14283

This article describes how to set multiple values for Source Code Control options of the ACUCOBOL-GT compiler. Problem: Is it possible to use multiple patterns with –Si and –Sx compiler options? Resolution: To use multiple values, you can repeat the option: Ccbl32 –Si value1 –Si value2 –Si value3 program.cbl Or separate all the values with a semi colon: Ccbl32 –Si value1;value2;value3 program.cbl Incident Number: 2279382 Old KB# 14282

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 identifies different behaviours of "call system” between UNIX environments. Problem: The user program makes a call to system, for example: call “system” using “ls -la”On one system this works as expected, whereas on another it is necessary to add x“00” to the end of the command-line. For example: 01 WORK-COMMAND. 03 COMMAND PIC X(050) VALUE “ls -la”. 03 FILLER PIX X(002) VALUE X”00”.procedure division.CALL “SYSTEM” USING WORK-COMMAND.Why is this? Resolution: This behaviour depends on the case used in the CALL statement. call "system" (all lower-case) calls the OS system utility. This is platform specific, and may give unexpected terminal display results. When you are using the MF function CALL "SYSTEM" (upper-case) you must use x"00" to terminate the command. Incident Number: 2202924 Date: Name: Description of change: Date: Name: Description of change: Old KB# 14206

This article describes how to modify AcuXDBC table ownership with the provided batch files. Problem: Some ODBC front-end applications have trouble with the "public.tablename" format that is the default for AcuXDBC when it adds table information to the system catalog.  Frequently, when using Microsoft Access for example, an application cannot interpret the owner.tablename syntax, so an application error results.  Removing the "public" owner from the table specification is necessary for the desktop application.The AcuXDBC manual (section 5.3.1) indicates to use the -o "<space>" option of the XDBCUTIL script.  An example of how to automate the process when using script, demo.bat is provided below. Resolution: Here is a quick way to use the batch files provided with the software to make this change. In the bin directory, locate addfile.bat and open it in a text editor. There are two lines, which need to be edit

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

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

Micro Focus Virtual Environment Support Statement for systems such as VMWare, Citrix, Microsoft Virtual Server. Problem: Micro Focus Virtual Environment Support Statement – for systems such as VMWare, Citrix and Microsoft Virtual Server. Resolution: Micro Focus has no explicit support in its products for a virtual environment. Micro Focus relies on a 100% emulation of the environment by the virtual software vendor. Micro Focus International plc has many customers worldwide successfully using its products in virtual environments. Micro Focus will support correctly licensed customers who run products on a supported environment, irrespective of whether or not they are running in virtual environments. Virtual environment suppliers support a set of certified Operating Systems and Hardware, and the customer and their virtual environment suppliers will be responsible for any interactions or issues that arise at the Hardware or Operating System layer as a result of their use of virtual e

Problem: The File Handler Configuration File correctly specifies FILEMAXSIZE=8 and IDXFORMAT=8, but 4 Gb files cannot be created. Even though the correct settings seem to be specified in the file handler configuration file, files of size 4 gig cannot be created. Resolution: In order to create indexed files of size 4 GB or larger, the settings in the file handler configuration file must be specified correctly.  These settings are: FILEMAXSIZE=8IDXFORMAT=8 Note: When modifying this file, take care to preserve the case and the spelling. By default the file handler configuration file is named "extfh.cfg" and the system expects to find this file in the current directory.  As an alternative, the full path location, and the name of the configuration file can be specified using the EXTFH environment variable. Within the File Handler Configuration File, tags within square brackets are used to indicate which data files are affected by which configuration setti

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