Rocket® COBOL

Problem: IC255-I Resolution: This error requires that two files (fttext.lng and idxcheck.lng) be extracted from Mflangdf.lbr and added to the directory where the program is executing. Old KB# 6821

Problem: Problem calling COBOL .DLL from Visual Basic program Resolution: Release: 3.0   If you want to animate the COBOL then the VB files must be copied to the DEBUG directory and then when you start Animating specify the program DEBUG\\DEMO1.EXE. This will start the VB program and then when it calls COBOL the programs will be loaded into the animator. Attachments: DB2TableDefines.piz Old KB# 6842

Problem: Release: 3.1   The definitive answer the question  is yes, external names are case sensitive. Resolution: Example: CLASS-ID. classa AS "ClassA". *> "ClassA" is the external name REPOSITORY.     CLASS myclass AS "myClass" *> "myClass" is the external name.     CLASS classB *> No AS clause "CLASSB" is the external name.    .     CLASS classa *> external name taken from CLASS-ID clause, "ClassA"     . Old KB# 6857

Problem: HELP is a module name that is used by Windows. Resolution: Rename the subprogram. Old KB# 6853

Problem: It is possible to animate COBOL when called from Java, but it is not possible to animate Java when called from COBOL, if COBOL is the main program, but it is possible to animate Java when called from COBOL if Java is the main program: Resolution:   Java ---> Cobol ---> Java This is the case with any mix programming, the reason being that any of the third party debuggers do not have a similar feature to our "CBL_DEBUGBREAK" that allows you to start the debugger at any point of the execution of a COBOL program. So if you want to animate an application where the main program is COBOL that invokes a Java class, then the only way of doing it is creating a dummy Java main program that calls the COBOL main program that has to be linked as a dll instead of an EXE in the following way: 1) create a simple Java program that calls the COBOL DLL e.g.:     import mfcobol.*;     class de

Problem: How to do a batch compile and link from the command line? Resolution: Release: 3.1   @echo off cls echo. echo This batch file has to be run from a Net Express Command Prompt echo. echo Start - Programs - MERANT Net Express 3.1 - Net Express Command Prompt echo. pause rem set cobcpy=Drive:\\YourDirectory\\YourSubDirectory;%cobcpy% echo. echo The compiler directives in COBOL.DIR will be used echo. pause echo Here are the options for the CBLLINK utility echo. cbllink pause FOR %%I IN (*.CBL) DO CBLLINK -bsf %%I pause echo. echo Deleting the OBJ files ... rem DEL *.OBJ pause echo. echo Moving the EXE files to D:\\Temp ... rem MOVE *.EXE D:\\TEMP pause Attachments: 2957 EFX53.zip Old KB# 6826

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

Problem: How to link to the shared runtime from the command line? Resolution: Release: 3.1   Open a Net Express Command Prompt and execute CBLLINK from the command line. This will display all options that can be used with the CBLLINK utility. Using the -F option to link with the shared runtime system will imply that the users will have to make sure the runtime files are in the current directory or the PATH and COBDIR environment varialbes are pointing to the runtime files prior to run the user's application. On the other hand, the -R option is to link the user's application with the dynamically bound shared runtime. The Applicaiton Server or Net Express runtime system are automatically located by looking them up in the Windows registry. Old KB# 6859

Problem: COBOL switch turned on from Appl. Environment still in effect after turning Resolution: Release: 3.1   This was fixed in the compiler FixPack v3.1.007 (or CMP07NE31.EXE) and part of the latest compiler FixPack v3.1.008 (or CMP08N31.EXE). Old KB# 6813

Problem: Release: 3.1   Mmmm, always a tricky one this.  Firstly, you will need to have fonts installed on the PC that contain a Euro symbol.  Microsoft have these available for download on their website. Resolution: The next thing is the IDE.  I am not sure if any of the OEM fonts contain the Euro symbol.  If not, then you will need to switch the editor to ANSI mode before you enter the symbol (you might have to do this via the Character Map utility). The next problem is displaying the symbol!  Dialog System runs in ANSI mode so this should not be a problem.  However, the console does not and you may find that you need to convert the strings before you display them (ANSI to OEM APIs).  However, if there is no console font that contains a Euro symbol then you may be stuck! Net Express will display the fonts that it can use in the editor based on the OEM/ANSI setting and m

