Rocket® COBOL

Problem: Method to make PROJMAKE build the debug and/or release versions Resolution: Supply the parameters within quotes, for example:     projmake -buildall <name.app> "Generic Debug Build" or     projmake -buildall <name.app> "Generic Release Build" Old KB# 5294

Problem: Which version of the windows compiler supports Unicode? Resolution: Micro Focus advises end-users with such requirments to employ the Micro Focus Net Express COBOL compiler, because there is now added support for many parts of the ISO 2002 COBOL standard including: o ISO2002 Object Oriented COBOL support delivering enhancements such as typed object references. o UNICODE support for global applications. Old KB# 5304

Problem: A text in your application appears differently once executed on another machine or a font routine fails to use a font that is installed in Windows. Resolution: It is possible that the selected font is not a True Type one, and Windows is set to use ONLY True Type fonts. Since Courier for example is not a True Type font, a routine such as PC_PRINTER_SET_FONT would fail with return code 13. Not only this Cobol routine cannot use it, but all applications in Windows. Here are the steps to turn off this setting in Windows: 1. Go to Control Panel 2. Open Fonts 3. Click on Folder Options from the Tools menu 4. Click on the True Type Fonts tab 5. Uncheck the only option in there, which is "Show only True Type fonts in the program on my computer" 6. Click on the Apply button 7. Click on the OK button, and you will be prompted to restart the machine 8. Restart Windows (after saving your work) Old KB# 5274

Problem: How to pass a linker option like /DELAYLOAD through CBLLINK? Resolution: Unfortunately, CBLLINK cannot pass options to Microsoft's LINK.EXE. The alternative is to specify options for the Microsoft linker LINK.EXE as an environment variable, e.g. set LINK=/DELAYLOAD:MyDLL.dll Microsoft's Linker options can be found here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_core_linker_reference.asp and how to set those options here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_core_set_linker_options.asp Old KB# 5270

Problem: How to write all the console output (including errors) from a batch program to a text file? Resolution: 1) You will need to compile your programs with the CHARACTER option rather    than GRAPHICAL.  This ensures that any errors are display as plain text    rather than in a Windows message box. 2) You will need to set the following runtime switches:    set cobsw=-I2 S5 3) You then run your program with redirection:    paddy01.exe > x.txt For example, the following program:        procedure division.            display "Before CALL...".            call "fred".            display "After CALL...".       

Problem: CALL 'CBL_DEBUGBREAK' to animate a program vs. via Net Express command-line with COBSW= A or COBSW= a Resolution: The preferred way to debug programs under Net Express is to start via CALL 'CBL_DEBUGBREAK', whereas COBSW= A also COBSW= a are out of use, therefore not documented. COBSW= A was included within older 16bit/32bit Micro Focus products (e.g. Workbench), and it is not intended to use this under Net Express. Old KB# 5267

Problem: Receiving message "ASLM Semaphore failure" when trying to run an application deployed using Net Express 4.0 Application Server when logged in with standard user priviliages. Resolution: This is actually a known issue when installing from the base release (or first release) of the Net Express Application Server. This version had a problem with setting the registry privileges correctly. This has been fixed.  Simply update the current version of Application Server using the latest build on the Micro Focus SupportLine web site: http://supportline.microfocus.com/websync/aps40.asp - (as of 6th September 2005) the file to be  downloaded and applied is APS06A40.EXE. This will install the latest build of the Application Server and allow users to run applications when logged in with standard user privilages. Old KB# 5309

Problem: Method to trap COM Errors without the black console box popping up Resolution: Code/logic a registered COM Exception Handler: The exception handler does not automatically terminate but allows users to determine the best action. In many cases this would be to terminate (ie STOP RUN). However, users can decide on the correct course of action for themselves. An Example of this is:-       $set ooctrl( P)        program-id. ADSIDemo.       ******************************************************************       *       *    Author  - David Sands (Micro Focus Technical Support)       *       *    Date    - December 2003       *  &n

