Rocket® COBOL

Problem: Does the SET OPTION QUERYTIME option affect all queries executed on a connection or only those in the same COBOL module? What is the minimum value that can be used? Resolution: If SET OPTION QUERYTIME is specified, it is used for all subsequent SQL operations within that thread, hence any subprograms will effectively inherit that setting. This is also true if you have multiple connections within a single application thread. The option passed to QUERYTIME specifies the number of seconds that the program waits for a response to an OpenESQL statement. According to SQL Server documentation, the minimum value is 0, which means no timeout, but the lowest timeout is 1 second. Old KB# 6919

Problem: You can reference an external MS VB.NET DLL from a solution or project. Resolution: The MS VB.NET DLL must be added as reference in the solution by following the steps below: 1. right-click on References, which is in his Solution Explorer 2. select Add Reference 3. click on Browse button to get the DLL 4. click on the Open button 5. click on the OK button. Old KB# 6932

Problem: When using a ListView in Net Express Dialog System, the method "allowItemsToBeEdited" only relates to the first column of the List View. Resolution: This method does only allow items from the first column to be edited. To edit the other columns, you would need to use a form of grid control, such as Proto View (demo available in in \\dialog system\\demo\\activex\\custgrid.app ). This demo uses grid control software supplied by a company called Infragistics on an evaluation basis for testing. Go to  <http://www.infragistics.com/download/downloads.asp> to download the evaluation version of the grid control software to use with the Net Express custgrid demo. Old KB# 6915

Problem: You may have multiple push buttons on a Dialog System screen and want to be able to tab between them. Resolution: Enclose the push buttons within a group box. Old KB# 6938

Problem: Compiling this statement             EXEC SQL              SELECT                     nextval for myseq              INTO                   :hostvar                FROM MYTABLE WHERE COL1 = 10             END-EXEC returns this compiler error : COBES0100S Incorrect SQL statement syntax near    : sample.cbl(23,20) Resolution: OpenESQL is designed to support ANSI-standard SQL. As the NEXTVAL and PREVVAL clauses are not part of the

Problem: Description: OLESUP method "adviseEvents" gets error 243 - class could not be loaded The class olesup cannot load the event handling class because the case of the event handling class name does not match the case of the class name in the program using olesup. When using the olesup "adviseEvents" method to register an event handler, keep in mind that the class names default to lower case. In this case, you should specify the class name literal in CLASS-CONTROL as lower case in the program where you invoke the "adviseEVents" method of the olesup class: CLASS-CONTROL.     MYEVENTCLASS IS CLASS "eventhandlerclass". If you specify the class name in upper case ("EVENTHANDLERCLASS"), then make sure that you add an entry in CLASS-CONTROL in the event handling class such as: CLASS-ID. EVENTHANDLERCLASS, INHERITS FROM OLEBASE-E.   CLASS-CONTROL.      

Problem: WINDOWS scripting ( .wsf) to update registries for Application Server 3.1 or 4.0  and Application Server KEYS DataBase on a computer where Application Server  and Application Server KEYS DataBase are not installed. ( The aim is to use an Application Server and an Application Server KEYS DataBase available on the network ) . Updating registries -> you'll be able to run on a PC where Application Server not installed .EXE application linked as shared DYNAMIC ( dynamic meaning i find in registries the location of the Application Server ) Resolution: ====== Modify csetas40env.bat so parameters AS40InstDir et AS40LMFDIR  conform to your environment Modify: ASLMF=ASLMF ( and not ASLMFx )   AS40RegistryEntry=Net Express\\4.0\\COBOL\\4.0\\Environment launch in a DOS prompt: csetas40env.bat ====================================

Problem: 173 Error calling a VB DLL Resolution: VB6 DLLs are actually COM DLLs. You should not use the CALL statement to call then. You should use the COM Support in Net Express. The Distributed Computing section of the help details the syntax requirements. In summary you need a class-control section with something like:-    mycomclass is "$OLE$theVBprogid" and then use the INVOKE verb to call the COM methods. Old KB# 6906

