Rocket® COBOL

Problem: Is it possible to have more than 1 list view control in a Dialog window? Resolution: This is a Net Express 4.0 Dialog System project. A Dialog System Window is created with 2 (two) List View controls. These steps were taken to create this example: 1)  Start Net Express. 2)  Click File (menu), New (button). 3)  Click Dialog System Screenset in New dialog. 4)  Click OK (button). 5)  Click Yes (button). 6)  Click Browse (button) and navigate to the directory  where you want to work. 7)  Type a project name into text entry field 2 and click Create (button). 8)  Click Next (button) through the Wizard. You want all of the defaults. Click Finish (button). 9)  Click anywhere on the default dialog window to bring it into focus. Drag this window downward      so that none of it is hidden by the Dialog System menus and

Problem: How exactly do you setup Net Express and Visual Studio 6.0 to debug a Visual C/C 6.0 DLL from within Net Express? Cobol is calling the 'C' DLL. This is one of those situations where you must accept Microsoft Win32 limitations and adopt an  approach that is less intuitive. Under Microsoft Win32, only one debugger can be running at any time. You need both the Net Express development system and the Visual Studio system installed on the same machine. You need to make certain the Dynamic checkbox is checked in your Build Settings for your COBOL program(s). Merge your COBOL project into the 'C' project directory structure where the 'C' DLL project is located. Both directory structures have a Debug directory. Your COBOL application file (*.APP) and your COBOL source files are in the same directory as the 'C' source programs and workspace files. The Debug directory should be subordinate to this project directory.

Problem: When the following warning messages are issued when compiling a SQL application : 801-W External Compiler Module message ES1000 Use of EXEC SQL INCLUDE SQLCA END-EXEC.     12     05  SQLCABC         PIC S9(9) COMP-5 VALUE 136. *1209-I COMP-5 is machine specific format. (future occurrences not indicated) Resolution: The warning messages appear when compiling with the WARNINGS"3" compiler directive: 801-W External Compiler Module message ES1000 Use of EXEC SQL INCLUDE SQLCA END-EXEC. This warning message is required for ANSI certification.     12     05  SQLCABC         PIC S9(9) COMP-5 VALUE 136. *1209-I COMP-5 is machine specific format. (future occurrences not indicated) This message is due to the SQLCA structure contain

Problem: "Internal Error. Module c:\\Program Files\\Rational\\ClearCase\\bin\\cccmndlg.dll is using command ranges improperly. Please contact technical support." Resolution: Known problem with Clearcase, was reported to them in Jan'01 workaround is to create a shortcut with drive\\path\\mfnetx /RSRCCHKOFF or lauch Net Express from Net Express command prompt by typing mfnetx /RSRCCHKOFF This turns off resource checking. Old KB# 6925

Problem: In some cases it is necessary to run cblcored -i to modify the desktop security to be able to start animator with CBL_DEBUGBREAK. But the desktop security is restored each time the PC is restarted. Resolution: The easiest thing to do it would be to create a new shortcut in the Startup folder of that user that would have     Net ExpressPath\\Base\\bin\\cblcored.exe -i To create a new shortcut in the startup folder: Start / Settings / Task Bar & Star Menu / Advanced tab / Click on Add - Browse for cblcored.exe in the Net Express base\\bin subdirectory. add the -i option after the name of the file. Click on Next. - Find the Startup folder to place the shortcut in. Click on Next. - Give any name you wish to the shortcut. Click on Next. Old KB# 6912

Problem: Description: OLESUP method "adviseEvents" gets error 243 - class could not be loaded The class olesup cannot load the event handling class because the case of the event handling class name does not match the case of the class name in the program using olesup. When using the olesup "adviseEvents" method to register an event handler, keep in mind that the class names default to lower case. In this case, you should specify the class name literal in CLASS-CONTROL as lower case in the program where you invoke the "adviseEVents" method of the olesup class: CLASS-CONTROL.     MYEVENTCLASS IS CLASS "eventhandlerclass". If you specify the class name in upper case ("EVENTHANDLERCLASS"), then make sure that you add an entry in CLASS-CONTROL in the event handling class such as: CLASS-ID. EVENTHANDLERCLASS, INHERITS FROM OLEBASE-E.   CLASS-CONTROL.      

