Rocket® COBOL

Problem: Fileshare not working with 2 NIC cards. Resolution: Release: 3.1   Fileshare was designed to work with only one NIC card. Old KB# 6806#ServerExpress#RMCOBOL#netexpress#AcuCobol#COBOL

Problem: Cannot get the advanced break point to advance on a condition. It wont stop. Resolution: Release: 3.1   The animator will stop at breakpoint-on-condition after 1st stop at breakpoint line Attachments: 2857 EFX114.piz Old KB# 6847

Problem: Release: 3.1   When you move the source from the right to the left what compile type should you select for an EXE.  You would select OBJECT CODE OBJ. Resolution: Next highlight the OBJ in the left window, right click mouse and select Package Selected files to Executable File (EXE) Now to be able to animate you would want to add the ANIM compiler directive for the compile. Highlight the CBL in the left window, right click mouse and select Build Settings then select the Compile tab. Add the directive ANIM before the semi-collon seperated by a space from the prior directive. Attachments: ABNFIL.cob Old KB# 6831

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: HELP is a module name that is used by Windows. Resolution: Rename the subprogram. Old KB# 6853

Problem: Project file cannot resolve the location of source codes Resolution: Release: 3.1   Just do an Update All Dependencies to resolve all files in the current directory and use the cobcpy environment variable to resolve the location of the copybooks in different directories. Old KB# 6838

Problem: Question on ISO2000 support in 4.0 Resolution: Release: 3.1   All the ISO OO syntax will be part of the Micro Focus 'MF' dialect, so one will be able to use normal Micro Focus extensions also. Old KB# 6833

Problem: Compile of function UPPERCASE, causes  message 13-s user name required Resolution: Example: Move function upper-case (dataname-1) to dataname-2. Attachments: LSWPOL.cpy Old KB# 6816

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: Release: 3.1   I am afraid there is nothing that Micro Focus can offer above REBUILD. Resolution: REBUILD is a utility which will attempt to restore corrupted files.  As you have found, the success of REBUILD is dependent on the corruption level of the file.  If the file is badly corrupted then it will fail to recover the data. This is why it is very important for Customers to take regular backups of their data files.  If they require the ability to rollback/rollforward then they should also use the transaction processing features within Fileshare. One thing they could do is to use the byte-stream I/O routines to read the file at the lowest level - they may be able to extract more data this way. Attachments: RMW_Close_Function_NonOperative.doc Old KB# 6848#ServerExpress#AcuCobol#netexpress#COBOL

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: File error when using UNC path names Resolution: Release: 3.1   need to specify \\\\server\\path  in the program, not just the directory path Old KB# 6827

Problem: Error code 119 on EXTSM when calling subroutines that do a SORT Resolution: Release: 3.0   Do not link in the system programs on the DLLs (advanced link option).  Instead link in the system programs on the main EXE and add EXTSM.OBJ as an additional object (advanced link option again. Attachments: Header.rar Old KB# 6845#COBOL#ServerExpress#AcuCobol#RMCOBOL#netexpress

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: 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: Are there character display dimensions other than 80X25, 80X43, 80X50? Resolution: The COBOL Text Window will adapt to the standard dimensions, 80X25, 80X43 and 80X50. The operating system may be capable of other dimensions, however, only the standard dimensions are supported. Old KB# 6869

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: Sorting on a file and having problems with the size of the file. Resolution: Set the TMP and TEMP environement variables to a location where more disk space is available. Old KB# 6818#ServerExpress#COBOL#netexpress#RMCOBOL#AcuCobol

Problem: CONVERT within  a SQL statement is causing a syntax error when defined at the 01 Resolution: Release: 3.1   The latest ESQLv3.1 002 fixpack has SQL TYPE's that can be defined at 01 level o  OpenESQL now supports new "SQL TYPE"s that can be used as host variables        DATE, TIME, TIMESTAMP, DATE-RECORD, TIME-RECORD, TIMESTAMP-RECORD,        CHAR-VARYING, BINARY, VARBINARY, LONG-VARBINARY, AND LONG-VARCHAR. Old KB# 6825

Problem: Release: 3.1  It is not possible to use character tables in dialog system.   Resolution: In order to display lots of information there are two options available, Listview or an ActiveX grid, both have demo's included within the Product.  A listview simply displays information in a list whereas with an ActiveX grid you are able to edit the information within the table. 1.  Listview demo found in \\Net Express\\dialogsystem\\demo\\commoncontrols\\listview 2.  ActiveX grid demo found in \\Net Express\\dialogsystem\\demo\\activex\\custgrid Both examples are attached to this KB. Attachments: LISTVIEW.zip Old KB# 6822

Problem: Getting an error 173 when calling a .DLL which contains an EXTERNAL file def Resolution: Release: 3.1   Link the modules MFFH.OBJ EXTERNL.OBJ and BSIO.OBJ into the .EXE program. These can be added under Link options Advanced. Attachments: 10517 (Delete Partition) 20081011.zip Old KB# 6829

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