Rocket® COBOL

Problem: File status 9/173 on read of index file with data compression. Resolution: Release: 3.1   If you are using the DATACOMPRESS"1" compiler directive, you should link cbldc001.obj in with your application. The Net Express help topics "Linking the Run-time Support Modules" and "Run-time Support Modules" mention some of the modules that may be required. Attachments: Second Load.zip Old KB# 6823#ServerExpress#COBOL#netexpress#RMCOBOL#AcuCobol

Problem: 173 ON MFEXTMAP.DLE Resolution: Release: 3.0   Advised:     remove ".dle" extension from call;     use the assign"external" compiler directive;     set Mfextmap environment variable in Project Properties, IDE. Old KB# 6814

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: How do you resolve 805 error? Resolution: 805 specifieds package not found. The program you are trying to execute was not bound to the database. Either make sure when compile program that using db2(access) or have your compile produce a bnd file and bind manually to the database. Attachments: ORA-04031 Error.doc Old KB# 6850

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: 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.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: 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: Problem running old Workbench code with new Net Express code Resolution: Release: 3.1   I'm sorry but you cannot mix the Workbench product applications with applications created with Net Express.  They have incompatible and conflicting run-time systems. If you wish to run your application in Net Express then you need to recompile the entire system using Net Express.  Some of the run-time files between the two products, such as UTILS.LBR have the same name and so they cannot just be copied over. Old KB# 6804

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: 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: Release: 3.1   You must pass a pointer to the data item to COBOL and establish addressibility within the linkage section. Resolution: Linkage section. 01  some-string    pic x(256). procedure division.     call "some_func" using by value int-param                               returning address of some-string     end-call Then in your C program return a pointer to the array Attachments: DB2_description.JPG Old KB# 6858

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  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: 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: 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: 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: 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: 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: 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: How to debug a COBOL program and Dialog System screenset in the same session Resolution: Release: 3.1   -  You can certainly use both the Net Express and Dialog System animators in the same session. To start, you can change in your COBOL code the call to Dialog System using DS instead of DSGRUN. This will always invoke the Dialog System Animator everytime you step to this call from the Net Express Animator. In other words, you can start to step through your COBOL code, and the Dialog System Animator will be invoked when you step the call to Dialog System. That is, I am referring to the following call in your COBOL program: CALL dialog-system USING Ds-Control-Block, Data-Block where dialog-system has the value of DS. Old KB# 6832

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: 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: 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: For Update clause not allowed with declare cursor in SqlServer 7 Resolution: Release: 3.1   fixed in OpenEsql 3.1.001 fixpack dated 14 Feb 2001 Attachments: Data Flow.doc Old KB# 6819