Rocket® COBOL

GetOSInfo demo has been expanded to include Windows Vista, Windows 7, Windows 2008 and Windows 2008 R2 operating systems. Problem: The existing GetOSInfo demonstration illustrates older Windows versions such as 95, 98, NT, XP, 2000 and 2003. Is there a GetOSInfo demo available that illustrates the new Windows versions, for example Vista, 2008, 2008 R2 and Windows 7 operating systems? Resolution: The attached GetOSInfo.cbl demonstration file includes Vista, Windows 7, Windows 2008 and Windows 2008 R2 operating systems. Differences are marked with ‘mfsupp’ in that new source. This demonstration file was compiled under Net Express 5.1 WS3 and successfully tested against these operating systems. s. GetOSInfo.cbl attached GetOSInfo demo Vista, Windows 7, Windows 2008 Old KB# 14562

This article explains why a dialog box presents in the background rather than foreground. Problem: PC_PRINTER_OPEN will display a dialog box allowing the user to choose a printer. In some circumstances the dialog box is displayed behind another window. Why is this, and can it be forced to the foreground? Resolution: The PC_PRINTER_OPEN accepts a handle (HWND) that is made the parent of the dialog box. The box can be forced to the front by using the GetForegroundWindow API call to retrieve HWND of the current window and passing that to the PC_PRINTER_OPEN routine. Incident Number: 2353637 Old KB# 14573

This article explains how to activate the Database Connector component in Server Enterprise Edition 6.0 Problem: Having installed the runtime product Server Enterprise Edition 6.0 it will be necessary to activate the various components of the product using the various license keys and authorization codes supplied with the product. Database Connector is activated via two codes: a 16 digit Product Code and a 12 digit Product Key. How is this done? Resolution: In order to activate this component go to the Bin directory of the Server Enterprise Edition installation and identify the file activator. Double click on this file and you will be prompted to populate two fields; one for the Product Code and one for the Product Key. Old KB# 14593

This article explains what to do if the call to the C$SLEEP library routine is ignored when running in the debugger. Problem: When executing a program in the Runtime debugger the program’s call to C$SLEEP is ignored and the program immediately proceeds to the next statement. Resolution: The program in this case is multithreaded and the debugger was not set to run all threads. The resolution is to toggle the debugger to Run all Threads mode. This is done by entering “ra” at the debugger prompt or selecting the corresponding item from the Run menu. Old KB# 14542

This article explains EL00003 error when trying to use ODBC and an SQL Server database. Problem: Installation is completed and configured, however when trying to use the product the following error occurs: EL00003 EnterpriseLink Server: Cannot connect to the EnterpriseLink repository There is no problem connecting to the database directly using the ODBC driver but inside Enterprise Link the error occurs. Resolution: The ODBC driver that was installed came from EasySoft. This version of the software was not compatible with Enterprise Link. EasySoft provided an updated module and the problem was resolved. Incident Number: 2288909 Old KB# 14577#Rumba#EnterpriseLink

This article explains how to backup and rebuild files to resolve an RTS 114 error in mFFH. Problem: After upgrading from OCDS to Server Express an RTS 114 error in mFFH occurs randomly even though no code has changed and everything has been recompiled with Server Express. Resolution: Indexed files created by applications compiled with OCDS can occasionally cause problems when using the same applications that have been recompiled with Server Express. This is due to differences in the file handlers of OCDS and Server Express. The solution is to backup the files and then rebuild them with Server Express. Rebuild command: rebuild -d -e infile, outfile This rebuild command takes the input file, infile, and creates a new output file, outfile, from the data in infile. After running the rebuild, replace infile and its index with outfile: rm infile* mv outfile infile mv outfile.idx infile.idx If the problem persists after rebuilding the files please contact Micro

This article explains how to create an XML file which has include files. Problem: Can an XML file have include files? Is it possible to create an include instruction using COBOL XML-I-O? Resolution: Yes, this is possible. The include instruction for XML files look like: The DOCTYPE declares a file which then is included with the newly defined entity name testing: <!DOCTYPE wrapper [<!ENTITY testing SYSTEM 'testing.xml'>]> The include is done as: &testing; <wrapper> &testing;</wrapper> The include instruction can be written as PLAIN-TEXT: write frame-tag KEY PLAIN-TEXT"<!DOCTYPE wrapper [<!ENTITY testing SYSTEM 'testing.xml'>]>" For more information, see the demo attached to this article. Incident Number: 2285017 Old KB# 14518

