Rocket® COBOL

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

This article describes the steps to add a macro to the OnWeb Web-to-Host toolbar. Problem: Web-to-Host doesn’t have options to add a macro to the toolbar as Rumba does. How is this accomplished? Resolution: It is possible to add macros to the Web-to-Host toolbar. The trick is to add a button on the toolbar and assign a macro to it. The following are the steps to add a macro to the toolbar: On a Web-to-Host session click on View > Toolbars > Customize to open Customize window. Click the New button to display the New Toolbar window. Enter the desired name for the new toolbar and press OK. The Customize Toolbar window will appear Click the New button to bring up the Button properties window. Select Macro from the Button Type pull down. Click on the Browse button and navigate to the location where you saved your macro. Select the macro and press the Open button. You will notice that the macro path is entered for you. Enter the Description an

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 how to specify a cataloged filename in extfh.cfg. Problem: How do you specify a cataloged filename in extfh.cfg? Resolution: Rather than map the physical filename, which may change from run to run, you can specify the unmapped filename in extfh.cfg using the internal keyword. To map SYSOUT for example: [internal:SYSOUT] INSERTNULL=OFF Old KB# 14579

This article describes how you can write constructors with different signatures in COBOL .NET classes. Problem: You need to define different constructors in a COBOL .NET class that have different signatures. Resolution: The following code gives an example of a COBOL .NET class that has different constructors: class-id. Class1 as "ClassLibrary1Cobol.Class1". environment division. configuration section. repository. static. working-storage section. end static. object. working-storage section. method-id. NEW. procedure division. display "ClassLibraryCOBOL.Class1 Constructor()" goback. end method NEW. method-id. NEW. procedure division using aStr as String. display "ClassLibraryCOBOL.Class1 Constructor(String)" goback. end method NEW. method-id. NEW. proced

This article explains what to do if a dictionary invalid error occurs when compiling a large program. Problem: When compiling a large program with a simple cob –u we get the followiong error: 912-S Internal error - Dictionary invalid r/w MULTISCREEN@ Inform Technical Support. Resolution: Check that there is sufficient space in /tmp. If /tmp has lots of cob* files directories, delete those and then try again. Old KB# 14590

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

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

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 to generate XML header information when running in CGI mode. Problem: A COBOL program that runs in background mode must write to SYSOUT so that it will be shown in a web browser. The problem however is that the output must be in XML format instead of HTML. The error indicates that the content type needs to be XML. How can this be done this using AcuCOBOL? This is what has been suggested for php: header ("Content-type:text/xml") But this is not something that can be done in the XML file itself, but must be set as part of the header. How can this be accomplished with the AcuCOBOL-GT Runtime? Resolution: Set this variable in the runtime configuration file or environment: CGI_CONTENT_TYPE=text/xml. This will direct the runtime to provide the specified value for the Content-type header that the runtime automatically generates. The runtime can also be prevented from supplying _any_ HTTP headers automatically. To do this, s

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 how to use a file of compiler directives without defining them on SDE. Problem: We use SDE to create, modify and compile COBOL modules. How can a file of compiler directives be used without defining them on the SDE menu? Resolution: SDE reads the file cobol.dir that is on the current directory. This is a example of a cobol.dir file : P(cobsql) end-c config=./config/mypcbcfg.cfg endp Some compiler directives are defined in the SDE menu, therefore the values of these directives that are defined in cobol.dir are not the values that are using by SDE . For example, to create a list file, the option list of the SDE menu must be used. Old KB# 14515

This article addresses the compiler error message reported for READ XML file with AT END condition specified. Problem: A compiler error is generated when a READ statement is coded for an XML file with organization is XML and the AT END/NOT AT END clause is present. Resolution: You cannot use the AT END/NOT AT END clauses when reading an XML file. Instead you should check the xml-file-status as follows: READ XML-FILE IF XML-FILE-STATUS = -7 *> end of file ... ELSE ... END-IF Incident Number: 2183877 Old KB# 14505

This article provides a walkthrough to add new locale to AIX 5.x. Problem: How can we add a new locale to AIX Server running Server Express? Resolution: A walkthrough of how one adds a new locale (Turkish in this case) to an AIX 5.3 installation. This method can be used on earlier revisions of AIX. Refer to attached Word document (smitty mle.doc). Old KB# 14484

