Rocket® COBOL

Problem: No, add COPYEXT"CPY,COB"  directive to the Project | Properties | Project directives. After adding this directive use the Project | Update all dependency to update the project. Be sure that you have only one semi-colon as the last entry within the Project directives %FILENAME COBIDY(%TARGETDIR) WB3 WB CSI ANIM EDITOR(MF2) ENSUITE(3) COPYEXT"CPY,COB" Resolution: Old KB# 6979

Problem: "ERROR: (10) Requested main program entry point not found" when trying to compile a program that has a names larger than 30 bytes. Resolution: This is a limitation that is documented: Limits on Names, Literals and PICTURE Character Strings Language elements are limited to the following sizes: Language Element Maximum Size Alphanumeric literal values 2048 bytes PICTURE character string 30 characters PICTURE replication  (for example, n in PIC X(n)) 256,000,000 Program-Id name 30 characters Entry point names 30 characters Programmer defined words 30 characters External filenames  (for program source and object files, copyfiles, data files) 261 characters for the filename, 256 characters for the basename and extension together Dynamically loadable program names 261 characters for the filename, 256 characters for the basename and extension together. The first 30 characters must be uniq

Problem: Executing an OpenESQL application under .NET can return RTS173 against SQLASTRT when attempting to connect. Resolution: This is with .NET and needs the ODBCRW32.DLL added as a reference to the project. Old KB# 6996

Problem: Is it possible to add version information to a COBOL .dll or .exe? Resolution: It is possible to add your own version details to an .exe or .dll. First of all, you need to create an .RC file. Create the .RC file using a text editor - an example of the contents and parameters of the .RC file are below: 1 VERSIONINFO                                                             FILEVERSION    1,1,1,1                                        &nbs

Problem: PC_PRINTER_OPEN PC_PRINTER_SET_DEFAULT         PC_PRINTER_INFO PC_PRINTER_GET_FONT PC_PRINTER_SET_FONT PC_PRINTER_WRITE PC_PRINTER_CONTROL PC_PRINTER_CLOSE You may wish to know which API's are called from the PC_ routines... Resolution: To see the API's used, drop to a Net Express command prompt and change directory to the Net Express\\base\\bin folder and run the command LINK -DUMP -IMPORTS CBLPRNT.DLL Old KB# 6986

Problem: My program does not find the MFEXTMAP.DAT-file Resolution: 1. See handbook: Example of using the External File Mapper 2. Remember: the environment-variable MFEXTMAP points to a directory, rather than to the file itself 3. Try to use the dynamic runtime system 4. Try to read the environment variable MFEXTMAP, e.g.        01 actual-value pic x(60).        display "MFEXTMAP"     upon Environment-name        accept  actual-value       from Environment-value        display "Value of MFEXTMAP = " actual-value Old KB# 6988

Problem: "CGI Error: The specified CGI application misbehaved by not returning a complete set of HTTP headers." is the message the webserver will return when a web application (or cgi) cannot find or access the runtime files or other resources. Resolution: Application Server was installed on deployed workstation, application was linked with shared dynamic but no license had been installed to the Application Server License database. Entering a valid Application Server serial number and license key through AppTrack utility, found in the Application Server directory, resolved the CGI error. Old KB# 7000

Problem: Haven't you ever wondered why there is not a simple way of obtaining this, like an intrinsic function, or using INSPECT? Or maybe you have tried something like:        working-storage section.            77 ws-name                      pic x(50).          77 ws-count                     pic 9(03).          procedure division.            move "Micro Focus" to ws-name          inspect ws-name tallying ws-count for characters      