This article explains how to rename a project from the command line. Problem: How do you rename a project from the command line in EnterpriseLink? Resolution: You can rename a project from the Administrators Site > Projects > Edit page. The web browser simply executes a CGI program distributed with EnterpriseLink to execute SQL statements to modify the ELRepository. It's possible (though unsupported) to invoke these SQL statements directly. Copy the following command into a file with a .bat suffix on Windows. Note that the value for ELINSTALL should be replaced with your EnterpriseLink installation directory. @echo offremrem RenameProject old-project-name new-project-namerem renames old-project-name to new-project-namerem update ELINSTALL with the EnterpriseLink installation pathremset ELINSTALL=d:\\microfocus\\enterpriselink506echo Project %1 renamed to %2, warning="@warning", error="@error" >message.txtset PATH_TRANSLATED=message.txtecho "a=1&server=EL

This article explains how to configure the date-entry control to display dates prior to 1930. Problem: The date-entry control is set to the SHORT-DATE format. When the user enters a date prior to 1930 the year changes. For example the user enters 1929 and the control displays 2029. Resolution: When using the date-entry control’s SHORT-DATE format for displaying the date, the CENTURY-DATE style must also be applied. Old KB# 14543

Setting the 'NO-TAB' property on a graphical control can be done using 'MODIFY' and this works properly. However, it is not clear if there is a way to reverse the 'NO-TAB' setting without exiting the screen. Problem: A screen has several entry fields and some fields need to be skipped based on information contained in other fields. The 'NO-TAB' property can be set on the desired fields using 'MODIFY' and this works properly. It is not clear if there is a 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 style from a control is to destroy the control and redisplay it without specifying the NO-TAB style. The same is true for the SECURE style available on an entry-field. A different option is to avoid the NO-TAB style and used the ENABLED property f

The F4-key does not generate an exception with a Combo Box control. Problem: Pressing <F4> while a combo box is active causes it to drop its drop-down list, and the COBOL program is not notified of an exception. Resolution: If the runtime configuration variable WIN_F4_DROPS_COMBOBOX is set to its default value of "1" (on, true, yes), then combo boxes use the standard Windows handling for the <F4> key. When this variable is set to "0" (off, false, no), pressing <F4> with a combo box active causes the COBOL program to get the exception, but the combo box does not drop its drop-down list. It is not possible to get both behaviors at the same time. Incident Number: 2191737 Old KB# 14526

This article describes an issue in accessing documentation from AcuBench help menu even though extend product documentation has been installed. Problem: After installing AcuBench the help menu item shows the appropriate documentation options, but nothing happens when they are chosen, even though the documentation has been installed on the machine – as can been seen by successfully accessing the documentation via the Windows Start menu. Resolution: This is typically caused by the helpfile.ini file pointing to a location other than where the documentation exists or the helpfile.ini not being present. When this occurs the options in the helpfile.ini need to be modified to point to the correct location for each of the help item options. For example: [MainHelp]AcuBench=C:\\Program Files\\Acucorp\\Acucbl810\\Docs\\acubench\\index.htmACUCOBOL-GT Manual Set=C:\\Program Files\\Acucorp\\Acucbl810\\Docs\\index.htmACUCOBOL-GT Runtime Manual=C:\\Program Fil

This article explains how to avoid having ENTRY-FIELD controls drawn incorrectly in a screen section. Problem: Starting with version 7.2.2 it is possible for ENTRY-FIELDS to be incorrectly displayed without an upper boarder. This behavior is caused by the combination of three events: The upgrade to runtime 7.2.2 from a previous version. A vertical size (LINES property) of the ENTRY-FIELD that is very thin (for example, less than 0,75 pixel or less than 1,10 cells). The ENTRY-FIELD is right justified using RIGHT property or using JUSTIFY_NUM_FIELDS environment variable set to TRUE. Resolution: There are several solutions to avoiding this behavior. One solution is to modify the code by resizing all the involved ENTRY-FIELDs. The amount of work that would be required in some cases may make this a non-viable solution. Another approach depends on whether or not the code can be recompiled. If recompiling is an option then use the -C71 com

