Rocket® COBOL

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

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