Rocket® COBOL

Problem: When using CBL_ routines and setting flags, it says set bit 0, bit 1, bit 2 etc. Is bit 0 on the left or right end? Resolution: - go to Net Express v5.0 Online Help - type in CBL_OR - select the topic under it 'using to set the value of a bit' - click 'display' - under the 'Parameters' area, click on the link to 'Key' - you are taken to 'Library Routines - Key' - page down - notice the lines:     On Exit:     Indicates which of the parameters shown are returned on exit.     Where bits of one or more bytes are referenced,     bit 0 is the least significant (rightmost) bit. Old KB# 1214

Problem: Release 5.0: Showing and hiding Windows when mixing graphical and character Screens. When you are doing a phased conversion of a character based application to a GUI it is often useful to hide the character screen window so that the user cannot click in the character window when control is on a graphical window. If the user does this then the character portion of the application will not response as control is currently in the character screen. Resolution: If the application EXE is built as a "graphical" application or started using the RUNW trigger EXE (int or gnt code) then any character screen are run in the COBOL Text Window. When the COBOL Text Window is used for character screens there is a runtime call PC_WIN_HANDLE that allows you to get the HWND windows handle. This allows you to manipulate the Window using standard Win32 api calls. The ShowWindow api with the SW_HIDE flag can be used to hide the Text window when required and

Problem: When accessing Micro Focus files it is always good practice to check the file status returned after each I/O operation. Resolution: It is possible to create a general COBOL copybook that can be reused in all programs.  The following is an example of just such a copybook:        01  (tag)-fstat.            03  (tag)-fs-values.                05  (tag)-fs-key1         pic x(1).                05  (tag)-fs-key2         pic x(1).                05  (tag)-fs-key2-bin   redefines &nb

Problem: Compiling a program with mulitple entry points gave the error: 002-R Attempted to redefine symbol when the program was compiled. Resolution: This was caused by the following scenario:- aaaaa.cbl had a program-id of bbbbb aaaaa.cbl also had a an ENTRY POINT called aaaaa. The problem here was generated because the compiler was attempting to create duplicate entry point called aaaaa. Here the program id did not match the source name. The solution was to rename the source file to bbbbb.cbl. The program then compiled cleanly to obj code. Old KB# 1247

Problem: Net Express 5.0 with .NET (base release): System.MissingMethodException on MicroFocus.COBOL.Program.Edited.loadCheck64bitNumericEdited message when running a Net Express 5.0 .NET application Resolution: Net Express 5.0 with .NET (base release): Where there is a combination of a MOVE from an edited data item to a non-edited  data item and the CHECKNUM directive. Removing the CHECKNUM directive is a work-around, but installing Net Express 5.0 WrapPack #2 (or higher) will resolve the problem. Old KB# 1235

Problem: Is there a possibility to interface COBOL vs Open Source databases, e.g. MySQL or PostgreSQL? Resolution: Yes, via an ODBC interface provided by Net Express Windows product also provided by Server Express Unix / Linux product (to find in doc files under:OpenESQL) and including a precompiler there is a possibility to interface Open Source databases, e.g. MySQL / PostgreSQL, using ODBC drivers delivered by this Open Source community: a) MySQL:  http://www.mysql.org/downloads/connector/odbc/ b) PostgreSQL: http://pgfoundry.org/projects/psqlodbc Old KB# 1240

Problem: When compiled to GNT the application just terminated with no error being output. However when it was built to INT it worked successfully. The last event from a COBOL runtime Consolidated Trace output was an exit program event. Resolution: The top level program in this case was C and it used cobcall to invoke the COBOL. Errors such as this are usually down to the application exceeding stack size.  Recursion and local storage all contribute to the stack usage. To increase the stack size by using the /STACK option of the Microsoft Linker. Using another linker then please see the documentation supplied with your linker. Old KB# 1231

Problem: What is the simplest way to set the default ADIS (DISPLAY) colours so that all DISPLAY statements would use the specified colour. Resolution: The simplest way to do this is is simply to clear the screen as follows:       display spaces with foreground-colour 3 This sets the default Text colour to CYAN. The online documentation details the number that correspond to colours. Old KB# 1249

Problem: Working with Net Express 5.0 WrapPack 2, having linked an OpenESQL application to executable in 64-bit mode on x86-64 platforms, executing the application returns an RTS114 error. This does not occur in 32-bit mode on x86-64, under 32-bit environments, nor on 64-bit Itanium platforms. This does not occur when working with the GA release of Net Express 5.0 either. Resolution: This issue is resolved in the latest WebSync for Net Express. To workaround this issue with WrapPack 2 installed, there is a must explicitly to link the application with ODBCRW64.LIB. To specify this module if linking from a Net Express command prompt, using cbllink. If building your application from within the Net Express IDE,  specifying this module by : From the Project menu item, select Build Settings. Click on the name of your executable, for example myapp.exe. Click the Link tab. From the Category pulldown, select Advanced. Enter odbcrw64.lib into the t

