Rocket® COBOL

Problem: Net Express 4.0 Oracle ODBC driver. Resolution: Investigations showed that this was an issue with the Oracle ODBC driver.  A solution is to use the DataDirect ODBC drivers: 1) Download the Data Direct evaluation version of their suite of ODBC drivers:    http://www.datadirect.com/download/index.ssp - Data Direct Connect ODBC for    Windows release 5.0. 2) Install these and configure a new DSN for Oracle using their driver. Alternatively, contact Oracle support who may be able to supply an updated driver of their own. Old KB# 5249

Problem: The MFDS Service hangs when attempting to apply the Net Express 4.0 fixpack collection. Resolution: Before attempting to run the Net Express 4.0 fixpack updates updates, go into control panel and right click on the MFDS service, and change it's properties to disabled - then reboot the machine. This will ensure that the service isn't started on boot up. Now there should be no problems in applying the updates. After they have been successfully applied, change the service back to automatic. Old KB# 5193

Problem: FSVIEW enters a FSVIEW command line environment. Resolution: The XFH05N40 fixpack which is part of the ALL04N40 wrappack adds the file FSVIEW.EXE to Net Express but the add pack FSV01N40 must be installed before it can be used. To exit the FSVIEW command prompt enter the word EXIT. Old KB# 5210#RMCOBOL#netexpress#ServerExpress#AcuCobol#COBOL

Problem: how to use files bigger than 4 gig Resolution: 1. use compiler directive IDXFORMAT"8" allows the creation of large indexed files up to 128 Tb **this step only has to be used for a program creating new files 2. Need to set FILEMAXSIZE=8 in extfh.cfg file under [XFH-DEFAULT] ex.  this file is just a text file. [XFH-DEFAULT] FILEMAXSIZE=8 3. Next  set environment variable EXTFH to point to path and file name of the cfg file (if using a project can set environment variable under Project Properties> Environment>IDE) Old KB# 5197#ServerExpress#netexpress#AcuCobol#RMCOBOL#COBOL

Problem: There is some confusion about how the VALUE NEXT phrase works when it is defined for a 78 level constant data-item that is embedded within a group item containing the REDEFINES clause. Using the example below, the following questions are asked: Is there any reason why the value of MTCount is 23 and not 12?   Is there any reason why uncommmenting TABLE-TWO will correct the problem?        01  TABLE-ONE.            78  LTSize                 VALUE 17.            78  LTStart                VALUE NEXT.            05  WS-LEVEL-TABLE.   &n

Problem: Tips on how to use data type 'SQL TYPE is TIMESTAMP' vs. MSSQLSERVER also ORACLE database. Column in MSSQLSERVER is declared as 'DATETIME'. Column in ORACLE is declared as 'DATE'. Both databases reflect a date format 'dd.mm.yyyy hh:mm:ss' which is different to 'yyyy-mm-dd hh:mm:ss' by default. Resolution: A string should be redefined as follows, i.e.: 02  upd-date.     05  upd-dd           pic 99.     05  filler          pic x     value ".".     05  upd-mm          pic 99.     05  filler          pic x    &nbsp

Problem: A program using an open extend statement for a file defined without the optional phrase works fine on one computer. If the file does not exist then a file status code of "05" is returned, which is fine. On another machine the program cannot create the file if it does not exist unless the optional phrase IS specified. Resolution: The compiler directive option-file is the default for the Micro Focus dialect. If the RM or ansi'85' directive is used then the nooptional-file directive is also set. This could be the problem. If one of thes directives is being used then defining the optional phrase in the select statement overrides this and it will work correctly. Old KB# 5238#RMCOBOL#netexpress#AcuCobol#ServerExpress#COBOL

Problem: There have been instances in Net Express 4.0 when after installing the all04n40 fixpack the 'Dialog System' option has dissapeared from the 'Tools' dropdown menu. Resolution: To permanently have 'Dialog System' on the 'Tools' dropdown menu: From the menu bar go to 'Options', 'Customize IDE' and select the 'Tools' tab. Select 'New Tool' and type in the desired name to display (i.e. Dialog System) and then select 'Program' and navigate to: C:\\Program Files\\Micro Focus\\Net Express\\DialogSystem\\BIN\\DSWIN.EXE Dialog System should now permanently be on the 'Tools' dropdown. Old KB# 5220

