Rocket® COBOL

Problem: Since applying SP2 to Windows XP our CGI programs run fine but they cannot be debugged/animated within Net Express. Resolution: We suggest you try the following: 1)  Log on to Microsoft's Windows Update and ensure your installation of XP is fully updated. 2) Disable the XP's internal Firewall. 3) Execute CBLCORED -I from within a Net Express Command Prompt.  This CBLCORED option implements a number of security tweaks that Microsoft recommend.  It is only active for the duration of the user being logged on to the machine i.e. a reboot or logging of the XP box will require the command to be executed again. 4) Enable CGI debugging from within IIS 5.5. Please contact Micro Focus SupportLine if you still have problems. Old KB# 4260

Problem: If the following MOVE-OBJECT-HANDLE causes strange behaviour, e.g. for a ListBox: SCREENSET-INITIALIZED ...     MOVE-OBJECT-HANDLE WIN-01 SM-HANDLE(1) Resolution: The object WIN-01 is not available at SCREENSET-INITIALIZED. So its handle cannot be moved. Move this code fragment to the WINDOWS-INITIALIZED dialog of WIN-01 and the handle of WIN-01 can be received. Old KB# 4248

Problem: This demo shows how you can use the SetParent Windows API to dynamically change the parent of a Dialog System window. Resolution: INTRODUCTION ========== This demo shows how you can use the SetParent Windows API to dynamically change the parent of a Dialog System window. SOURCE FILES: ========== Program Files         Description -------------------     ----------------------------------------------------------- SetParent.app Mainprog.cbl Copy Files -------------------     ----------------------------------------------------------- screenset1.cpb Screenset Files -------------------     ----------------------------------------------------------- screenset1.gs ========================================================== Keywords: demonstration, sample, example, demo, Dialog System, setparent.zip demo.ex demo.ne

Problem: Linkage parameters are not passed in a project with other CICS programs Resolution: Please check if you have the following directive in your project properties: CICSECM(). This directive should only be used with CICS programs.  If the programs where you have this problem are not CICS programs, you should remove the CICSECM() directive when you compile them. CICS uses the linkage in a very particular way.  In a CICS program you access to linkage using special CICS calls... so in this case your linkage parameters are there but you would need to use a CICS sentence to access to them. Old KB# 4271

Problem: This demo demonstrate how to invoke some of the basics functions of Microsoft HTML Help via API calls. Resolution: INTRODUCTION ========== This demo demonstrate how to invoke some of the basics functions of Microsoft HTML Help via API calls. SOURCE FILES: ========== Program Files         Description -------------------     ----------------------------------------------------------- HTMLDemo.CBL      Dialog System/Cobol program DSHTML.CBL COBOL programs using HTMLHelp                                API calls Copy Files: -------------------     ----------------------------------------------------------- HTMLDemo.CPB     Dialog System screen

Problem: A Cobol program is running under ES/JCL with Connect to UDB through XA. It calls a C (.dll) which includes embedded SQL. How must the C module be compiled and linked ? Resolution: Linking an operational "C" module as a .dll can be achieved through the Net Express Build process. Just add the object code produced by the "C" compiler to the project, and create a package type .dll from the .obj. In order to enable embedded SQL you need to include db2api.lib into the .dll. Please ensure that the CBLLINK utility also creates a .lib library and is exporting the entry points .exp. Old KB# 4268

Problem: What do you do if you cannot do exact placement of objects on a graphical Dialog System screenset window? Resolution: If you add new objects to a graphical screenset window and they seem to have a snap-to-grid behavior where you cannot place them exactly, then select the Dialog System Edit menu, Alignment menu, and notice the values for X axis and Y axis under the Grid increments group. You may need to change these values to 1 if you want exact placement of objects on a window. Old KB# 4258

Problem: Release 4.0: Below is a snippet of code produced by the OpenESQL Assistant. Some lines of code are included beginning with 'MOVE..'....but seem to have have been inserted incorrectly and should not be there: EXEC SQL              DECLARE CSR12 CURSOR FOR SELECT                      "A"."T$CONO"                    ,"A"."T$PTYP"                    ,"A"."T$YEAR"                    ,"A"."T$PRNO"      &nbs

Problem: Bei Anwendungen mit Ausgabe in eine zeichenorientierte Umgebung erscheinen die Umlaute im Allgemeinen falsch dargestellt. Das passiert typischerweise in Befehlszeilen oder in einer DOS box. Die Ursache liegt in der Verwendung des OEM Zeichensatzes im DOS Subsystem. Resolution: Zur Verbesserung der Darstellung kann Net Express in den ANSI Input Mode umgeschaltet werden. Das erreicht man in der Application Environment der Project Properties. Dann erscheinen z.B. die Umlaute eines DISPLAY richtig im Application Output. Läuft die Anwendung in einem Befehlsfenster, dann muss man die Umstellung in den Runtime Tunables vornehmen. Dazu braucht man eine Runtime Configuration File. Diese muss mit Hilfe einer Umgebungsvariablen definiert werden:   SET COBCONFIG_=d:\\path\\rtsconfig.cfg Darin wird der Schalter für die Umlaute gesetzt:   SET ANSI_INPUT_MODE=TRUE Old KB# 4245

