Rocket® COBOL

This article describes how to configure SQuirreL SQL Client to test the JDBC driver provided with Relativity Data Server. Problem: The Relativity JDBC driver is shipped with the Relativity Data Server. Also, a small Java application, DBSample, is included to test the JDBC connection. However, DBSample provides only a small amount of information that may be obtained from a JDBC connection. Resolution: SQuirreL SQL Client is an open source tool available from SourceForge. A PDF document is available which describes the many uses of SQuirreL SQL Client. See Related Links at the right for more information. Follow these steps to configure SQuirreL SQL Client for a Relativity Data Server JDBC data source. Copy the Relativity JDBC driver, RelJDBC.jar, from the distribution media to a convenient location. Following the instructions found on SourceForge, download and install SQuirreL SQL Client. Start SQuirreL SQL Client. Click on the Drivers tab. A large list of drivers is displayed. C

This article describes how to enable cursor blink when running Web-to-Host sessions on a Windows terminal server. Problem: When running W2H (Web-to-Host) sessions on a Windows 2003 terminal server, the display cursor doesn’t blink. Why is this, and how can we make it blink again? Resolution: For bandwidth conservation reasons, the cursor blink is disabled by default for applications running on a Windows 2003 terminal server. Perform the following steps to enable cursor blink: Make a backup copy of the registry. On the Windows Terminal server open the registry editor, regedit.exe. Select this registry key: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Terminal Server Right-click on the key, and select New | String Value. Type CursorBlinkEnable for the name, and set the value to “1”. Close the registry editor. Future terminal server sessions will now allow the Web-to-Host display cursor to blink. Note: This registry change will only w

This article addresses why the Close browser after session starts option no longer appears in the host wizard for Pro sessions, as it did in previous versions of Web-to-Host. Problem: In the Web-to-Host 5.2 Host wizard, there is an option to run a session in a separate browser window. This option would cause the session to load in its own browser window, while hiding the browser’s tool bar, menu bar, address bar, etc. This option had three sub-options, including Close browser after session starts. With this sub-option selected, the original browser window that was used to navigate to the Web-to-Host session would be automatically closed after the session started, leaving only the stand-alone session window. This is how the option appeared in the version 5.2 Host Wizard: This option no longer exists in Web-to-Host 5.3.2: Resolution: The same functionality can be achieved by selecting the Client Options 2 tab, and checking Start Zoomed: The result will be the same as with the pre

ACUCOBOL-GT options for mobile computing Problem: How can a PDA running Windows Mobile technologies best be utilized? Perhaps by connecting to a LAN using a wireless router and run thin client on the PDA?. Could this then run programs from the server accessing files to perform validation and write transaction data to the server? However, if the AcuThin files are copied to the PDA, and the application is launched, the message "'Acuthin' is not a valid Pocket PC application" is encountered. Is it possible to run Thin Client from a PDA? Resolution: Acucobol-GT can be used as a back-end for this type of solution; however, it is not quite as easy as installing Thin Client on a Pocket PC. You can use the following technologies as part of a mobile computing strategy: ACUCOBOL-GT COM Server ACUCOBOL-GT Common Gateway Interface (CGI) language extensions ACUCOBOL-GT runtime and Short Message Service (SMS) processing For a

This article explains how to delete one of more screens and their associated pages from the command line. Problem: From the command line, how can you delete one or more screens (and their associated pages) from an EnterpriseLink Repository? Resolution: In the same directory, create two files on Windows, using the file names and contents from the attached document. Note that the value for ELINSTALL should be replaced with your EnterpriseLink installation directory. Old KB# 14630#Rumba#EnterpriseLink

This article explains how to get more information about error message from sqlcode. Problem: When running a program, we received a number of SQLCODE = -2627 from an EXEC SQL INSERT statement. There does not appear to be much information about this and other SQLCODE values. How can it be resolved? Resolution: The SQLCODE -2627 is not a code which is returned by the Micro Focus OpenESQL run-time system. It is instead returned from the ODBC driver that you are using. The best way to get more information on these undocumented codes is to make sure that you include the following data item in your program: 01 MFSQLMESSAGETEXT pic x(256) When an error occurs, the actual error message text will be placed into this field so by displaying its contents you can find out the meaning of any ODBC error returned. You could also check the other fields in the SQLCA structure such as SQLSTATE to get more detailed information regarding the error that is occurring. In this c

This article explains why User Scripts are grayed out and cannot be enabled in the host wizard when creating a new session. Problem: When a new session is created in the host wizard, the Enable User Scripts option on the Keyboard Map, Auto Macro and VBA Scripting tab is grayed out and cannot be selected. Why is this? Resolution: In order to enable the user scripts feature, HLLAPI must be enabled for the session first. To enable HLLAPI: Select the HLLAPI Configuration tab in the host wizard. Select a Session Short name for the session. Select the Keyboard Map, Auto Macro and VBA Scripting tab. The Enable User Scripts option can now be checked. Note: The Session Short name for a session must be unique for all session instances. If more than one session will be running concurrently, they each must have a different HLLAPI short name assigned. Old KB# 14668#Rumba#Web-to-Host#OnWeb#ProClient

This article illustrates four ways to start a program containing spaces in the path or filename from COBOL. Problem: How can an EXE be started by a COBOL program when the path or EXE name contains spaces? Using a Move “My Path\\My Prog.exe My Parameters” to my-command-lineand trying to start the EXE by CBL_EXEC_RUN_UNIT will fail. Resolution: The attached demo shows four ways to start a program.exe with spaces in the path or filename. The main idea is that the path\\program has either to be included in quotes: Move ‘“My Path\\My Prog.exe” My Parameters’ to my-command-line, or Convert to short name following the 8.3 convention immediately before the program is called. You can use either a CALL “system”, or the WinApi CreateProcess, or the CBL_EXE_RUN_UNIT to start the EXE. Incident Number: 2352021 Old KB# 14614