Problem: What is 4DOS and is it supported on Net Express? Resolution: Basically it has never been officially certified on Net Express and is, therefore, not supported. 4DOS will run on Windows 95, 98, or ME, and the associated MS-DOS versions (7.0 and above).  The equivalent for Windows NT, 2000 and XP is a product called 4NT. Here's a description of what it is and can do. By adding a wide array of features that DOS omitted, 4DOS makes the command line easy to use, giving you more power and flexibility than you ever imagined. 4DOS replaces the DOS command processor, COMMAND.COM - the brains behind your "C:\\>" prompt. 4DOS adds features such as shorthand "aliases" for commonly used commands, a pop-up directory history window, and the ability to copy, move, delete, or list multiple files with a single command. Simple command-line editing, history, and recall eliminates extra keystrokes, and the FFIND command can quic

Created On:  21 March 2011 Problem: When deploying a web service you get the following error in a dialog box:<html><head><title>Error - File Not Available</title><meta name="robots" content="noindex"></meta><body><h2>HTTP Error 404 - File Not Available</h2><p>The requested file is not available</p></body></html> Resolution: A 404 error at the beginning of the deployment operation almost certainly means that MFCS was unable to locate either the mfdeploy.exe program or one of its path components, or one of the path components in the PATH_INFO portion of the URL.Once the CAR file has been built and the server's deployment listener has been contacted, the deployment client (here the IMTK) does an HTTP POST operation to send the CAR file to the deployment receiver program, mfdeploy.exe. It uses a URL that specifies the virtual path to mfdeploy.exe and the virtual path to the dep

Problem: When converting a CGI executable program created with Net Express to an ISAPI .DLL to run as an IIS extension, you may receive an IIS Server 500 error response when the HTML action calls a program. Resolution: When converting a CGI executable to an ISAPI .DLL you must ensure that the main program being called is compiled with the directives $SET WEBSERVER(ISAPI) CASE REENTRANT"2" and this program must be linked with the Shared Multi-threaded run-time system. If this main .DLL calls any other COBOL subprograms or .DLLs then they must all be compiled with the REENTRANT"2" directive and they must also be linked with the same Shared Multi-threaded run-time system. Since an ISAPI application must be multi-threaded, the entire application must be multi-threaded. An IIS Server 500 error is seen because some of the subprograms within a .DLL being called by the main program were not compiled with REENTRANT"2" and they were li

Problem: Customer is encountering a problem in publishing a method in Web Services.  He's following the tutorial - compiles the Hello Word program, asteriscs it etc.  When he comes to creating the client part adding the Web Service part he says that the Hello World method is not published and he cannot see it. Resolution: This problem may actually occur with any service that is selected from the Add Web Reference wizard. This simply means that the file name extension (.asmx) was not mapped to any program or interpreter that processes that type file. Here are the steps to map that file name extenstion to the program or interpreter: 1. Find out if there are different versions of the MS .NET Framework installed on the machine 2. Determine which one (if there are more than one version) is the latest version by looking at the directory name (e.g. C:\\[Windows directory]\\Microsoft.NET\\Framework\\v1.1.4322 is more recent than C:\\[Win

Problem: Create an EXE program in NX and then under Project>Build Settings, select the Link tab and select 'static' and 'character'. The following program runs just fine with the following file supplied as a variable length sequential file and produces the output below: Resolution:       $set rdw nobound        Identification Division.        Program-Id.  LORINCE.        Environment Division.        Input-Output Section.        File-Control.            Select In1  Assign to 'Vli.Dat' Status is InFs.            Select Out1 Assign to 'Vlo.Dat' Status is OutFs.     &nbs