Problem: Release 4.0: When installing Net Express with .Net the COBOL.NET Project Package is not installed and the error 'Package Load Failure' appears. Error message: Package 'COBOL.NET Project Package' has failed to load properly ( GUID = {DC88F376-25DD-49C8-99D9-1FD8AE484362} ). Please contact package vendor for assistance. Would you like to diable loading this package in future? You may use 'devenv /resetskippings' to re-enable package loading. Application restart is recommended, due to possible environment corruption. Resolution: The problem was in this case that the virus scanner Zonealarm prevented the installation from succeeding. After disabling this the installation went through ok. Old KB# 4264

Problem: This demo shows how to Get, Set and Redraw a Dialog System window using Win APIs Resolution: INTRODUCTION ========== This sample demonstrates how to change the attributes of a Dialog System dialog box...in this case, to make the dialog box sizeable by changing the window style. SOURCE FILES: ========== Program Files     Description ----------------     ----------------------------------------------------------- sizedlg.cbl          Main program source file. sc.cbl                 Subprogram that changes the attributes of the window passed to it. Copy Files: ----------------     ----------------------------------------------------------- ds-cntrl.mf         Dialog System control block. si

Problem: Multiple Line Text in Dialog System Push Buttons using Windows Styles. Resolution: INTRODUCTION ========== Multiple Line Text in Dialog System Push Buttions using Windows Styles. By default Dialog System truncated text on a Button when it is larger than the button size. This demo shows how to use Windows API calls in order to make the text go over multiple lines. SOURCE FILES: ========== Program Files            Description ---------------------     ----------------------------------------------------------- demo.cbl           setbuttonstyles.cbl Copy Files: ---------------------     ----------------------------------------------------------- thescreenset.cpb minwin.cpy winbase.cpy winclass.cpy winerror.cpy wingdi.cpy winnls.cpy wintypes.cpy winuser.cpy DS Scree

Problem: Version 4.0 If you have installed the Net Express 4.0 All Websync WrapPack 4.0.007 (all07n40.exe) and try to view an EBCDIC data file in the Data File Editor, you may not be able to switch from ANSI to EBCDIC to view EBCDIC data. This will occur if you have the "Find Text" toolbar open. This toolbar is visible if you choose the "Search" and "Find Text" menus when a source file is open in the editor. Resolution: Changes to the Text Find and Replace have caused the problem in all07n40. The workaround is to right-click on the Text Find toolbar and choose Hide from the popup menu before you open an EBCDIC file in the Data File Editor. The problem should be fixed in all fixpack releases and versions of Net Express after this fixpack. Old KB# 4257

Problem: Applications using the standard DOS character user interface use the DOS subsystem to display output text and data. In DOS the OEM character set is usually in place. Consequently some country specific chars will not be displayed correctly, especially the German Umlaute äöü. Resolution: You need to turn on the ANSI Input Mode. This can be achieved in the Application Environment of the Project Properties. The results of DISPLAY will then appear correctly in the Application Output Window of Net Express. If the application is to bel be executed in a runtime only environment, the appropriate Runtime Tunable can be set. The option ANSI_INPUT_MODE must be set to TRUE. The Tunables are defined in a Runtime Configuration File. An environment variable must be created to specify the configuration:   SET COBCONFIG_=d:\\path\\rtsconfig.cfg This method must be used in a Command Prompt before executing a RUNW. Old KB# 4

Problem: This demo shows how to swap the focus from a Dialog System window to a COBOL text window. Resolution: INTRODUCTION ========== This demo shows how to swap the focus from a Dialog System window to the COBOL text window.  This is important when you have an application which is made up from a mixture of GUI and character forms. SOURCE FILES: ========== Program Files     Description ----------------     ----------------------------------------------------------- TEST1.CBL         Main program which calls Dialog System. SPROG1.CBL      Example sub-program 1. SPROG2.CBL      Example sub-program 2. TEST1.GS           Dialog System screenset. Copy Files: ----------------     ------------------------------

Problem: The sample demonstrates how to create a Dialog System screenset which uses the Themed Controls of the XP Visual Style. Resolution: INTRODUCTION ============ This application demonstrates a method of using the Visual Style (XP-Style) controls in a Dialog System Application. REQUIREMENTS: ============= The APP requires Net Express 4.0 or a higher version. The demo should run on all Win 32 systems but will show the visual style only on Windows XP and later systems, where the visual style layout is activated. The Visual Style requires an EXE build of the start program, because the resource file must be linked in. I.e. it will not show the visual style in an INT or GNT build. OPERATION: ======== The Visual Style: -------------------- The same base name has to be used for the .RC resource file and for the EXE. The resource file can be edited using a text editor like notepad. Refer to the manifest file within the resource file. The NoBorder

Problem: Is it possible to send an HTTP Request to a Web Server which contains an XML file as the message to be sent by using Net Express with .Net and the HttpWebRequest and HttpWebResponse .NET Framework classes. Here is an example program written as a COBOL console application: Resolution:       $set sourceformat"variable"        program-id. Program1 as "testhttppost.Program1".        environment division.        configuration section.        repository.            class HttpWebRequest as "System.Net.HttpWebRequest"            class HttpWebResponse as "System.Net.HttpWebResponse"          &nb

