Rocket® COBOL

Problem: When setting MFCSCFG to a path that contains spaces, mfclient does not seem to find the configuration file. Resolution: Long directory name is not supported even if it is quoted. Use the short name instead, e.g. "C:\\Program Files" --> "C:\\Progra~1" You may want to look at a demo (longname.zip), which shows how to return a short filename (or directory name) from a long file name under COBOL using the WIN 32 APIs. Demos can be found at the Example & Utilities page from the Micro Focus SupportLine site (http://supportline.microfocus.com) Old KB# 1417

Problem: There are many differences between the Object-Oriented language extensions that are provided in the .NET checker and the unmanaged COBOL checker. Resolution: The unmanaged COBOL compiler actually supports two methods of writing Object-Oriented COBOL. The first method uses syntax that was developed by Micro Focus before the ISO2002 standard defined its own syntax. These extensions are known as the Micro Focus alternative syntax and makes heavy use of the Net Express class libraries. The later syntax is known as the ISO2002 syntax and it uses a repository section to hold all of the class and method information. Old KB# 1511

Problem: Release 5.0: After installing Net Express 5.0 and trying to run an application compiled within the IDE as well it seems this F5 key does not work as expected, because CTRL F12 binds the run functionality now. Also, the tooltip for the "Run"ner button shows CTRL F12. What to do getting back this F5 keystroke to "Run" an application? Resolution: To resolve this issue take a look here: Net Express 5.0 IDE-> Options -> Customize IDE... -> Keyboard Configuration -> Load Scheme Binding "Run" to F5 is related to this MS.KEY file covering Microsoft's scheme, and picked up from the Net Express installation here: ..\\Net Express 5.0\\Base\\bin\\MS.KEY Old KB# 1498

Problem: How can you interact with a FTP Server from COBOL on .Net ? Resolution: The .Net framework V2 introduced some new classes that allow developers to easily use FTP programmatically. The FTP classes are located in the System.Net namespace. There are 2 main classes involved. You need to create an instance of FtpWebRequest containing the details of the FTP request you need to perform. You then need to use the FtpWebResponse class to receive the file you are attempting to receive. If you are accessing an FTP server that requires logon then you can specify login details using the System.Net.NetworkCredentials. An instance of this is returned from the FtpWebRequest "Credentials" property. Attached to this article is an example showing how to use these FTP classes from COBOL. You will require Net Express V5 and Visual Studio 2005 in order to this example. The demo is attached. Attachments: FTPSample.zip Old KB# 14

Problem: A dll was created  in Netexpress 4.0 for .Net to access our Isam files.   This dll is called from a Web based application.Experiencing performance issues when accessing the Isam files. There can be up to 100 users accessing the files at the same time.  Also are there tools to monitor file access performance? Resolution: A setting change in the System icon will help with file I/O perfromanance. Goto the Control Panel Open up System icon. Click on the Advance tab In the  Performance section, click on Settings In the Performance Options window, click on Advanced tab In the Memory Usage seciton, change setting from Programs to System cache This will help with file I/O performance. Tools for monitoring file access performance. There is a Microsoft website , SysInternals, that has utilities for file monitoring that could help with file I/O performance. Here is the url: http://www.microsoft.com/

Problem: Customer runs Fileshare as a service on 2 separate machines. The name of the Fileshare service is the same on each machine. Since installing WS03, whichever Fileshare is started last gets and error: FS077-S A Fileshare Server of the same name has already been defined - the Fileshare Server is closing down. Resolution: Go to ES Admin > Configure > Options > General and uncheck 'Generate UDP Broadcast Search Requests' on all machines. This will prevent the Fileshare Server from broadcasting its presence to other MF Directory Servers and will allow Fileshare Servers of the same name to run on separate machines. Old KB# 1464#RMCOBOL#ServerExpress#netexpress#AcuCobol#COBOL

Problem: CANCEL statements used inside a class program cause the compiler to loop and produce the following error in Net Express 5: "Error 912 : Internal error - Dictionary invalid r/w Inform Technical Support" Resolution: This issue has been fixed in WrapPack 3 (a.k.a WS3) and is available at the Micro Focus SupportLine site (http://supportline.microfocus.com). The name of the file is NXP3250030082.MSP. Note: Please make sure to read the important instructions in the WrapPack's description before applying it! Old KB# 1424

Problem: After calling CBL_DIR_SCAN_START with return code of zero, CBL_DIR_SCAN_READ fails with return code 127. Resolution: Make sure the path provided in CBL_DIR_SCAN_START does not contain any double quotes. If you called CBL_GET_CURRENT_DIR to get the current directory and the path contains spacey directory name, the returned path will be quoted (e.g. "C:\\Documents and Settings\\UserID\\My Documents\\My Current Directory"). If you use this quoted path in CBL_DIR_SCAN_START, it would return a zero return code, but CBL_DIR_SCAN_READ will fail with return code of 127. Old KB# 1444

Problem: Application was built with Net Express 4.0 that had all07n40 wrappack applied. Resolution: This message indicates that the application server 4.0  is back  level from the development machine which is running all07n40 so they need to apply aps09a40.exe. aps09a40 is the first Appliocations serv er version to have CTF enabled. http://suppportline.microfocus.com Sign in and select "click here for latest software updates" or "patest and fixes" Under Micro focus servers select "Application Server for Net Express 4.0 / Applications Server for Net Express with .NET". By looking at the description you can find the version of application server that will match the development version you are using. Old KB# 1457

Problem: XML document & COBOL -  accepting XML string through linkage - (using COBOL SELECT statement to use buffer area (address using "WSDATA") -  in XML file, between start of document event and end of document, parsing halts with "Exception error 102" message while searching for root element. Resolution: XML exception error 102 parsing error is to be expected in this scenario.  The parser reached the end of the document while looking for the root element. With XML exceptions, no further events are returned from the parser, even if you set XML-CODE to zero and return control to the parser after processing the exception. Control is passed to the statement that you specify on your NOT ON EXCEPTION phrase or to the end of the parse statement if you have not coded a NOT ON EXCEPTION phrase.  Solution:  Include the NOT ON EXCEPTION phrase. Old KB# 1482

Problem: The following error may occur if you are trying to invoke a C function from COBOL with NetExpress 5.0 and Visual Studio .Net 2005 (C) installed.   "Runtime Error! Program C:\\NetExpress5.0\\BAse\\Bin\\RUN.EXE R6034 An Application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information". This error occurs when trying to set the entry point in the COBOL program as it tries to invoke an (exported) function of the DLL. The C DLL is built from .obj files, linked together with link (v8 link). The .obj files are built , from the VS2005 command line, using cl.exe. The problem occurs only when /MD is specified in the command line of cl.exe. The problem does not occur on when running NetExpress 4.0 and Visual C Studio .NET 2003. Resolution: Consider the following commands being run from the VS2005 command prompt: cobol caller.cbl,,,, GNT(&q

Problem: The aim of this demonstration is to show "How can a Cobol program consume an EJB deployed on a Java Application Server". First question: Is it possible? ( OO Cobol EJB Client <-> EJB home Interface <-> EJB remote Interface <-> EJB [Bean] ) The answer is NO, Not directly it is not possible to invoke a instance of an EJB from Object COBOL, due to the Object COBOL Java domain not support "proxy classes". How to Proceed then? Use a Java Wrapper which will communicate with the EJB. This will be possible: ( OO Cobol Client <->  Java EJB Client STUB <-> EJB home Interface <-> EJB remote Interface <-> EJB [Bean] ) Resolution: Environment used in the context of this demonstration Weblogic 8.1 Net Express 5.0 Websync3 ==> Demonstration is  in the .ZIP attached to KB more comments in the ..DOC file in the .Zip file which d

Problem: The COBOL code attached just does what's pasted below  which is a VB code OL2000: How to Programmatically Change the Displayed Calendar Date http://support.microsoft.com/kb/259767 some more glue regards to Outlook Object Model Overview http://msdn2.microsoft.com/en-us/library/ms268893(VS.80).aspx http://msdn2.microsoft.com/en-us/library/aa221870(office.11).aspx VB sample: Dim ol As Object Dim olns As Object Dim oCalendar As Object Dim oAppt As Object Dim oViewCmdBar As Object Dim oItem As Object Dim nItem As Integer Sub ChangeCalendarView()    ' Create Outlook Application object.    Set ol = CreateObject("Outlook.Application")    Set olns = ol.GetNameSpace("MAPI")    ' Retrieve the Calendar folder.    Set oCalendar = olns.GetDefaultFolder(olFolderCalendar)    ' You can retrieve your specific a

Problem: The following error is occurring in Net Express 5.0, Wrappack 4(WS4 :) ----- Form Designer requires Microsoft Internet Explorer 4.01 or greater to be installed on this system. See Installation Notes for more details. Form Designer cannot continue. ----- Resolution: WrapPack 3 (WS3) of Net Express 5.0 contains the fix for the issue with Internet Explorer 7 (IE7). However, the same fix is NOT unfortunately included in WrapPack 4 (WS4). WrapPack 3 (WS3) --> NX3250030082.MSP WrapPack 4 (WS4) --> NX3250040064.MSP It is likely that those who have applied WS4 on Net Express 5.0 that did not previously have WS3 will not be able to start Form Designer and will see the error message above. If WS3 was applied before WS4, then this problem will not occur. Please follow the steps below to resolve this problem: 1. Uninstall WS4 (see below the uninstall steps)    a. go to Start | Control Panel | Add or Remove Programs   &nbs

Problem: Can the selected tree view item be displayed in light blue? Can the tree view items be colorized individually? Resolution: To do this you have to derive your own tree view class from the standard tree view and use this class in the class control paragraph of your tree view control program. You find a sample "owndrawtreeview" as attachment. ------------------------------------ The "owndrawtreeview" defines a method "wmGadgetNotify" which handles a redraw of the tree view items in the desired style. "owndrawtreeview" sample shows any level (up to 6) of the tree view items in a different color and shows the selected item in light blue and underscored style. The background of the selected item is white or yellow depending on the line, which is commented in. ------------------------------------ To use the "owmdrawtreeview" in your application, he class declaration in the control program has t

Problem: Does Net Express 4.0 IDE support Windows XP Pro 64 bit? Resolution: Net Express 4.0 is a 32-bit application, and 64-bit operating system are supposed to be able to run both 32-bit and 64-bit software. l Net Express 4.0  can be installed on a 64-bit operating system . Information about operating system support can be found in the Net Express readme (click on Start | All Programs | Micro Focus Net Express version | Readme, double-click on Installation Notes under Contents, and click on Hardware and Software) Installation instructions are as follows: This only applies to NX development not .NET To be able to install Net Express v4.0 on an x64 or Itanium environment you need to follow the provided set of instructions. 1) Copy the entire Net Express v4.0 CD to a temporary folder on your workstation. For example, NX40 2) Because of the 32-bit compatibility mode, the default installdir location contains "(x86)" which is not allo

Problem: Open i/o on a file getting status 9/57, when animating or running under debug build type. When running under release build type, Do not get the 9/57 error. Resolution: Error was resovled by adding the following to the Select Statement on the file that recieved the 9/57 error.   LOCK MODE IS AUTOMATIC          SHARING WITH ALL Old KB# 1468#COBOL#ServerExpress#RMCOBOL#netexpress#AcuCobol

Problem: was trying to generate clients and gets compile problems when doing a generte web service client - the generation recompiles the program - Resolution: The problem here was that the project is a mainframe migration project using pcommain that was setting mainframe dialect(entcobol)  - It may compile clean when just compiling from the project window - because it does not know you are going to make a web service from it. when generating a client from the Open Services Interface window it recompiles the program this is where it will not accept the mainframe dialects. Web Services cannot use entcobol - 2 options: create a separate project for programs that will be web services and do not use pcommain -or- find the programname.dir and place a &space at the beginning of the line for directves not to be used (making the directive comments) - so it will not be used Old KB# 1441

Problem: The demonstration attached uses the Microsoft APIs to ' I-O'  on named pipes Microsoft URL / named pipes:       http://msdn2.microsoft.com/en-us/library/Aa365590.aspx Microsoft URL / named pipes->PipeReference->Pipe Functions :      http://msdn2.microsoft.com/en-us/library/aa365781.aspx Resolution: A .ZIP is attached. For the simplest, 1) Unzip the attachment on a working directory 2) Open a Net Express command prompt 3) Compile the sources files, just launch DOcl.bat 4) Open another  Net Express command prompt session, just type start in the 1st DOS session 5) Launch the PIPE server in DOS session 1 ( run STARTpipeserver ) this 'PIPE' server will create a named pipe and wait for incoming requests from 'PIPE clients' 6) Launch a "PIPE client   in DOS session 2.  ( run MSG2pipeserver ) Th

Problem: External file mapper (mfextmap) seems not to work in a managed (.NET) application). Resolution: 1. MFEXTMAP is not supported in .NET 2. Use app.config (i.e. set environment variables) instead to avoid having multiple configuration files as in using external file mapping 3. It may be overwhelming to think of setting each one of the dd names as an environment variable in the project settings, but this can be done outside of Visual Studio. You may want to build your own program or script to import your MFEXTMAP.DAT file into the app.config file Here is a content of an app.config file: ----- <?xml version="1.0" encoding="utf-8"?> <configuration>   <configSections>     <!--The following code declares a section group for application configuration -->     <sectionGroup name="MicroFocus.COBOL.Application">      &nbs

Problem: Receiving sqlcode -19514 on DELETE statements, when re-submitted it then works. Using Net Express 4.0 and Oracle ODBC Resolution: This was an issue that was corrected in all08n40 all websync wrappack    o  The OpenESQL run time was updated to resolve an issue with        searched DELETE statements that were incorrectly returning a        "19514 Cursor is not prepared" error. Old KB# 1410

Problem: Compile fails with RTS114 in prexml.gnt when building .NET console application with a web reference Resolution: Compile fails with RTS114 especially when a web service is included and "p(prexml) endp" is set in the COBOL settings. The Preprocessor should only be called to parse XML source file only. Remove "p(prexml) endp" from the global setting and set it instead at the beginning of the COBOL file that contains XML syntax:       $set p(prexml) endp The XML pre-processor and .NET web services can exist in the same project as long as the preprocessor is not being used to parse source file that has non-supported syntax. The pre-processor does not support classes and .NET codes. Old KB# 1414

Problem: How do you uninstall a Wrapack for Net Express v5.0 ? This resolution also applies to Mainframe Express v3.1 and Micro Focus Server v5.0 Resolution: As of late 2006 and early 2007 Micro Focus is using Microsoft installation tools to install products and subsequent fixes commonly known as WrapPacks. If/when you need to uninstall a WrapPack you will need to do the following; - Go to Control Panels - Select Add/Remove Programs - When the Add/Remove Programs window appears ensure the the List Upates checkbox at the top right-end of the window is checked - Select the WrapPack to uninstall. The 3rd item above is important.  As the WrapPack are a subset of your product installation they will only be listed if the checkbox is filled. Old KB# 1501

Problem: It seems that animating a CGI with IIS version that comes with Windows XP does not work. It just runs through. Resolution: It seems there is a difference between IIS 5.0 that comes with Windows 2000 and IIS 5.1 that comes with Windows XP. The security in 5.1 is much tighter than in v5.0. There is no problem to animate a CGI in any versions of Net Express with IIS 5.0 of Windows 2000, and nothing additional has to be set. Please bear in mind that IIS is running as a service, and Net Express is a desktop application! Anonymous access or any other user id that were used to run the CGI must then have the proper permission to run a desktop application. This was not the case with IIS 5.0, but this is now enforced in IIS 5.1. Here are the steps to animate a CGI in Net Express with IIS 5.1 (it would be likely the same for any later versions): 1. Create a virtual directory (e.g. cgi-bin) for the Net Express project's DEBUG subfolder 2. Set Read an

Problem: A Net Express project was set to to perform remote animation between Net Express and a COBOL  program running on AIX with Server Express 4 SP3. When selecting to Start/Animating in the Net Express IDE the follow error message appears:- Execution error: file 'opt/microfocus/cobol/dynload/animsrvr.libr/dispatch.gnt' error code: 115, pc=0, call=1, seg=0 115 Unexepected signal (Signal 4) Resolution: This error was resolved by installing IBM APAR Number IY80008 to the AIX installation. Old KB# 1479