Rocket® COBOL

This article provides a sample COBOL routine to display the HEXA value of COBOL variables. Problem: How can you retrieve and display the HEXA value of COBOL variables? Resolution: The routine named HEXAutil.cbl attached to this article will sh you how to retrieve and display the HEXA value of COBOL variables. Following is a sample COBOL program: ... linkage section. 01 aCobolVar pic x ANY LENGTH. procedure division using aCobolVar.... The test program callHEXAutil calls the routine HEXAutil: working-storage section.78 HEXAUTIL value "hexautil".01 anInt pic s9(9) comp-5 value 123456789.01 aStr pic x(40) value "0123456789abcdefghijklmopqrtsuvwxyz".01 aComp-2 comp-2 value 123456789.01.01 aComp-3 pic 9(9) comp-3 value 123456789. procedure division.working-storage section.78 HEXAUTIL value "hexautil".01 anInt pic s9(9) comp-5 value 123456789.01 aStr pic x(40) value "0123456789abcdefghijklmopqrtsuvwxyz".01 aComp-2 comp

This article provides an example for importing Namespaces within a COBOL project in MS Visual Studio. Problem: It is convenient to have imported namespaces in a COBOL project within MS Visual Studio so you can use classes belonging to a namespace without to specify it. How is this done? Resolution: On the COBOL project, right click, select Properties, then choose References and choose namespace(s) you would like to import. As an example, in the example code attached to this article, System.XML namespace was imported so you can directly use taking per example XmlDocument instead of System.Xml.XmlDocument leading to the COBOL .NET syntax to be lighter. A .ZIP is also attached to this article containing a Visual Studio solution with two COBOL projects: 1st project: named CobolImportNAmespaceNo and the namespace System.XML was not imported n the project 2ndproject: named CobolImportNAmespaceYes and the namespace System.XML was imported n the project

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

Created On:  12 January 2012 Problem: On 32-bit Windows systems, the default ODBC registry location that contains AcuXDBC information is HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBC.INI (System Data Source Name Definition), HKEY_CURRENT_USER\\Software\\ODBC\\ODBC.INI  (User Data Source Name Definition) and HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBCINST.INI (Driver Definition). For 64-bit Windows systems, the default ODBC registry locations are also HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBC.INI and HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBCINST.INI, which are used by the 64-bit ODBC drivers for defining the System Data Source Name (DSN) and driver. For 32-bit ODBC drivers, there is a secondary ODBC registry location, HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\ODBC\\ODBC.INI and HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\ODBC\\ODBCINST.INI which holds the 32-bit system DSN and driver definition.The confusion can come with User DSN’s as both the 32-bit and 64-bit ODBC administra

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 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 describes the procedure for disabling or enabling the automatic code suggestion dialog boxes in the AcuBench code editor. Problem: By default the automatic code suggestion (insight) features, code completion and code parameters, are turned on during installation. Some users do not desire this functionality and would like to disable it. Conversely, other users would like to enable this feature that has inadvertently been disabled. Resolution: Background information: The Code Insight functions are intended to facilitate source code creation, especially when working with graphical screens and reports. The code parameter feature displays hints (similar to the tool tips that appear when the mouse hovers over a button on a toolbar) for using certain COBOL verbs. Code completion provides pop-up lists of options to help complete some code statements and internal library routine calls. Code parameters and code completion are available for the follo

This article explains what you should do if you are not prompted for a password when using AcuXUI via thin client. Problem: When using AcuXUI via thin client and SECURITY-METHOD LOGON is set in the acurcl configuration file, the user is not prompted for a password. Resolution: This issue has been resolved by ECN-XUI059. Please contact Micro Focus Support to obtain the latest AcuXUI.jar file. Incident Number: 2351252 Old KB# 14661

Problem: When using the compiler directive RM"ANSI" to enable support for RM/COBOL source programs the default behavior of the ACCEPT statement is to sound an audible BEEP. This is the default behaviour for RM/COBOL programs and we would like to turn it off, how can this be done? Resolution: The BEEP can be prevented in two ways: Add the NO BEEP option to the ACCEPT statement. This is tedious for large programs. Use the (currently) undocumented compiler directive RM(NOBEEP), i.e. $set RM(NOBEEP) Incident Number: 2349342 Old KB# 14613