Problem: RTS 119 Name is not unique Resolution: Release: 3.1   Make sure the same module is not linked more than once in the same run unit. In other words, this error occurs if a module has already been loaded in memory and another program tries to load the same memory. Alternatively, make this common module as a DLL. Attachments: Code.zip Old KB# 6849

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: PC_PRINTER_INFO routine does not return the printer name correctly. Resolution: Release: 3.1  The problem has been addressed and the fix released in FixPack rts03n31for Net Express and aps05n31 for Application Server. Old KB# 6840

Problem: Unable to create a directory using UNC with CBL_CREATE_DIR Resolution: Release: 3.1   This does not work if the UNC contains ":" as to refer to a Novell path name. Windows does not allow this character in a path or directory name. This is used only to identify drive letter. Attachments: Brave.zip Old KB# 6841

Problem: Get 173 error when calling 16-bit DLLs from a 32-bit EXE Resolution: Release: 3.1    Get RTS error: 173 Called program file not found in drive/directory It is not possible to call 16-bit COBOL DLLs from a 32-bit EXE. You will need to recompile all in 16-bit or all in 32-bit. Old KB# 6871

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: ESO100 Cursor  not declared on Close Cursor Resolution: Cursors can be defined within Working-Storage to prevent the sequence problem. The checker is reading the program line by line not following any perform paragraphs when checking the program. Check that references to a cursor are not made before the Cursor is defined to the program. Attachments: image001.jpg Old KB# 6868

Problem: Any reason why size of LIB is smaller under Net Express 3.1 than Net Express 3.0? Resolution: Release: 3.1   The reason for the difference in LIB file sizes is that Net Express v3.0 uses Microsoft's v5.0 for linking, while Net Express v3.1 uses Microsoft's v6.0.  The linkers created the different output sizes. Attachments: Legacy.piz Old KB# 6866

Problem: 28-S Compiler Error Resolution: Release: 3.1: Customer was passing a pic x(9) item by value. Changed this to by reference and error went away. Attachments: StateFarm_Test Inventory report_D20081123.zip Old KB# 6835

Problem: Rebuild Error: IC255-I Error Reading Message file Resolution: Release: 3.1   Extract fttext.lng and idxcheck.lng from mflangdf.lbr and put these files into the same directory as rebuild.exe. To extract the 2 files from the library file, you need run the lmg3setup.exe addpack on the Net Express 3.0 fixpacks page.  Next you'll need to unzip libman.zip to a directory and run the libman.exe file.  This exe uses the library manager API to export and manage library files. Old KB# 6867

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: Release: 3.1    How to change the format of columns ? Resolution: A data item entry in the Data Block consists of a name up to 30 bytes long, a data type code, and, for data items other than object references which have a fixed size, the number of bytes before and after the decimal point. At run time, all data items can be used or changed by the screenset or the calling program. Data types within the data definition are represented by a code that enables the calling program to determine the data type. Each data item defined must have its type specified. Valid data type codes for a data item are any of the following: X Alphanumeric 9 Numeric A Alphabetic S Signed numeric C Computational (number of bytes must be 1.0, 2.0, 4.0, or 8.0) C5 COMP-5 (number of bytes must be 1.0, 2.0, 4.0, or 8.0) N DBCS (N) (Double-byte Character Set) G DBCS (G) OBJ-REF Object reference Numeric data items have a maximum length of 18 chara

Problem: How do you use Active X controls in a Net Express project? Resolution: Release: 3.1   ActiveX/OLE Automation is covered in the Net Express bookshelf/online books topic "Distributed Computing". There are chapters on OLE Automation and DCOM which explain how COBOL programs can take the form of a client or server in the OLE/COM domain. Visual ActiveX components can be used in a COBOL program thru the use of the GUI Object COBOL class library or with Dialog System.  See the OO Class Library Reference in the help or the Dialog System User's Guide (chapter 10: Programming Your Own Controls) in the bookshelf. Old KB# 6861

Problem: How to use Fileshare as a Windows Service Resolution: Release: 3.1   You can only have one copy of Fileshare running as a NT service. If you wish to have a number of FileShare servers running to split up the file access then you will have to load them as separate processes.  Running them on different physical machines on the network would give you your best performance benefit. Attachments: - Old KB# 6809#AcuCobol#ServerExpress#netexpress#COBOL#RMCOBOL

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