Problem: Can MFSORT be used outside of Net Express? Resolution: MFSORT is part of Micro Focus' development and application server products.  It works on Windows, Linux and UNIX. Old KB# 5305

Problem: Release 4.0: Setting the compiler directive PERFORM-TYPE"ENTCOBOL" to ensure that programs have the best compatibility with the mainframe COBOL dialect. Since doing so, the user cannot do a RUN RETURN in the animator to step out of a performed paragraph or section. Resolution: This is the expected behaviour. Setting a mainframe dialect for PERFORM-TYPE has an implementation, where the appropriate information to determine the correct return point is not available. The PERFORM-statement behaves different from the default to the PERFORM-TYPE setting to mainframe compatibility (or RM).        a.     perform b through d.                display "a1".                goback.         

Problem: Existing project - source has been moved, but there is a requirment to change the project location Resolution: First when building a Net Express project - the suggested way is to copy any source being used to the local directory. If this has not been done and the project now points to a particular directory other than the project directory,  and the source has now been moved to a different directory The only way to correct the project settings is to remove the source from the project and read it to the project from the new directory. Note:  Net Express is UNLIKE Mainframe Express project where the location can be changed without removing and reading. Old KB# 5288

Problem: If a program has a long running block of code that adds items to a listbox or listview then the User Interface does not reflect the changes until the code has completed. Is it possible to update the control while the processing takes place ? Resolution: This occurs because all the processing is taking place on the same thread as the user interface. While the COBOL is processing data and adding items to a listbox the user interface will not respond as the Windows message Q is not being processed. The simplest mechanism to do this is by calling the "DoEvents" on the Application class at various points in the code. This will ensure that the Windows message Q will be processed at that point to reflect changes in your user interface. A more complex approach would be run the COBOL processing on a seperate thread from the user interface. This will ensure that the user interface is responsive while the COBOL processing takes place. Ol

Problem: The install of Net Express with .NET goes to a certain point, and it then abends without displaying any errors. In this case, Microsoft Visual Studio .NET 2003 is already installed. Resolution: Net Express with .NET requires the following products to be installed first: Net Express 4.0 with at least WrapPack 4.0.001 (all01n40.exe) Microsoft Visual Studio .NET 2003 with its own prerequesites It is worth to note that Net Express with .NET is an addon to Net Express 4.0. In other words, it does depend on Net Express 4.0. Old KB# 5283

Problem: Serial number was sold as Net Express with .NET 4.0 Installed Net Express Professional which installed the Revolve product with Net Express Resolution: Need to exit licensing windows. Go to START bar Select All Programs Select Micro Focus Net Express 4.0 Select Configuration Select License Management System Make sure that only Net Express is checked or high-lighted; depending on the license update version installed. Select full license and internet licensing Response YES; two times max; to the question; server is not responding do you want to wait License request has been completed message was received Old KB# 5316

Problem: Method to suppress the DOS window showing on an x"91" function 35 Resolution: Unfortunately there is no method to suppress the command window being displayed when executing an x"91" function 35.  An alternative solution is to use: 1) Using the CBL_EXEC_RUN_UNIT API instead. 2) Calling the operating system CreateProcess API. Old KB# 5317

Problem: Error when attempting to silently install the Net Express product. In the log file from the install the following error is displayed: Error:  Invalid silent script file, unable to start unattended install. when using a script that was previously recorded. Resolution: This can be caused by the ordering of some parameters in the install command. Run the install with a command using the following syntax: setup.exe /INI=C:\\mynetx.ini /LOGFILE=C:\\nxsetup.log /NO_SILENT_REPORT /SILENT=C:\\mynetx.sss This should produce the desired result. Old KB# 5291

Problem: How to use a self declared type within the File Section?        FD  EIN.         01  EIN-SATZ.             05  Testdate PblType-Dat.              05  filler    pic x.        working-storage section.         01 PblType-Dat         is typedef pic  9(08). Resolution: Use a prototype for your program: program-id. tst is PROTOTYPE. working-storage section.     01 PblType-Dat         is typedef pic  9(08). end program tst. program-id.tst. ... FS EIN. 01  EIN-SATZ.  &