Problem: A COBOL program built as an .exe in Net Express and Interface type as Graphical, displays characters in the 'COBOL Text Window' -- a MF implemented win32 console -- when run. Try to change the font size and you can only choose up to a maximum value of 20. Resolution: The value 20 is the font size limit of the COBOL Text Window. Old KB# 1211

Problem: Is there an easy way to count the number of records in an indexed file? Resolution: Use rebuild with the "/n" option to read the header of the indexed file and return information on the file which will include the numbert of records. e.g. rebuild /f file.datOld KB# 1233#AcuCobol#ServerExpress#RMCOBOL#COBOL#netexpress

Problem: How to deploy a Net Express 5.0 Web Service? Deploying a COBOL .NET Web Service and may get an error after deploying the .asmx and the code behind cbl file. This is due to the COBOL compiler not being included in the Server 5.0 runtime install. Just copying the contents of the project to the deployment server server is not enough as it attempts to compile the CBL file. Resolution: To get a COBOL.NET Web Service working on a deployment machine there is a need to perform the following steps:- - Load the Project in Visual Studio - Highlight the COBOL project and use "Build" / "Publish Web Site" from menu - Uncheck the "allow precompiled website to be updateable" option A compiled version of the Web Service will then be built into the same location as the project. This can be copied to the deployment machine and configure IIS for use it as required. There is also the need to setup some permissions in order for the

Problem: Environment variables can be set at several locations and there was an invisible setting of the environment variable EXTFH which got priority over other settings. The resolution is valid for all environment variables. A status 9/194: "File size too large" was reported even if the settings in EXTFH.cfg configuration file were correct. The EXTFH.cfg settings were: [XFH-DEFAULT] FILEMAXSIZE=8 which allow to access an IDXFORMAT"8" file larger than 4 GByte. But nevertheless the OPEN gives a file status code 9/194. The setting of the environment variable EXTFH in the environment does not change the behaviour. What can cause this? Resolution: The cause for the status is that the EXTFH.cfg could not be read or a false one was found. See also KB: 23553 for "Using Filemon to ensure that the correct version of a file is in use" The resolution here was to delete the <project-name>_RTECFG.obj, because it was no longer used. This obj is linked

Problem: Attempting to install Net Express 4.0 onto a machine that previously had Application server installed.  However, the Application Server product was not listed in the 'Add/Remove Programs' in the Control Panel, to enable it to be removed. Error:  Setup has detected an installation of Application Server for Net Express 4.0.   Net Express 4.0 cannot be installed while Application Server for Net Express 4.0 is present. Resolution: Fully check that no Application Server or Net Express product is installed: - check 'Add/Remove programs' via the Control Panel - check via Windows Explorer for the following folders      C:\\Program Files\\Micro Focus\\Net Express    OR      C:\\Program Files\\Micro Focus\\Application Server    OR      C:\\mfaslmf - In the Windows Explorer and click on the C

Problem: When installing wrappack NXP3250020077.msp for NetExpress 5.0, the .NET part of the product is automatically uninstalled.   Having successfully installed the wrappack and uninstalled .NET in NetExpress 5.0, the following error was encountered when attempting to reinstall .NET in NetExpress 5.0 via the control panel.  This error is returned in an attempt to install Assembly. (Error 1935.An error occurred during the installation of assembly 'MicroFocus.IDE.Util,Version="2.1.0.0",ProcessorArchitecture="MSIL",PublicKeyToken="0412C5E0B2AAA8F0",Culture="neutral",FileVersion="2.1.2.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {6F0DFD4C-19BB-4347-99E5-6502E8C9A6CC}) Resolution: It was necessary to uninstall Visual Studio 2005 and all the .NET components via the control panel

Problem: Is there a way to display application errors in a dialog box? Resolution: Net Express 4.0 and later The attached demo illustrates a way of displaying errors from your applications within a Windows dialog box.  The demo takes the form of a sub-program that can be called and passed information on the error.  The demo supports the following error types: 1) Dialog System 2) General 3) Intrinsic function 4) Panels2 5) File I/O The code is easy to follow and can be extended without too much effort. Attachments: DISPERROR.ZIP Old KB# 1242

Problem: Determining the EXE to start the program is easy. - The windows explorer can be used to start it. - If an icon on the desktop is uses, its properties give the path - If the command prompt is used, the EXE is in the actual directory, or ... Here the difficulties - or better say for this paragraph "possibilities" - begin: Examining the environment variable PATH will give the answer. If there are two, the first one is used. In the normal world of programs the EXE will not be the only file used by the application. The EXE may - need a COBOL runtime system -- which may need a _COBCONFIG.cfg configuration file - use self programmed DLLs, COBOL INTs and GNTs - start other EXEs, e.g. by CBL_EXEC_PROGRAM - uses DialogSystem screen sets --- which may need an *.ICN file - open user files -- which may need an EXTFH.cfg configuration file ... The strategies to find the files are manifold. Environment variables like PATH, COBDIR, and others, re