Problem: 173 ON MFEXTMAP.DLE Resolution: Release: 3.0   Advised:     remove ".dle" extension from call;     use the assign"external" compiler directive;     set Mfextmap environment variable in Project Properties, IDE. Old KB# 6814

Problem: The Source Control menu does not show Resolution: Release: 3.1   If PVCS is already installed and the PVCS portion for Net Express and the Source Control menu from Net Express, uninstall the PVCS portion and reinstall it. Old KB# 6817

Problem: Unable to apply filehandler FixPack Resolution: Release: 3.1   Create c:\\temp and have environment variables tmp and temp point to this folder. Old KB# 6836

Problem: Problem running old Workbench code with new Net Express code Resolution: Release: 3.1   I'm sorry but you cannot mix the Workbench product applications with applications created with Net Express.  They have incompatible and conflicting run-time systems. If you wish to run your application in Net Express then you need to recompile the entire system using Net Express.  Some of the run-time files between the two products, such as UTILS.LBR have the same name and so they cannot just be copied over. Old KB# 6804

Problem: Display not working when application built in Generic Release Mode - adis object Resolution: Release: 3.1   Change 'Interface Type' from 'Graphical' to 'Character' Attachments: FW_ Testing of Relativity EE.txt Old KB# 6854

Problem: Does Net Express support Microsoft ADO ? Resolution: There is no support for ADO via COBOL Embedded SQL as we support the ODBC standard via OpenESQL. You can however use ADO from Net Express applications as it is just a COM interface to the data. You need to use OLE Invokes to access the data. Note that Net Express with .NET 4.0 and later supports connectivity using ADO.NET. Refer to the Micro Focus .NET Help for further information. Old KB# 6807

Problem: Running the java demos and gets message about having to add the path to java com Resolution: Release: 3.1   If the file mfj.cfg does not exist in the Net Express\\base\\bin directory, you'll have to create it. Use a text editor to create the file and add the full path and name of the java compiler on one line. Old KB# 6808

Problem: Incorrrect results from elementary numeric move operation. Resolution: Release: 3.1   Use comp with no trunc instead of comp-5 Attachments: (Trunc Program-ID) 20080129.rar Old KB# 6811

Problem: Release: 3.1   Inserted 3999.999999 from sqlplus into number(15,6) came out 4000, in program came out 3999.999999 which is correct results. Resolution: SQLPLUS has setting numwidth whose default is 10 , it will round to display 10 digits. This is why sqlplus showed different results than program. If set numwidth to 15, then sqlplus shows same results as program, which is the value stored in the database. Old KB# 6870

Problem: Status of the support of Btrieve files by Net Express Data File Editor. Resolution: Although the File Hanlder still support Btrieve files the Data File Editor and the Data File Convert no longer supports Btrieve files. This information is for Net Express v3.1 and above. Old KB# 6846

Problem: Echo to STDERR Resolution: The STDERR Compiler directive only applies to the compiler's behavior and should only be used if you are compiling from a command line. It is not going to be effective in the IDE. Attachments: banner_strat_66aa44.gif Old KB# 6828

Problem: Error 114 on file '...\\check.lbr\\CMD.gnt' Resolution: Release: 3.1   This problem is fixed with the compiler fixpack cmp08ne31.exe Attachments: alert_rmw21.log Old KB# 6815

Problem: Compatibility with Net Express v2.0 & v3.0 Resolution: Release: 3.0   There's an online book called Migration Cookbook for some reference, regarding features that could have been omitted or changed from previous compilers (like Object Cobol, Workbench, Net Express 2.0 products). However, we recommend that you recompile all your programs, initially, using REBUILD ALL.   Then when given new amended source codes/patches, just do a REBUILD for those files.   Only the parts of your project that have changed (including files that are dependent upon changed files) are rebuilt. Old KB# 6855

Problem: INTERNAL ERROR PLEASE RESTART MACHINE Resolution: Release: 3.1   Spelled out procedure: 1) uninstall 2) reinstall 3) apply clu01n31.exe 4) start Net Express. etc. Old KB# 6830