Rocket® COBOL

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: 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: 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: 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: Block version numbers do not match Resolution: Release: 3.1   Export and import the screenset. In a case this occurs with application that uses RS files, the RS files may be required to be regenerated. Attachments: A3686.ddl Old KB# 6810

Problem: What would increase the DLL size coming from 3.0 to 3.1 considerable? Resolution: Release: 3.1   Net Express v3.0 shipped with and used the Microsoft v5.0 linker.  Net Express v3.1 shipped with and used the Microsoft v6.0 linker.  The size difference that you are seeing is due to the difference between the linkers. Old KB# 6824

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: 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: 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: 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: Dynamic OLE Classes Resolution: You can specify:- oleclass is classname  instead of oleclass is "$OLE$aclass" and in procedure division:- move "$OLE$aclass" to classname Old KB# 6820

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: 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: 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 package Dialog System ".s" screenset files as part of an executable? Resolution: The only way to package the screensets so that you do not need to send each one out to the other sites individually would be to add them to a Micro Focus LBR library file. Attachments: smime.p7s Old KB# 6863

Problem: Converting files from OEM to ANSI Resolution: Release: 3.1   To use mfoemtoa utility for files then to use call_by_names routines PC_WIN_OEM_TO_CHAR and vice-versa respectively Attachments: RMW_Case00010594.doc Old KB# 6839

Problem: Release: 3.0   No bitmap/icon resource file was associated with the screenset, ie. no sidefile was  found. Resolution: Allocated a sidefile resolved this error. Resource files enable you to specify the following files to be used:      * Bitmap side file, used for images of bitmaps, icons, and mouse pointers      * Font side file      * Error file Dialog System uses the bitmap side file, which is an ASCII text file, to find the bitmap images used by a screenset. Select "Resource files" from the Options menu in the Dialog System main window. Specify the side file name in the Resource File dialog box. Note:  Dialog System can use one side file at a time (in addition to ds.icn). Old KB# 6864

Problem: Release: 3.1   Each COPY statement in your program identifies a copyfile to be copied.  If the filename in the COPY statement is incomplete, because it lacks either an extension or a path, the Compiler searches for it as follows: Resolution: 1. In the directory given by the COPY library-name. Note that if the name of the copy file is a qualified filename, that is, it     includes the path or directory, the Compiler searches that directory only 2. In the directory containing the main source program being compiled 3. In any directories listed in the COBCPY environment variable, in the order specified If the COPY statement does not give the extension of the copyfile's filename, the Compiler searches for files with extensions given by the directives OSEXT and COPYEXT. You can set the COBCPY environment variable from each project as follows: 1. Go to Project > Properties > Environment&#3

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   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: 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