Rocket® COBOL

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

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 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 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 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 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 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 how to fix compiler error CS1503 received when a C# program is calling a COBOL program. Problem: A C# program is calling a .NET COBOL program passing three parameters as its arguments. You receive error CS1503 in the C# program: C:\\Users\\ConsoleApplication1\\Program.cs(25,56): error CS1503: Argument '3': cannot convert from 'int' to 'MicroFocus.COBOL.Program.Reference' The C# program includes the following code: string unit = "102"; string msgtext = ""; int i = 0, r = 0; try { r = cblprog.PROG1(ref unit, ref msgtext, i); } catch(Exception ex) { Console.WriteLine(ex.Message); } The COBOL program includes the following code: Linkage section.01 unit-no usage string.01 return-msg-text usage string.01 test-int pic s9(9) comp-5.Procedure division using unit-no return-msg-text tes

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 describes an easy way to determine the processor level (software tier) of an iSeries system. Problem: IBM classifies its iSeries systems according to “Pnn” software tiers – P05, P10, on up to P60. It is not obvious what the “P” rating of a customer’s system is. It is not on the faceplate of the system, and may not be defined even in the system’s paperwork. Resolution: There is a simple command an operator can type that will provide the system’s “Pnn” rating directly. Bring up a RUMBA session (or whatever emulator the customer is currently using) and go to a standard menu screen and type in the command WRKLICINF. This will display the Processor Group at the top of the screen. Old KB# 14604#OnWeb#Web-to-Host#Rumba

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

The ACUCOBOL-GT runtime can manage different character sets other than the common Western European. Problem: Is it possible to use different character sets other than Western European in a COBOL graphical environment? Resolution: Yes, the ACUCOBOL-GT runtime enables you to change the locale of an application at runtime. When changing the character set, it is possible to accept and write into a Vision file characters that belong to different languages, such as Russian (Cyrillic), Greek, Turkish, Arabic and Hebrew. The attached program shows how to do this. Incident Number: 2351489 Attachments http://community.microfocus.com/cfs-file.ashx/__key/communityserver-wikis-components-files/00-00-00-01-22/0755.International.zip  Old KB# 14588

This article explains how the Server Express licensing works when using a clustered file system. Problem: Within a clustered file system, when the host falls over, will the Server Express runtime license broker (aslmf) automatically recover? Resolution: At the time this article was written (March 2009) Server Express is not cluster aware so if you fail-over to another machine, some interaction is required to ensure the licence database (mflmfdb) is licensed. This can be automated to a point by using aslmdbrecover, then apptrack in batch mode to populate the database. Note: Micro Focus does not test on clustered systems. Old KB# 14580

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 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 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 import business XML documents containing an unknown number of repeating items. Problem: Business oriented XML documents often contain an unknown number of repetitions of complex elements. For example, a web service based credit application processing system may return any number of credit acceptances, with each credit acceptance structure being complex. Another example would be a document representing a series of purchase orders, with each purchase order including any number of line items. If such a document is imported in its entirety, the COBOL data structure must use an OCCURS to describe the group data item that represents the top level repeating element. However, the OCCURS clause requires a fixed upper bound, and most XML documents of this type do not have a specified maximum number of repeating elements, thereby almost guaranteeing that some document will be presented that exceeds the maximum of the OCCURS clause. Resolution: Version

The RM/COBOL binding for PDFlib, included in the distribution of RM/COBOL, may be used to create highly complex PDF documents through a CALL interface. Problem: Modern applications are often required to produce PDF documents, for example as replacements for traditional printed reports or as a standardized mechanism to distribute documents via email. Simple solutions, such as printer drivers or external conversion tools, often lack the ability to control fonts or take advantage of intra-document linking and other advanced features of Portable Document Format (PDF), resulting in PDF documents that fail to meet user expectations for modern ‘look and feel.’ Many solutions also lack the platform portability required by RM/COBOL applications. Resolution: RM/COBOL includes a binding for the PDFlib API in the standard RM/COBOL distribution. PDFlib is a product of PDFlib GmbH; more information can be found on the PDFlib GmbH web site (see Related Lin

This article explains what to do when you get this error when loading support module librmterm.so. Problem: On Linux, the run-time reports:<install path>/librmterm.so: undefined symbol : TCSETATTRNOWRM/COBOL : Error loading support module. Resolution: Extract the attached fixed librmtc.so into the RM/COBOL installation directory. Also copy it to librmterm.so, that is: cp librmtc.so librmterm.so Incident Number: 2352024 Old KB# 14536

This article explains what to do if you receive an error -119 during installation. Problem: During installation, an error -119 indicates that the installer was unable to register a control or process necessary for the product to function properly. Resolution: Most frequently, this occurs when a virus protection program determines that a process is trying to alter the registry of the machine when it should not be doing so. The solution is to temporarily disable the virus protection program for the duration of time it takes to install the product. Remember to reactivate the virus protection software once the product is properly installed. Old KB# 14534

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 explains how to use the MS Word printout automation object from COBOL. Problem: The printout automation method in Microsoft Word allows you to print out specific page ranges from your application. However there are a lot of different options available for this method and most are not relevant for page ranges. How can you call this from COBOL ? Resolution: You can use OLE Named Parameters with the printout method to print a page range. An example of this is: mftech***** Use OLE Named parametersmftech invoke olesup "setNamedParameters" using by value 4 size 4mftech set wdPrintFromTo of ws-range to truemftech invoke theDocument "PrintOut"mftech using by reference z"Background"mftech by value -1mftech by reference z"Range"mftech by value ws-rangemftech by reference z"From"mftech by reference "1"mftech by reference z"To"mftech by reference "2" Before you use the “PrintOut

This article describes how to resolve an XML-code 201 error for XML PARSE when parsing data that contain German umlauts, French accented characters, or a charater that has an ANSI code larger than 0x79. Problem: When parsing data that contains German umlauts, e.g. äöüÄÖÜ or ß, French accented characters, e.g. àÀéèÉÈ, or a charater which as an ANSI code larger as 0x79 XML PARSE delivers an XML-code 201, which is "Miscellaneous XML document parsing errors". <ROOTELEMENT><GermanWords>Ärger Öse Übel -</GermanWords><ABitFrench>ètè means summer</ABitFrench></ROOTELEMENT> Resolution: These characters require the ISO8859-1 encoding specified in front of the root element: <?xml version="1.0" encoding="ISO8859-1"?><ROOTELEMENT><GermanWords>Ärger Öse Übel -</