Problem: NetExpress releases 4.0 - 5.0 Overview of file handler parameters. Resolution: To get an overview of file handling, please refer to: Net Express  Help -> Help Topics -> Content -> Reference -> File Handling -> File Handler -> Configuration -> Configuration file parameters - Overview Old KB# 5307

Problem: Problem when running a sample downloaded from the Micro Focus web site. The sample is a Net Express 4.0 CGI application that sends email using CDO to access an SMTP server. When running the sample on a development server it can send email fine. When the application is moved to a test server that has Application Server 4.0 installed, the following error message is displayed in the browser: execution error : file '' error code: 200, pc=0, call=1, seg=0 Run-Time System internal logic error (in rtsarea.c 85. line 400). The Application Server is unprotected. see incident 2104379. The Application Server was updated with aps05a40.exe (4.0.005?) The CDO sample was on the Micro Focus website. see incident 2105768 Resolution: The sample was being linked using the static and multi-threaded options. After changing these options to dynamic shared and single threaded the problem was resolved. Old KB# 5257

Problem: This is an example that will walk the user through the steps needed to take an EBCDIC mainframe sequential file and convert it to ASCII.  Follow each step carefully in the Resolution below to take the ASCII file and convert it back to EBCDIC. The example will also demonstrate how to create and use a Record Layout to be used with these files. Resolution: Convert mainframe EBCDIC file using  Tools ==> Data Tools ==> Convert to an ASCII file. Next, take ASCII file and convert it back to EBCDIC file. Files and project also will be attached to article Attachments: ascii_ebcdic_convert.doc Old KB# 5297

Problem: Dsrun Error 19,0,0, what does this translate to? Resolution: A Dsrun error 19 means that an attempt has been made to use a ds-use-set call but the screenset-id in ds-set-name has not been found on the screenset stack. Alternatively, an attempt has been made to use a ds-use-instance-set call but the screenset-id and screenset instance specified in ds-set-name and ds-screenset-instance has not been found on the screenset stack. Old KB# 5260

Problem: In this case the program was printing and then falling through into a loop. The program was recently recompiled using a newer version of Net Express. Resolution: This problem occurred because there had been a new Net Express project created and the compiler directive PEFORM-TYPE"OSVS"  was omitted. After adding the missing directive the looping stopped and the program ran fine. Old KB# 5263

Problem: RETURN-CODE always 255 when program starts to execute Initcall"mfextmap" has been used to load the External File Mapper Resolution: Do not use the initcall"mfextmap" compiler directive to load Mfextmap. Initcall is causing RETURN-CODE to be initialized improperly. There are two alternatives to using the compiler directive to get the External File Mapper loaded into memory. 1) Add the following call statement: call "mfextmap" at the beginning of the initial program of your run unit (process). This will get the External File Mapper loaded and available to the application programs. 2)  Use a "tunable", a configuration file and an environment variable to set up the External File Mapper without making changes to your application programs. Open Net Express 4.0 Help, and click Contents (tab),   Programming,     File Handling,   &nbsp

Problem: Program creates EBCDIC file on development system while it creates an ASCII file on Application Server system. Resolution: Link CS0437.OBJ to the program by adding CS0437.obj to the build settings of the .EXE file. Old KB# 5271

Problem: Is it possible to develop COBOL CGI applications by using Net Express with .NET? Resolution: Unfortunately, CGI is not supported in our current Net Express with .NET product.  According to the online help the following areas are not available: * Some CBL_ and PC_ routines (the majority are supported) * ADIS (Extended Accept/Display) * CGI * Micro Focus class libraries * Multithreading syntax * Mainframe performs (perform-type(osvs/vsc2)) * SOC 7 * Mainframe pointers * ANSI debug * GLOBAL declaratives in nested programs * CICS commands * Screen section * CALL-CONVENTION * Threading syntax such as THREAD-LOCAL-STORAGE and SEMAPHORE-POINTER. Please see the .NET online help for full details. Old KB# 5306