This article explains an archive library error when running a script on AIX. Problem: A script is employed to build an RTS executable using the cob –x command. The script runs successfully on HP/UX but fails on AIX. On AIX, an error appears saying archive library CLAIMCHK cannot be found. The same cob -x command is used in each case. The archive library is specified on the cob –x using the following syntax: -l:CLAIMCHK.a Resolution: The “-l” option is accepted by the cob command, but cob in turn passes this option to the system linker "ld". The “-l” option is actually a feature of the system linker. For information about the “-l” option, consult the HP/UX and AIX Operating System documentation, and in particular the man pages for "ld”. On HP/UX, the linker "ld" accepts the syntax: -l:library That is, “-l” followed by a colon (:) followed by a library name. The "ld" ma

This article explains how to release a license from a client computer and return it to the Central License Server for Net Express 6.0 Problem: The license from a client machine needs to be added back to the pool of available licenses in the Central License Server. How is this done? Resolution: The license does not need to be revoked, as in previous versions of Net Express. When using the Central License Server, the license that is currently being used is released and returned back to the Central License Server once the product is closed. The license is only in use for as long as the product remains open. You can verify this by opening the License Management System and viewing the list of authorized licenses under the Licenses tab. The License Management System is found by going to Start > Micro Focus Studio Enterprise Edition 6.0 > Configuration > License Management System. The authorized license that was released will not be visible in the list. If you do no

This article provides an example of the use of the FUNCTION-ID paragraph with the RDFPATH and REPOSITORY directives. Problem: The FUNCTION-ID paragraph can be used in the IDENTIFICATION DIVISION to name an external function. When a program that uses this function is compiled, the following error message appears: 1304-S Method not found in repository Resolution: The RDFPATH should be used to compile the function program (mydouble.cbl in the example below) if the repository is generated somewhere different to the source folder. It should be used with the program that uses it (mymain.cbl) if the repository has to be searched somewhere different from the source folder or any of the directories in the $COBCPY environment variable (if defined). If both are used, the function and the main program are compiled with the same value in the RDFPATH directive, the 1304-S error message should not occur. The following example runs fine: cob mydouble.cbl -C RDFPATH=. cob c

This article explains how to resolve error 93 when accessing a file. Problem: When opening a file an error 93 is encountered saying: File locked by another user Resolution: There are three main causes of this error: Ungraceful exits. If the runtime exits in a manner that doesn't send a message to release the lock, the operating system will hold the lock until rebooted. On Windows Servers you can use the Administrative Tools > Computer Management > Shared Folders > Open Files to try to release locks on shared files. On UNIX/Linux copy the locked file to a different location, rename or delete the locked file and move the copied file back. For example: cp myfile ../myfile rm myfile mv ../myfile myfile Permissions problem. If the user has read-only permissions and the file is opened i-o this can cause the error 93. Other software having the file locked such as anti-virus or backup software. Inciden

This article explains how to add a new service to Enterprise Server from the local command line using and configuring mfdepinst. Problem: If you need to deploy a service to a number of servers, you might want to be able to do from the command line. You can use imtkmake to deploy your application, and this is well documented. imtkmake will pack all your application into a .car file and send it to the remote server, where mfdepinst will: copy the application files (*.int , ...) by unpacking the .car file copy the .idt file to a directory add a Package add a service assign Package and Listener to it do this on the right Enterprise Server do this on the right machine But how can you configure mfdepinst to assign another than the default path of the IDT file and to the service's Package and the right Listener to your Service? Resolution: When you use mfdepinst from the command line, there must always be a .mfdeploy file in the parent directory to the .ca

This article describes a work around to help Rumba users open a URL on a green screen. Problem: Rumba doesn’t open URL on an AS/400 display screen. Is there a way to do this? Resolution: Yes, there is a workaround to help you open a URL on a green screen. Follow these steps: Download and save the attached script to a desired location. On a Rumba AS/400 display click on Options > API and enter session short name “A” and press the OK button. Now click on Tools > Edit Power Pad to bring up the Power Pad editor. Click on the New button to create a new key. Under the caption section enter text for the new key. For example: “Open URL”. Change size and color as per your requirements. Under the When clicked section, select the Play Script option and click on the browse button to select the script. Browse to the location where you saved the attached script. Select the script and press Open. Then press OK and then press Save. Click on the T