Problem: What is a return code of 128 from STOP RUN/GOBACK? Resolution: If a program simply terminates with a STOP RUN or GOBACK then the value returned to ERRORLEVEL is undefined.  Basically it could be anything from an OS value through to a piece of uninitialized memory. When using ERRORLEVEL with a COBOL program then it is necessary to explicitly control/set it within the program code.  For example:      ...      move 12 to return-code.      stop run. or      ...      stop run returning 12 size 4. or      ...      move 12 to return-code.      goback. or      ...      goback returning 12 size 4. Old KB# 5192

Problem: Trying to install Net Express 4.0 from CD. Receiving error cannot  write to silent script log file unable to continue Logged on as administrator, TMP and TEMP point to C:\\temp Resolution: Running the following command where X: represesent the CD=Rom drive installed the product X:\\SETUP\\SETUP /INI=X:\\SETUP\\NXSETUP.INI /LOGFILE=C:\\TEMP\\SETUPLOG.TXT Old KB# 5202

Problem: Net Express 4.0 on 32 bit Windows. When running an application an error stating that the runtime DLL OOPS entry point is not recorded in the Windows registry occurs. Resolution: This error is normally caused by previous versions (e.g. Net Express 3.1) of runtime files being picked up via the PATH.  Carefully check the PATH setting via Net Express command prompt and ensure no rogue entries are present. Old KB# 5222

Problem: The following error is received during the install. Failed to set up Integrated Development Environment. At least one Net Express option failed to install. Please exit setup and start install again. Resolution: Check the share path to the server for spaces. If there are spcaes in the path, remove the spaces and attempt the install again. Old KB# 5245

Problem: The output file seems to be sorted incorrectly. Resolution: Perhaps the file was to be sorted in EBCDIC order. Use the compiler directive native"ebcdic" . Old KB# 5237

Problem: Can Screens.GS be in another directory and be found at runtime or animate time? Resolution: Yes, by adding the directory that contains the GS files to the COBDIR they will be found at animation time. For deployment a safer method would be to follow the instructions in the packaging knowledge base article 4150. Old KB# 5244

Problem: Error received; "cannot run 16 bit window program - access to specific devise is denied" Resolution: copy cd installation to a directory on the hard drive that has no spaces in the name Old KB# 5201

Problem: How can the HIDE-OBJECT function be used in Dialog System dialog on a ListView? Resolution: The HIDE-OBJECT function cannot be used in a Dialog System dialog on programmed controls like a ListView or a TreeView. But the corresponding routine from the class library can be invoked in the control program. Please use the method "hide" of the class abstract window, which is inherited by the programmed controls:     INVOKE aControl "hide" This will hide the ListView. Old KB# 5207

Problem: Net Express 4.0 with .NET Does SQL(DBMAN=ADO) in .NET give access to all ADO.NET functionality? Resolution: The current version of Net Express with .NET documentation states: 1) Existing ODBC applications can be supported by using the SQL(DBMAN=ADO) compiler    option.  An application can use both ODBC and ADO.NET but not within the same    source program. 2) However, it is stated that ADO.NET does not have all the features of ODBC.  Also    the storage and performance characteristics may also differ. 3) Additional EXEC ADO statements have been added to Net Express with .NET.  These    allow access to the ADO.NET objects that OpenESQL uses at run time. Old KB# 5223

Problem: This article provides instruction and a demonstration regarding how one can detect when a program developed with Net Express with .NET 4.0 is running under the control of the CLR (.NET Common Language Runtime). Resolution: Functionally, the method of detection involves two steps: 1. use the MF function CBL_GET_OS_INFO 2. look at the bit 5 of cblte-osi-rts-capabilities When = 1, it means that the program is running under the control of the CLR The demo program showing how this is used follows.   Note: To run this demo, the latest update (ALL04N40.exe) needs to be installed in the Net Express 4.0 product.       $SET SOURCEFORMAT"FREE"        program-id. CLRprogOrNot as "CLRprogOrNot".        environment division.        configuration section.      