Problem: File and Filename Routines: CBL_CHANGE_DIR, CBL_CHECK_FILE_EXIST, CBL_COPY_FILE, CBL_CREATE_DIR, CBL_DELETE_DIR, CBL_DELETE_FILE, CBL_DIR_SCAN_BEGIN, CBL_DIR_SCAN_END, CBL_DIR_SCAN_READ,  CBL_GET_CURRENT_DIR, CBL_JOIN_FILENAME, CBL_RENAME_FILE, CBL_SPLIT_FILENAME, PC_FIND_DRIVES,  PC_PRINT_FILE PC_PRINTER_CLOSE, PC_PRINTER_CONTROL, PC_LOAD_BMP, PC_PRINTER_OPEN, PC_PRINTER_WRITE, PC_PRINTER_WRITE_BMP, PC_READ_DRIVE, PC_SET_DRIVE Example:     01  infile-name  pic x(20) value '%TMP%/infile'.     01 outfile-name pic x(20) value '%TMP%/outfile'.     call 'CBL_COPY_FILE' using infile-name outfile-name. Will fail unless a file with the literal name "%TMP%/infile" exists. Likewise for the outfile name. The CBL_ routines use system API calls, not the command shell, to do their work. Only the command shell "knows&quot

Problem: Runtime DLL 'CBLRTSS' not found when running a CGI web application. Encountering any message mentioning runtime DLL 'CBLRTSS' not being found when running a web application on a server where Net Express Application Server is installed, it means that the COBOL runtime files cannot be located by the web application. Resolution: Built/linked the application to use the shared runtime, but have not specificed the "dynamic" option for the shared runtime, then it is a  must either to set the PATH and COBDIR environment variables to the location of the runtime files (Application Server) or to place the application where those files reside. Linked the application to use the dynamically bound shared runtime, then the application will first search the Windows registry to find the location of the Application Server runtime files. It is possible that the web application, when deployed to the web server, does not have access

Problem: Release 4.0: Receiving this error when trying to run an executable from within the Net Express 4.0 development environment after applying the all08n40 Websync WrapPack. Receiving a similar error when running the executable on a separate machine with Application Server for Net Express 4.0 installed then please refer to KB # 22608. This article refers specifically to when this error is encountered when running within the Net Express development environment. Resolution: One possible solution is to rebuild the executable using dynamic binding. _____ Using the Net Express IDE, open the Project used to build the executable and select 'Project' from the menu bar, select 'Build Settings' from the dropdown and then select the 'Link' tab. At that point try setting the 'Run Time Library' settings to be 'Shared, Dynamic'.  Setting this either Single or Multi Threaded as required. Rebuild and then re-ru

Problem: In the NetExpress 5.0 documentation, if the link to "Extended File Status Codes" is followed from the master index, the message for the "nnn" field cannot possibly be correct.  For example "161" is shown as "Illegal Intermediate Code". Resolution: The links in the version 5.0 documentation for extended file status actually go to the run-time system error numbers, which are not applicable.  The example above, 161, should be "file header not found". The workaround is to use the Error Messages reference manual from an older version of NetExpress.  The NetExpress 3.1 documentation is correct and is available at the SupportLine web site, http://support.microfocus.com under "Documentation". Corrected documentation is tentatively scheduled for release in July 2007. Old KB# 1209

Problem: When attempting to perform a rebuild of an indexed file from the command line (eg rebuild filename.dat) , the following error may be displayed:       Error on Input File - Striped File Descrepancy even though  file striping is not being used. Resolution: One possible way of rebuilding the file is to generate a new version of the .idx file. In one previous instance where this error occurred, it seemed that the original .idx file was completely corrupted and was not able to provide any meaningful information to the filehandler. Subsequently, it incorrectly determined that the file was a striped file. This resulted in the creation of a new version of the .idx and match that with the original version of the .dat file and then rerun rebuild  in order to regenerate the index based on the data in the original .dat file. The steps to achieve this are as follows: 1) Deleted the existing .idx file

Problem: OFN-ALLOWMULTISELECT flag can be set from the WinAPI GetOpenFileName function to specify that the File Name list box allows multiple selections in the open file dialog box. This however causes dialog box to use the old-style user interface. Resolution: It is documented from the Microsoft MSDN site (http://msdn.microsoft.com) that you need to set also the OFN-EXPLORER flag to have the dialog box to use the Explorer-style user interface. If this flag is not set, then it will use the old-style user interface. Old KB# 1246

Problem: On occasions there is an issue whereby the majority of the COBOL WinForms Toolbox Icons are the same. Unloading the project and reloading it, rebooting the PC does not help. Resolution: Drop to a Visual Studio command prompt and run the command   DEVENV /ResetSettings The result will be that the Toolbox Icons are reset to their correct settings. Old KB# 1224

Problem: Net Express 5.0. Is it possible to turn the newline x"0A" character off when writing an XML stream to :cgi:. Resolution: The Net Express 5.0 documentation includes the following: New syntax for select statement is:      SELECT xmlfile ASSIGN TO [[NOT] LINE ADVANCING] FILE Of course if "NOT LINE ADVANCING" is specified then no line-feeds would be included in the output.  How to write a newline character at the end of the XML stream? This can be achieved as follows: ...        select xml-file            assign to not line advancing file-name            organization is xml            document-type is "CompanyTrans.xsd"