Problem: Net Express 3.1 is certified on Windows 95 (Windows 98 recommended), Windows NT V4.0 (Windows NT Service Pack #5 or later), Windows 2000, or Windows XP Professional. Net Express 4.0 is certified on Windows 98, Windows NT 4.0 (Windows NT Service Pack #6a or later), Windows 2000, Windows Server 2003 or Windows XP Professional. Net Express 5.0 is certified on Windows 98, Windows NT 4.0 (Windows NT Service Pack #6a or later), Windows 2000, Windows Server 2003 or Windows XP Professional and Windows Vista. NetExpress 5.1 is certified on Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP or Windows 2000 Resolution: Net Express 4.0, 5.0 and 5.1 are certified on Windows Server 2003. Old KB# 6960

Problem: 114 on 'acccgi' when running a COBOL CGI Application under Windows 2003 / IIS6 Resolution: This problem has been fixed in the runtime fixpack for Net Express 3.1 and 4.0. Old KB# 6952

Problem: WrapPack will fail or freeze when getting to the Runtime portion of the WrapPack Resolution: Prior to running the installation of the Net Express 4.0 All WebSync WrapPack, ensure that all Net Express applications are shut down. This also includes components of Net Express such as Enterprise Server, Fileshare, Net Express command prompts, Net Express for .NET, Net Express Help files and the Net Express IDE itself. To stop any Enterprise Servers that may be running on your development system, from the Net Express IDE click on "Tools > Enterprise Server Administration" to launch the Enterprise Server Administration Home page and for each Server which currently displays "Started" under the Current Status column, press the Details button directly under the status and then at the bottom of the Details page click on the "Stop Server" button Old KB# 6961

Problem: Launch the Run method of the COM WORD application component. in the COBOL sample pasted  below, the cobol program opens a file test.doc ( located on the current directory )  which contains a macro named MaMacro which receives a String parameter: Sub MaMacro(machaine As String)     MsgBox machaine End Sub Resolution:       *> This is required for OLE applications       $set ooctrl( P)        program-id. worddemo.        class-control.        *> OLE automation classes            wordapp is class "$OLE$word.application"            .        working-storage section.   

Problem: Error message; "Failed to set up Integrated Development Environment At least one Net Express option failed to install .please exit setup and start install again" Resolution: This can be caused by a problem with the 16-bit subsystem setup on the workstation To check if the 16-bit subsystem is setup properly; - Reboot your workstation to ensure that you are working in a clean environment.  *** Please ensure that you are log on as a user that has administrator rights *** - Once the machine is rebooted, move your cursor on your taskbar, right click and bring up Task Manager. - Go to Start/Accessories/Command Prompt to start a Command Prompt. - type the following command; command.com, and press enter.   - Under normal circumstances you should see a new process in your Task Manager called NTVDM.EXE - If you have a problem, you should see and error message usually something like; "WOW NTVDM illegal instruction m

Problem: The following statement has caused a compiler error "Operand TALLY is not declared":   DIVIDE WS-VALUE1 BY WS-VALUE2      GIVING TALLY REMAINDER WS-VALUE3               Resolution: The TALLY special register is a syntax that is not standard COBOL but is part of IBM Syntax. To use this you need to enable it using either the OSVS or VSC2 compiler directives. If you use either of these then your program will compile cleanly. Old KB# 6991

Problem: With every attempt to print, the print job shows in the print queue as "spooling", and never changes status.  On exiting the application, the job disappears from the queue. Resolution: The following settings will work once the Net Express 4.0 Application Server Service Pack (currently aps03a40.exe) has been applied. Click "Start" (button). Point "Settings" (group) and click "Printers and Faxes" (button). Click the printer-name you want to select. Right mouse click on the printer- name that you want to use and click "Properties" (button). Click "Ports" (tab) and confirm LPT? is selected. Click "Advanced" (tab). Click "Always available" (radio button). Click "Spool print documents so program finishes faster" (radio button). Click "Start printing immediately" (radio button) Click "Print Processor" (button). The default Print Pr

Problem: Net Express doesn't appear to integrate with Seapine Surround source control, how do I make that relationship. Resolution: You can use any SCCS that conforms to the Microsoft Common SCC Interface spec. The Net Express Source Control module will use the SCCS interface specified in the registry under MyComputer\\HKEY_LOCAL_MACHINE\\SOFTWARE\\SourceCodeControlProvider\\ProviderRegKey. The last SCCS to be installed should be register itself here, so the last SCCS installed on the machine will be the one used by the Net Express Source Control module. Make sure that Net Express is not up when software is installed,  Net Express only looks for a Source Code Control System when it is first opened. Opening Net Express after the installation will show SourceControl in the menu bar. Old KB# 6955

Problem: Using different ODBC drivers resulting in an ODBC error 900 "Invalid SQL string": EXEC SQL AT DBO         PREPARE DYNSQL FROM :DB-SQL END-EXEC. Resolution: OpenESQL soes not support using the AT clause with SQL PREPARE statements, so remove the 'AT DBO' from the statement. Old KB# 7004

Problem: When installing to a machine that doesn't have a c:\\ drive you may see the message appear: "Cannot write to silent script log file. Unable to continue install" Resolution: The setup process attempts to create a log file on the c:\\  drive by default, and if you don't have a c:\\ drive, it can't write the log. To avoid this problem, you can redirect the log file elsewhere by supplying a parameter to the setup command: From a command prompt, change directory to the location of the setup.exe (let's assume this is on D:\\) and type the command: D:\\setup\\setup.exe /ini=d:\\setup\\nxsetup.ini /logfile=x:\\thelogfile.txt This will run the setup.exe from your D:\\ drive and write the logfile to your x:\\ drive. Old KB# 6993