Problem: Customer is encountering a problem in publishing a method in Web Services.  He's following the tutorial - compiles the Hello Word program, asteriscs it etc.  When he comes to creating the client part adding the Web Service part he says that the Hello World method is not published and he cannot see it. Resolution: This problem may actually occur with any service that is selected from the Add Web Reference wizard. This simply means that the file name extension (.asmx) was not mapped to any program or interpreter that processes that type file. Here are the steps to map that file name extenstion to the program or interpreter: 1. Find out if there are different versions of the MS .NET Framework installed on the machine 2. Determine which one (if there are more than one version) is the latest version by looking at the directory name (e.g. C:\\[Windows directory]\\Microsoft.NET\\Framework\\v1.1.4322 is more recent than C:\\[Win

Problem: Using Sybase with Net Express may return RTS114 error Variables defined in Sybase-provided copyfiles, cobpub.cbl and sybhesql.cbl, are defined as USAGE COMP. This does not match the byte ordering expected by Sybase. Resolution: In the Sybase-supplied copyfiles cobpub.cbl and sybhesql.cbl, change all data items defined as USAGE COMP to USAGE COMP-5. Old KB# 6882

Problem: Using Net Express Version 40 OpenESQL interface: What to do to get locked records similar to COBOL's locked records using ISAM files? Resolution: Firstly, you should turn on the SQL(DBMAN=ODBC) compiler directive: IDE: Project -> Properties -> SQL Directives... This ODBC interface has a wide range regarding the use of relational databases, if you are using Microsoft's SQL SERVER you should add the TARGETDB=MSSQLSERVER option as well. To control a CURSOR behavior you should set the SET CONCURRENCY LOCKCC option to get locked rows after a FETCH. This option should be set by default unless the ESQLVERSION option is set to 2.0, then the default should be set to OPTCC (optimistic). Old KB# 6892

Problem: The sample program below illustrates various methods of invoking an Oracle stored procedures and functions. This COBOL program illustrates invoking these procedures and functions with positional values, that is the physical order of the input data in the CALL is associated, in order, with the stored procedure and functions parameters as defined in the CREATE statement.  This sample program also demonstrates the use of an Oracle package.  An Oracle package is just a logical way of grouping objects together.  It consists of a specification which identifies the interface to each object (stored procedure and function) and the body, which implements the procedural logic. The procedures and functions are very simplistic but demonstrate the mechanism for creating and calling ORACLE stored procedures and functions through the ODBC interface in Net Express. Resolution: The package GETCOUNT contains a stored procedure 'gcount_sproc&

Problem: What is 4DOS and is it supported on Net Express? Resolution: Basically it has never been officially certified on Net Express and is, therefore, not supported. 4DOS will run on Windows 95, 98, or ME, and the associated MS-DOS versions (7.0 and above).  The equivalent for Windows NT, 2000 and XP is a product called 4NT. Here's a description of what it is and can do. By adding a wide array of features that DOS omitted, 4DOS makes the command line easy to use, giving you more power and flexibility than you ever imagined. 4DOS replaces the DOS command processor, COMMAND.COM - the brains behind your "C:\\>" prompt. 4DOS adds features such as shorthand "aliases" for commonly used commands, a pop-up directory history window, and the ability to copy, move, delete, or list multiple files with a single command. Simple command-line editing, history, and recall eliminates extra keystrokes, and the FFIND command can quic

Problem: Error on COMPILE on a 88 level item defined as USAGE COMP SYNC in DECLARE SECTION using Oracle Pro*COBOL 1.8. Resolution: The COMP SYNC is being converted to COMP-5 SYNC within the DECLARE SECTION. This will work if the host variable is defined within a SQL INCLUDE file, but not when it is defined within the main program. This can be resolved by specifying the Pro*COBOL directive COMP5=NO. Old KB# 6907

Problem: Install This page explains how to install Net Express, Net Express with .NET and Net Express Professional Edition, and the other software on the CD. If you want to create applications (using Microsoft Visual Studio .NET) to run in the Microsoft .NET framework, then follow the instructions for installing Net Express with .NET. If you want to create Windows applications that do not run in the .NET framework, or if you want to create applications to run on UNIX, then follow the instructions for installing Net Express 4.0. Warnings: If you install Net Express with .NET and either Net Express Professional or Net Express 4.0, you may be asked to reboot when Net Express Professional/Net Express 4.0 has completed installing, but before Net Express with .NET has started installing. Do not choose to reboot your machine until the Net Express with .NET install has completed. You may need to minimize the Setup window to see the dialog box for the install of Net Expr