A file opened for I-O gets a 48,01 error when trying to WRITE. Problem: An indexed file is opened for I-O. The application can READ and REWRITE a record, but gets 48,01 when trying to WRITE a new record. 48,01 means that a file that is defined to be access mode sequential is open for I-O, or the file is open for INPUT only. Resolution: The problem is in the File Control paragraph FILE-CONTROL ACCESS MODE. In AcuBench, it defaults to “none”, which means sequential. The error message indicates that the runtime is trying to write to a file opened I-O, access sequential, which is not legal. Set ACCESS MODE to DYNAMIC and the problem is resolved. Incident Number: 2264513 Old KB# 14657

This article explains what to do if OEM characters aren't displayed correctly by AcuXDBC. Problem: When OEM font information is included in data returned by AcuXDBC to third party business intelligence applications, the characters display incorrectly. (With AcuODBC, this worked correctly when the “Character Set” option on the advanced tab was set to “OEM”.) Resolution: There is an undocumented option included in Version 8.1.1 of AcuXDBC that provides this functionality. Implement this by setting the OEM_CHARACTER_SET to 1 in acuxdbc.cfg. (This is not included in Versions 7.4.0 through 8.1.0, however, so upgrading to 8.1.1 is necessary.) Old KB# 14660

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 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 explains if WS-I Basic compliant WSDL can be generated by the IMTK. Problem: Net Express is being used to create Web Services and a WSDL file is being generated.The WSDL file generated is not compliant with WS-I standards. Is there any way to generate the WSDL file so that it is WS-I compliant? Resolution: The WSDL files generated by the IMTK (Interface Mapping Toolkit) first become compliant with WS-I Basic Profile 1.0 in Net Express 5.0 GA release. The WSDL files were not compliant in any earlier releases like 4.0. Incident Number: 2155191 Old KB# 14612

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

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 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 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 explains alignment in COBOL when using the EXTERNAL and SYNC clauses. Problem: What address is set to the data item in runtime if the SYNC clause is specified in 32 bit and 64 bit mode: a multiple of 2 bytes, multiple of 4 or multiple of 8? Does this depend on the data item being EXTERNAL? Resolution: There is no guarantee about the alignment of external items. Generally, there are 4 byte aligned in 32 bit mode and 8 byte aligned in 64 bit mode. The sync phrase is documented in the Language Reference Manual. Sync only has an effect when the directive IBMCOMP is also on. Old KB# 14615

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 provides instructions on programming numeric pad and – keys in VT Keyboard. Problem: When using VT320 terminal, the numeric pad does not map the "-" (minus) and " " (plus) sign correctly. The " " sign comes out as a "-" sign, and the "-" sign comes out as one of the Greek letters. How is this resolved? Resolution: Open a Rumba UNIX Display session and click on the Options > Keyboard menu. Select the Keyboard Strings option from the Function Keys drop down menu. Then press the Add button and it will open a new window. Press the – minus key in the Character to send field on the KB and press OK. Then click on the New button under Mapped To section and press Numeric Pad – sign on Rumba KB on the screen. Then press the Accept button and press OK. Press OK if you get the message to over write it. Repeat the above steps for the sign. This should allow you to send the numeric pad and – signs to the host when you type and – keys on the numeric pad.

This article explains how to resolve when LU1 print jobs sent to Rumba Printer print with misaligned data. Problem: When an LU1 print job is sent from the mainframe to the Rumba Mainframe printer, the output is not aligned as expected. For example, a printed form’s fields may not line up as expected, or some data may not be centered or justified as anticipated. This can be caused by null characters (0x00) being embedded in the original print job, as sent by the host. By default, Rumba printer will ignore these null characters and they will not affect the printed output. However, there are circumstances where it may be desirable to translate these null characters into spaces. Resolution: Rumba printer can be configured to translate null characters into space characters to preserve formatting. Perform the following steps to enable this behavior: Make a backup copy of the registry. Open the registry editor, regedit.exe. Navigate to the HKEY_LOCAL_MACHINE\\Soft

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 describes what to do when you encounter the AcuXDBC error message VISION: Too many columns. Problem: If you are creating a table and exceed the maximum number of columns allowed, the following message will appear: VISION: Too many columns XXX [max: 256]. XXX represents the number of columns being used, and the max is what is set in the AcuXDBC Setup/Advanced Tab. Resolution: In the AcuXDBC Setup: Advanced Tab enter the maximum number of columns you would like to be allowed in a single table. Valid values are 1 to 1024. The default value is 256. Incident Number: 2265138 Old KB# 14663