This article explains how to resolve an error returned by a runtime query of a database table. Problem: When running a Database Table query we are receiving an error ORA-01403: no data found, when picx=varchar2 directive is specified, and even though the data is present in the table. The query is as given below: EXEC SQLSELECT CUSTOMER_NBR, CONTRACT_ID, CONTRACT_STATUS, EFFECTIVE_DATE, ACQUISITION_DATE, SETUP_DATE, CYCLE_DATE, LATEST_END_DATE, DT_FOR_INVOICING, PREBILL_SPAN, LATE_CHRG_DATE, LATE_CHARGE_NBR, BILL_DATE, COLL_FIRST_UNPD, CURRENT_AGED, LEO_STATUS, BRANCH_CO_NBR, BRANCH_NBR, SUSPEND_DATE, CLOSE_BILL_IND, LEO_INDINTO :ALF4000-CONTRACT :ALF4000-STAT-CDFROM CONTRACTWHERE CUSTOMER_NBR = :ALFSQL-CUSTOMER-NBR AND CONTRACT_ID = :ALFSQL-CONTRACT-IDEND-EXEC. Resolution: Use CHARF instead of VARCHAR in PICX directive: PICX Purpose Specifies the default datatype of PIC X variables. Syntax PICX={CHARF | VARCHAR2} Default CHARF Usage

This article provides an external C subroutine that you can use to set the mouse cursor. Problem: The mouse “wait” cursor is useful for indicating to the user that a process is busy. However, there is no built-in method to change the mouse cursor to the “wait” icon. Resolution: The attached zip archive contains a Dynamic-link library (rmcursor.dll) that implements two C subroutines that will allow you to invoke the mouse “wait” cursor and return the mouse back to the original, arrow cursor. Below is the syntax for invoking the two subroutines. To set the mouse cursor to “wait”: CALL "RM_SetCursor_Wait" To set the mouse cursor to “arrow”: CALL "RM_SetCursor_Arrow" Also included in the zip archive is a sample program (testrmcursor) that demonstrates the use of the mouse cursor subroutines. Old KB# 14608

This article explains how to resolve a 197 screen handling system initialization error. Problem: When running a batch job we are receiving the following messages: sh: line 1: cursor: not found Execution error : file 'ADIS' error code: 197, pc=0, call=1, seg=0 197 Screen handling system initialization error Resolution: ADIS checks for both screen input and output at the same time. For example, there has to be both screen input and output on the command line, even though there may only be DISPLAY statements in the program. While running in batch, System is missing the terminal definitions of stdin and stdout. Therefore, create an empty file with read permissions for everyone, then use: cobrun progx < empty_file > /dev/null & This is an example: $ cat start.shnohup sh -x run.sh & $ cat run.shecho $TERMecho $TERMINFOecho $COBTERMINFOcobrun test < empty > /dev/null $ cat test.cbl procedure division. display &quot

This article explains what to do if this error occurs when starting the Rumba UNIX display client. Problem: We are receiving the message API already in use error when starting the Rumba UNIX display client. (this applies to all the different host types, not just UNIX) The error appears as a message box and clicking OK clears the message and the software starts. How is this resolved? Resolution: Check what is set under Options > API Options > Identification/Configuration/Rename DLLs. You will see that it is not set to the default <None> but to a letter somehow. This error actually stems from the fact that all session short names on the desktop must be unique.   As noted in the help text "To use HLLAPI or DDE": This topic tells you how to configure your RUMBA display session for use with a HLLAPI or DDE application. From the Options menu, choose API. Specify whether you want to use this session with HLLAPI or DDE. To use EHLLAPI or WinHLLAPI Sele

This article describes how to modify AcuXDBC batch files to automate the process of removing public ownership of tables when populating the system catalog. Problem: Demo.bat and other supplies batch files automatically make the owner of the tables in the system catalog “public," yet many front-end applications require the owner to be blank. Which of the batch files need to be modified to make this correction, and what modification is necessary? Resolution: Add -o “” in the addfile.bat batch file to the xdbcutil commands:@echo offremrem Copyright (c) 2001-2006 Acucorp, inc.remrem======================================================================rem = addfile.batrem =rem = Usage: rem = addfile [-d catalog_directory] [-x xfd_directory] [-u user] filenamerem = addfile [-d catalog_directory] [-x xfd_directory] [-u user] -f listfilerem = -d specifies optional directory name to use for therem = System Catalogrem = -x specifies optional directory

This article explains why file status 9/065 occurs when a physical file is opened twice. Problem: We received file status 9/065 when trying to open a file on output mode . In the same program , the same physical file is opened in input mode with another file control name. We are using Server Express 5.1 and the same program runs fine with Object Cobol Developer Suite. Why is this? Resolution: File locking in OCDS did not take into account the fact that you might have two opens on the same file and so did not handle locks between the two opens. Under Server Express this is correctly handled. However, you can put the incorrect OCDS locking back in. For compatibility with OCDS you can use the tunable with the value FALSE. For example in the file $COBDIR/etc/cobconfig: set intra_prcess_record_locking=FALSE Remarks : In the file $COBCONFIG/etc/exthfh.cfg the following line must not be set : RUNITLOCKDETECT=OFF Old KB# 14631

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