Problem: Using "inspect ... converting" to convert signed, EBCDIC numeric data to signed, ASCII numeric data. Resolution: The example program, "CONVERTING.cbl" (see attachement). illustrates how to use an "inspect ... converting" statement to translate EBCDIC numeric display values to equivalent ASCII numeric display values. The following syntax is used.       INSPECT identifier-1 CONVERTING identifier-6 TO identifier-7 "identifier-1" is a pic x(9) item initialized to a hexadecimal value 'F1F2F3F4F5F6F7F8D9' that is equivalent to "123456789-", a signed, numeric display value on an EBCDIC computer system. "identifier-6" is a table of the numeric EBCDIC characters that might appear in a signed, numeric display item. There are three groups of possibilities. The first group, (C0C1...), are positive, unsigned digits. The second group, (D0D1...), are negative, si

Problem: The GNT code will require that ANIM is located in another location other than the project directives. Cannot animate the GNT code. Resolution: The GNT code will require that ANIM is located in another location other than the project directives. It can be added to the project pull down menu. Projects      Types of Build              Debug      CHANGE                    OPT(1) ANIM    OK    CLOSE Old KB# 5219

Problem: File systems on different operating systems can use different size addressing. Most current file systems use 32-bit or 64-bit addressing. The operating systems/file systems using these two sizes are listed below. Resolution: The File Handler is configured to work with either 32-bit or 64-bit addressing. It is vital that all applications sharing a file use a File Handler configured the same. Otherwise, data corruption can occur. You can configure the File Handler to use 32-bit addressing in a file system that uses 64-bit addressing. In this case, all files will be safely limited in size (to 32-bit addressing) by the File Handler. 32-bit file systems: - Windows 95 - Windows 98 - Windows Millennium - Windows NT (FAT) - Windows 2000 (FAT) - Windows XP (FAT) - UNIX without large file system enabled 64-bit file systems: - Windows NT (NTFS) - Windows 2000 (NTFS) - Windows XP (NTFS) - UNIX large file system - Linux File syste

Problem: Is there a way to call a .NET DLL (VB.NET) from a DLL developed in NX 4.0?, and if there a way to call a VB 6.0 DLL from a NX 4.0 DLL?. Resolution: When calling a VB.NET dll from a Net Express 4.0 .dll,you need to expose the VB.NET dll as a COM object. You can use the regasm command on the vb.net dll to expose it. Once you have done this, then you will need to call it by using INVOKE's from COBOL, using OO COBOL syntax in the same way as you would when calling a COM object from COBOL. Old KB# 5194

Problem: Net Express install displays message that application server is installed. Resolution: To workaround this error message when attempting to install Net Express 4.0, the following needs to be done: Using the REGEDIT tool, rename: HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\Currrent Version\\Uninstall to HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\Currrent Version\\Uninstall-temp Start the Net Express 4.0 setup. When the first setup screen is displayed, rename the key back to HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\Currrent Version\\Uninstall Continue the setup. Old KB# 5240

Problem: The user is creating com objects with Net Express 4.0 . On  his developement machine they work fine, but on his production machine when he tries to register the com object using regsrv 32 he receives the following error message: "runtime dll "oops version 4.0, entry point "oops" not recorded in registry not found or incompatible". He has application server for Net Express with .net and application server for Net Express 4.0 installed on production machine and they both have lastest updates applied. Resolution: Adding the location of Application Server for Net Express 4.0 to the path environment variable  resolved the problem Old KB# 5216

Problem: A program has been developed and compiled on Net Express and then copied over to a UNIX machine. When running the program on the UNIX system, an RTS0165 error is encountered.   Resolution: The problem here is that there is likely a library file or COBOL module which isn't looking in the correct pathname caused by a missing or wrong $COBDIR, or a newer version of Object Cobol Developer Suite, Server Express, or Application Server has been installed while parts of a previous product installation have not been removed correctly. Therefore a check should be done of the opt/lib or cob/lib  (or shlib) and also where the $COBDIR is pointing to.  If it is unknown which versions of product modules and libraries that are installed on the system on which the error is encountered, it is advisable to remove the products completely and reinstall the product to insure that the modules available are not from mixed product releases.