Problem: A program contians some DOS LineDraw characters which can be seen correctly in Net Express but which cannot be printed with Windows. Not even using various PC_PRINTER routines will solve the problemt.  The characters can be printed correctly in DOS on port LPT1 but are treated differently when using a deskjet or laser printer via the USB port. Resolution: The issue lies with the DOS LineDraw characters which are part of the OEM character set. The problems is that Windows Fonts are based on the ANSI code page. In the Net Express IDE you can edit in an OEM font by using Options/Edit/Dos Compatability. If you switch to OEM then you should see that characters correctly in the editor. However when printing you get this problem. What some customers have done in the past is to install and use a font that supports the OEM Line Draw characters. Microsoft used to ship a font "MS LineDraw" for this which can be found at: http://www

Problem: Is cblfh.dll required when deploying a COBOL.Net File Handling application ? Resolution: If you are using a release prior to April2004 then it is required. From the April 2004 WebSync the COBOL File handler is now managed code and therefore does not require the unmanaged file handler to be on the system. Old KB# 6953

Problem: When using an extfh.cfg file to access a file >6GB that is located using a physical path, often the physical path is mistakenly configured as:     [\\\\TESTING\\\\DATA\\\\TF.DAT]     IDXFORMAT=8     FILEMAXSIZE=8 Resolution: To configure a physical path in an extfh.cfg file, you need to enure that an extra set of \\\\ characters are at the begining of the path, so in this instance it should read: [\\\\\\\\TESTING\\\\DATA\\\\TF.DAT]     IDXFORMAT=8     FILEMAXSIZE=8 Old KB# 6971#RMCOBOL#COBOL#netexpress#ServerExpress#AcuCobol

Problem: The error was encountered when running Net Express from a DOS prompt. The error refers to the runtime, and the compiler starts without any problems. Resolution: This occurs when there are other software products installed in the same path as the Net Express installation.  In this case, some old DLL files of a previous version of Net Express were found on the path of the new Net Express installation.  Removing these DLL files the problem no longer occurs.   Ensure that path where you install Net Express is free of any existing Net Express installations, or other software products. Old KB# 6977

Problem: Is it possible to  link to existing btrieve module in net Express with .Net? Resolution: Making calls to the Btrieve entry point "_BTRV" cannot be done directly from a .NET managed code program because the Windows 32-bit Btrieve library WBTRV32.DLL is, itself, an unmanaged Windows .DLL. In order for a .NET COBOL program to call an unmanaged .DLL, it must use the PInvoke functionality. In this case, you cannot use the _btrv.gnt file as only Windows .DLLs can be added as references to a .NET project. Use the following steps: 1.  In the Net Express\\base\\lib directory their is a file called _btrv.obj.      Create a Net Express 4.0 project which packages this file as MFBTRV.dll (or any name) and under Link options the entry point name should be "_BTRV". 2.  In your .NET project, right click on the References folder and select "Add Reference". Use the Browse

Problem: An stack overflow error or a  stackOverflowException can be easily corrected by increasing the size of the stack. Knowledge base article 19007 - "STACK OVERFLOW, EXCEPTION_STACK_OVERFLOW <- increase stack's size of the process" describes how can you set up an environment variable to define a specific stack size when the executable is being created when linking. This article describes how you can increase the size of an executable once it has already being created. This affects to any kind of executable, even a .NET executable. Resolution: There is an SDK utility called editbin that allows you to change the stack size for an executable (amongst other things). Open a command prompt and cd to the directory where your application executable is, and then run:    editbin /stack:nnn application.exe where application.exe is the name of the executable of your application and nnn is the number of bytes in siz

Problem: when opening  a file in the data file editor - it is not loading the structure file that was created Resolution: if you open a file and the editor does not use the structure file automatically you can do File (form top tool bar) - datatools - load record layout if the str is in the same directory as the file with the same name - it will automatically use the str in the editor Old KB# 6958