Problem: It seems that a PREPARE statement is not running correctly within an OpenESQL application using dynamic SQL. You may also find the SQL Descriptor Area (SQLDA) structure is not set as expected. Resolution: You should check your application regarding the SQLDA items SQLN and SQLDABC first because it is a must to initialise these items before you can run PREPARE. SQLN This must be set to the maximum number of SQLVAR entries that the structure can hold. SQLDABC The maximum size of the SQLDA. This is calculated as SQLN * 44 16 Old KB# 6894

Created On:  21 March 2011 Problem: When deploying a web service you get the following error in a dialog box:<html><head><title>Error - File Not Available</title><meta name="robots" content="noindex"></meta><body><h2>HTTP Error 404 - File Not Available</h2><p>The requested file is not available</p></body></html> Resolution: A 404 error at the beginning of the deployment operation almost certainly means that MFCS was unable to locate either the mfdeploy.exe program or one of its path components, or one of the path components in the PATH_INFO portion of the URL.Once the CAR file has been built and the server's deployment listener has been contacted, the deployment client (here the IMTK) does an HTTP POST operation to send the CAR file to the deployment receiver program, mfdeploy.exe. It uses a URL that specifies the virtual path to mfdeploy.exe and the virtual path to the dep

Problem: Don't want to silently install the base release but have the latest service pack installed in the process. Resolution: Currently the only way would be to put the following steps in a bat file, need to create the runtime files to be copied, easiest way is to install lastest service pack on a machine and use this as the basis for files which need to be copied. 1.  copy runtime files and set path (when running a deployed application, will have to ensure that path  is set to point to these runtime files) 2.  set up a new license database     a. Create a directory to contain the new license database, if necessary.     b. Copy into that directory the files prodfile and semfile from application server folder     c. Run the aslmpclocate utility as follows:               aslmpclocate license-db

Problem: How do you specify location of copybooks and include files using Oracle ? Resolution: There are two ways to resolve the location and expansion of copybooks.  One is through the use of Oracle's Pro*COBOL INCLUDE option and the other is by using the CP pre-processor along with setting COBOL's COBCPY environment variable.  The assumption being made is that the copybooks contain either embedded SQL statements or the declaration of host variables used in embedded SQL statements and the copybooks are not located in the source/default directory. (1) Using Oracle's Pro*COBOL INCLUDE option. This solution only works if the copybooks are included with the EXEC SQL INCLUDE statement. (and extension is cob). This is the easiest solution since Pro*COBOL automatically expands files included through the EXEC SQL INCLUDE statement if they can be located.  In order to specify the location, use Pro*COBOL INCLUDE option for

Problem: Error when registering a COM Server created using Interface Mapping Toolkit. File not found. Resolution: This error can occur as the COM DLL is dependant on the comservices.dll that resides in the base\\bin where you installed Net Express. If you add base\\bin to your path then the DLL will register correctly. Old KB# 6902

Problem: Here are few notes from documentations about migration from old Dialog System to Net Express Resolution: Chapter 8: Dialog System V2.5 This chapter lists some points to note if you're moving to the Dialog System in Net Express compared to Dialog System V2.5. If you've come from 32-bit graphical Dialog System V2.5 on Windows 95 or Windows NT, you should have no migration problems. There is just one minor incompatible change - see the section DSRUN below. The non-graphical versions and some little-used tools have been omitted. Source code templates are provided to enable you to use the new Class Library support for spin buttons, status bars, OCX controls, and a tree view control. You access the definition software from the Tools menu in the IDE. For advice on moving from 16-bit to 32-bit, and from other operating systems such as OS/2, see the chapter Same Screen, Different Platform in the online book Dialog System Guide . DSRUN The Gr

Problem: If you use charset"ebcdic" in a OpenESQL program that uses SQL Server you will get the following error when linking:- error : unresolved external symbol _OESQLEBC@12 Resolution: You need to link your EXE with  OESQLEBC.OBJ  that is supplied with Net Express Old KB# 6904

Problem: After adding an external reference (e.g. Microsoft Visual Basic . NET DLL), you might want to find out what classes, structures, properties, or methods are available in that external component. Resolution: Use the Object Browser. You will need to do few things before you can actually see the details about the external component since it will not be shown automatically: 1. click on the Customize that is just next to the Browse drop-down list 2. click on the Add button 3. click on the Browse button to find the component 4. click on the Open button 5. click on the OK button Old KB# 6934

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