Rocket® COBOL

Problem: Dialog System - unable to refresh text displayed on push button Resolution: Release: 3.1   Move the data to be displayed to a field in the data block and use SET-OBJECT-LABEL PB1 'data-block-field' Attachments: 8012-00-RF-DATE-VAL.cpy Old KB# 6852

Problem: How to initialize COM properties when COBOL COM is instantiated. Resolution: Release: 3.1   -  How to initialize COM properties when COBOL COM is instantiated. You can't do this automatically.  However, what you could do is create an initailize instance method and have the client call that, or have the instance variables as OLE properties and have the client set them. Old KB# 6805

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: 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: 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: 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: 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: 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.0   This rule is defined in the Net Express Help under Class-Control paragraph in the Language reference manual: Resolution: ------------------- This example shows a Class-Control paragraph which registers classes CharacterArray and myClass. The Class-Control paragraph is part of the new Object Section, which goes at the end of the Environment Division. class-control. CharacterArray is class "chararry" myClass is class "myclass" . The filename is in quotes at the end. You must enter the filename in lower-case this is for future compatibility with operating systems with filename case-sensitivity. Attachments: RMW_Case00010573.doc Old KB# 6834

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