This article explains how to uninstall a license for Server Express. Problem: How can a license for Micro Focus development system be deleted? I can install a license for Micro Focus development system with mflmcmd. Is it necessary to use mflmadm to delete a license for Micro Focus development system? Resolution: With all versions of Server Express older than 5.1, the license can be suppressed only with mflmadm. However, with Server Express 5.1 a new option U of mflmcmd allows you to uninstall a license. Old KB# 14499

This article explains how to use the C$SOCKET routine to connect to a Network Time Protocol (NTP) server and obtain a Universal Time. Problem: Sometimes it is useful to know the Universal Time so that the exact time and date can be provided to an application (for example to check license expirations). Resolution: The Universal Time is available from the internet thanks to NTP servers. The attached program shows how to use the C$SOCKET library routine to get information from one of these servers. Incident Number: 2284151 Old KB# 14461

This article provides information about the implementation date for the configuration variable A4GL-WHERE-CONSTRAINT. Problem: Although the Micro Focus Database Connectors User’s Guide documents the availability of the A4GL-WHERE-CONSTRAINT, it has not yet been fully implemented. Resolution: Currently, the full implementation of the A4GL-WHERE-CONSTRAINT is scheduled for version 5.1 WebSync 4 (WS4). Incident Number: 2285746 Old KB# 14493

This article describes how to use AcuXDBC to connect a string from an ASP project. Problem: Using AcuXDBC to connect a string from an ASP project sometimes generates the following error message: "Microsoft OLE DB Provider for ODBC Drivers error '80004005'[TOD][ODBC Driver]VISION: 'GENESIS_HOME' environment variable not found." Resolution: The key points to success in this process are the following: The installer sets the GENESIS_HOME variable in the USER environment, not the SYSTEM; you need to manually set GENESIS_HOME as a SYSTEM variable (copy it from the USER variable). Create a System DSN, using the AcuXDBC driver; name it “MY_DSN," and leave all options at their default settings, including configuration files set to “acuxdbc.cfg.” Create a virtual directory within IIS, leaving all defaults except "Execute Permissions:"; set this to "Scripts only".In that direc

This article explains what to do if OEM font special characters don't display correctly in Microsoft Access or Excel. Problem: When reading from a file in which data was written using OEM font information (usually from an old DOS character-based system), special characters like $ and £ do not display correctly in Microsoft Access and Excel. The special characters display correctly, however, when using the AcuXDBC utilities asql or odbcsql. Previously, AcuODBC had an option that allowed the character set to be chosen (ANSI or OEM); this option is not available in AcuXDBC. Resolution: AcuXDBC does not have the character map functionality that AcuODBC had. The resolution to this issue is to convert the OEM font data to ANSI font data, which will display correctly in Windows-based business intelligence tools. Old KB# 14512

This article addresses the Field Developed Solution MFFTP in the Mainframe Migration Toolkit. Problem: How do I resolve receiving an S806 error program not found when executing PGM=FTP or PGM=MFFTP? Resolution: The MFFTP support files are included as part of the Mainframe Migration Toolkit as a Field Developed Solution. If you have it installed under Windows, you will find the MFFTP files in the MFFTP directory of your Migration Toolkit. To resolve the S806 error: Install msdk08all.exe if it has not yet been applied. Copy the MFFTP.lbr into X:\\Program Files\\Micro Focus\\Net Express 5.1\\Base\\Bin (where X is the correct drive) and use PGM=MFFTP. To use FTP, set the Alias from ESMAC JES resources FTP Alias to MFFTP. Incident Number: 2285867 Old KB# 14506

This article describes a possible computational error when using fractional exponents and describes a potential work around. Problem: Upgrading to version 7.x uncovered a computational error that occurs when executing iterative mathematical statements that involve exponentiation with fractional powers, such as square root. For example, executing the following statement in a loop 50 times could cause the resultant value of MY-CALC-INT-A to equal 1 instead of the correct value of 3. COMPUTE MY-CALC-INT-A ROUNDED = 9 ** 0.5 Resolution: Upgrade to version 8.x or higher. A potential work around is available, but requires code modifications to the existing COBOL program source. To utilize this work around, an ON SIZE ERROR phrase may be added to the COMPUTE statement. For example: COMPUTE MY-CALC-INT-A ROUNDED = 9 ** 0.5 ON SIZE ERROR … Incident Number: 2264802 Old KB# 14459

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