Problem: Release 4.0: How can I get more  information about run time error codes used in Net Express? Resolution: Take a look at th following: Open the Net Express IDE -> Help -> Help Topics -> Index -> enter: 'RTS' and you should see this entry:  'error messages' After clicking you get back a sorted list by numbers ascending of all rts error codes used in this run time system. Old KB# 4266

Problem: Net Express 4.0 How to set the font size of a COBOL Text Window that has the System menu disabled: Scenario - a character-based program that is built with the graphical link option (cbllink -G), but has disabled the System menu, that allows you to set the font and size, by way of a call to the Win32 API SetWindowLong function. When this program is deployed to other machines, the user won't be able to select the System menu to set the font size. Resolution: The solution here is to enable the System menu by commenting out the call to SetWindowLong and then rebuild and run the program. Now, you should be able to select the System menu (in the upper left) of the COBOL Text Window, select the "Font Size..." menu, and select a font and size. Then select the "Settings..." menu and check on "Save font size on exit". Stop the program and run the Windows regedit.exe utility. The font settings will have been sa

Problem: Release 4.0: MFSORT - A file with ORG LS F 420 is read in and data is sorted with output in more than one file but the data in all the output files is truncated by the last 20 Bytes (all spaces) for each line. I don't want to truncate any trailing spaces. Resolution: 1) To prevent trailing spaces truncated at the end of each line you should add a configuration file extfh.cfg related to the Micro Focus File Handler. This extfh.cfg file is a text file edited by e.g. Windows Notepad ending with Enter (x'0d0a') for each line. In that case you write down this as follows: [XFH-DEFAULT] STRIPSPACE=OFF This configuration option STRIPSPACE=OFF (default: ON) ensures that for all line-sequential files you have addressed in MFSORT trailing spaces are present for each line. If you want to address a file (MYFILE.DAT) only you have to point this .cfg file as follows: [XFH-DEFAULT] [MYFILE.DAT] STRIPSPACE=OFF 2) Changing to the Net Express com

Problem: Client was running an executable that was creating a file. Each time it ran it should have created a new filename - but it kept creating the same filename. Resolution: At one time they had an environment variable for the file name in the project properties under the application button. The solution was to delete the rtecfg_....obj (most likely in working directory) and it take out of link properties in advanced "include objs" Then the EXE was rebuilt It's important that while testing environment variables that may change are only included in the IDE button and NOT the Application button. If they are included in the Application, the variable will be built into the executable. Old KB# 4242

Problem: Release 4.0: Getting compilation error when using alphabet-clause in a program which uses SET DIRECTIVES with ORACLE * Micro Focus Net Express            V4.0 revision 038           Compiler * Copyright (C) 1984-2006 Micro Focus (IP) Limited.      URN AXCGG/AA0/00000 * Micro Focus COBSQL Integrated Preprocessor * Net Express V4.0 Copyright (C)1984-2006 Micro Focus (IP) Limited. * URN AAAPA/ZZ0/00065 * CSQL-I-018: Invoking ORACLE8 Precompiler/Translator * CSQL-E-036: Unable to open the precompiler file: "C:\\uphv90.cs9" * CSQL-E-023: File Status  3/  5 Rebuild complete with errors ------------------------------ When removing the ALPHABET clause the programm compiles without errors Resolution: This was a problem with procob,  ORACLE's Pre-Compiler for C

Problem: Demonstrating the usage of the Dialog System Error Message File Handler, DSERRHAN. Resolution: INTRODUCTION ============ This project demonstrates using dialog system error handler "dserrhan". SOURCE FILES: ========== Program Files     Description ----------------     ----------------------------------------------------------- dseh.cbl             Program that loads the dserrh.gs screenset and the Dialog System error handler                           dserrhan.    dserrh.gs           screenset that demonstrates the dialog system error handler.   Copy Files: ----------------     ----------------

Problem: Supplying an argument or parameter to MFNETX /DEBUGPROJ (e.g. MFNETX /DEBUGPROJ:projectname arg) fails with an error that it cannot find the project. Resolution: Since spacey project names are allowed in Net Express, the MFNETX /DEBUGPROJ command treats the characters following the project name and space as part of the project name. To avoid this to happen, you simply need to quote the project name signifying that the following the closing quote is an argument, i.e. MFNETX /DEBUGPROJ:"projectname" arg Old KB# 4255

Problem: A customer in Brazil had a Character Dialog screen set with a field that converted automatically to upper case. However the characters 'áéíóú' were converted to 'áéí??' (the last two characters are box-drawing ones that do not display correctly with this software). Why did this happen? Resolution: The Windows API used by the runtime system in CBL_TOUPPER uses the Windows (ANSI) character set rather than OEM by default. In order to get the required conversion the customer needs to call PC_WIN_SET_CHARSET to get an OEM conversion. Details of this API are in the Net Express documentation.   Old KB# 4227