This article explains how to enable the Transfer option within the Server Express Information Manager Utility infomgr. Problem: If the Transfer option in infomgr is not set up, how do you enable this within Server Express? Resolution: Infomgr is the Server Express Information Manager Utility and is a screen interface to the in product demo collection. Unless you have enabled the Transfer option, when you attempt to compile a demo, a warning is displayed as follows: The data directory has no write permission or is pointing to $COBDIR/demo. To maintain files in their original state, you should set-up the 'Transfer' option to copy the file(s) to a directory of your choice. If the 'Transfer' option is already set-up, the relevant file(s) will be transferred to the designated directory and compiled there on leaving this screen. If the 'Transfer' option is not available, you need to add the 'TRANSDIR' entry to the [mf-infomgr] section of th

This article explains why there is no Application Server license available at COBDIR when running an application with Java on an AIX platform. Problem: We have installed Server Express successfully and COBOL programs are running without any porblems. Java is installed correctly a Java program will run without any problems. However, when trying to do a combination of the two it throws up an error that there is no license available at the $COBDIR location even though it has been proofed that Java does run and COBOL runs as well. Why is this happening? Resolution: Check the user profile and especially 32-bit/64-bit paths as this has to be correct according to the type of license you have for your AIX machine. If you have a 64-bit license and a 64-bit AIX machine but somehow your user profile has a 32-bit path in there it will show the error that there is no license available at the $COBDIR location. Old KB# 14591

This article explains the method for running a COBOL program in the background of Windows. Problem: How do you run a COBOL program in the background when using Windows? Resolution: To run a COBOL program in the background use the –b runtime flag which inhibits the terminal initialization done by wrun32. This can be useful if the program is run in the background because terminal initialization can prevent normal use of the terminal by the operating system. If this flag is used, the behavior of ACCEPT and DISPLAY statements is undefined; therefore use this flag with caution. A program can examine the ACU-NO-TERMINAL field after an ACCEPT FROM TERMINAL-INFO statement to determine whether it was started with "-b". Incident Number: 2350874 Old KB# 14586

This article explains why copybook names with trailing spaces receive message 8-S Unknown COPY file "xyz.cpy" specified. Problem: When a copy statement appears in quotes with trailing spaces, for example: Copy file "xyz.cpy ", the compiler issues an error "Unknown COPY file "xyz.cpy " specified. Once the trailing space is removed, the compile works fine. Because the spaces are within the quotes, the compiler assumes that the spaces are part of the copy file name. This did not occur in previous versions of Server Express, why is it happening now? Resolution: This was a bug in previous releases of Server Express. Compile should never have resolved to the file xyz.cpy. The correct behavior is for the space to be considered part of the file name. The defect has been corrected in Server Express version 5.0 and all future releases. Incident Number: Old KB# 14520

Attempting to add a record to a Postgres database table using AcuSQL encounters errors. Problem: Attempting to add a record to a Postgres database table using AcuSQL encounters errors: SQLCODE = -1, SQLSTATE = 42000, SQLERRMC = Attempt to execute nonexistent, unprepared or invalid statement SQLIST. Resolution: With the more recent ODBC drivers for UNIX and Linux the ReadOnly entry in the odbc.ini file needs to be set to NO. Once this is done any of the operations that modify data in the table (INSERT, UPDATE, DELETE) will work without error. Incident Number: 2220456 Old KB# 14527

This article provides a solution for the device name not displaying in the status bar of an OnWeb Web-to-Host 5.3.1 pro client session. Problem: The associated device name is not displayed in the status bar when an OnWeb Web-to-Host 5.3.1 pro client session is launched in the browser. How is this resolved? Resolution: An OnWeb Web-to-Host session can be configured to use a specific device name or a system variable from which a device name can be generated. This device name is then displayed in the status bar after the session is established with the host. However, an OnWeb Web-to-Host 5.3.1 pro client session does not display the device name in the status bar after the session is connected. This has been fixed in OnWeb Web-to-Host version 5.3.2. We recommend that customers upgrade to version 5.3.2 if they have a need to display the device name in the status bar. Note: The device name may also be referred to as an LU name, a session name, or a user locator name in y