Rocket® COBOL

Problem: "COBOL Rocks the World" optional workspace backdrops (wallpaper) for Net Express Resolution: BUILD W/RELEASE:      Net Express v3.1 ===========           Net Express v4.0 INTRODUCTION ========== These are additional workspace backdrop bitmap files which can be   optionally used within the IDE. SOURCE FILES: ========== Program Files               Description --------------------         ----------------------------------------------------------- cobolrocks.bmp           "COBOL Rocks" workspace backdrop (largest in size) cobolrocks16.bmp       "COBOL Rocks" workspace backdrop with 16 colors cobolrocks256.bmp 

Problem: Sample that demonstrates how to add a version label to an EXE Resolution: INTRODUCTION ========== The project file VersionNo.APP is used to demonstrate how to add a version label to your executable, EXE or DLL. This is accomplish by using an RC file.  To change to content of the RC file simply edit it as Text and modify it appropriatly to reflect your desired values To find out more about the parameters of the RC file please consult the WIN32 SDK documentation. SOURCE FILES ========= Program Files         Description -------------------     ----------------------------------------------------------- VersionNo.APP VersionNo.CBL VersionNo.RC ========================================================== Keywords: demonstration, sample, example, demo, versionno.zip demo.ex demo.ne Attachments: versionno.zip Old KB# 4032

Problem: This example illustrates how to format and use long file names with call-by-name routines. Resolution: =========== INTRODUCTION ========== This example illustrates how to format and use long file names with call-by-name routines. SOURCE FILES: ========= Program Files     Description ----------------     ----------------------------------------------------------- Cbnrndlf.cbl       Example program that uses call-by-name routines and long file names. OPERATION: ======== Rebuild the example program and then Animate the program. As you step through the program you will see that the text file in the project directory (LongFileName.txt) is copied and assigned the name "CopiedFile.txt". Next, the new file is renamed "RenamedFile.txt". Finally, the new file is deleted. NOTE: ==== The three constants that follow provide three long f

Problem: Calling Microsoft Word from Object COBOL Resolution: INTRODUCTION ========== Demonstrates how to invoke Microsoft Word from a COBOL program. SOURCE FILES: ========== Program Files     Description ----------------     ----------------------------------------------------------- ooword.cbl         COBOL program that invokes MicroSoft WORD. REQUIREMENTS: ========== Microsoft Word. OPERATION: ======== Rebuild program. All of the necessary directives are located at the top of the program. Start animating and step through the program. Microsoft Word is invoked when you execute the statement 'invoke theWord "setVisible" using by value 1' and appears in the background. ========================================================== Keywords: demonstration, sample, example, demo, ooword.zip demo.ex demo.me demo.ne Attac

Problem: In an existing application the "Blink" attribute is used fairly often.  Now, having recompiled for use in Windows (with NetExpress), the blink attribute does not work.  I have checked through the online manuals and the old Micro Focus manuals and the only references I have seen are to do with Accept and Display, however there is a mention of creating a .ini file with the entry COBBLINK=ON.  I have tried this and there is no change.  Is there any other way that I will be able to get this to work. This has been tested on Win 98 and Win 2000 Resolution: The BLINK attribute, used in ACCEPT and DISPLAY statements does not work as you would expect on Win32. Nor, indeed, does it work on Windows 3.x or OS/2. On a windowed operating system, blinking the attributes would be very expensive in terms of processor usage so instead the systems provide the ability to apply intensity to the background colours. The

Problem: This example program demonstrates the use of Exception Handling when working within an OLE environment. Resolution: INTRODUCTION ========== This example program demonstrates the use of Exception Handling when working within an OLE environment. This program contains two entry points. The first entry point is the default Procedure Division for TestException. This is where execution begins. The second entry point is named "MyHandler" and it contains the Exception Handling code which will be called whenever an OLE Exception occurs during the processing of TestException. Two parameters are automatically passed to "MyHandler" by the OLE Exception Handler within the Net Express run-time system. The parameters are defined in the Linkage Section and they are defined as:        01 lnkExceptionObject           object reference.     &n

Problem: CBL_DEBUGBREAK does not work when COBOL is called from a .Net WebService. In this case the .Net Web Service is C# based and calls COBOL via a Platform Invoke. The COBOL is unmanaged and issues a CBL_DEBUGBREAK call. The debugger never appears. Resolution: At a Net Express Command Prompt you can issue "cblcored -i". This sets up some security setting so that the Service can communicate with the desktop so that the debugger will start. Old KB# 3998

Problem: This sample demonstrates the features of the datewarp_dynamic and timewarp_dynamic runtime tunable. Resolution: INTRODUCTION ========== The project file DATEWARP-DEMO.APP demonstrates the features of the datewarp_dynamic and timewarp_dynamic runtime tunables.  You can see the description on these tunables and how to set it by starting the Net Express help, and selecting from the Index: datewarp_dynamic or timewarp_dynamic SOURCE FILES ========= Program Files                     Description ----------------------------     ----------------------------------------------------------- DATEWARP-DEMO.CBL     COBOL source program) MYCONF.CFG                    Run-time syste, configuration fil

Problem: Returns all valid drives on a PC using the PC_FIND_DRIVES library routines Resolution: INTRODUCTION ========== Returns all valid drives on a PC. SOURCE FILES: ========= Program Files            Description ---------------------     ----------------------------------------------------------- PcFindDrives.app     Application File DrivinF3.cbl              Source File DrivinFo.cbl              Source File OPERATION: ======== Open the application file and rebuild the project. Animate the program. The Application Output Window appears showing all available drives on your local machine. ========================================================== Keywords: demonstration, sample, example, demo,

Problem: How to trap COBOL errors using CBL_ERR0R_PROC Resolution: ============ INTRODUCTION ========== This project shows how to trap COBOL error messages using CBL_ERROR_PROC. SOURCE FILES: ========= Program Files     Description ----------------     ----------------------------------------------------------- CblTrap.APP       NetExpress project file Main1.CBL          COBOL source code Errorprc.CBL      COBOL source code Help Files: ----------------     ----------------------------------------------------------- Readme.TXT      This file OPERATION: ======= Here are few additional details about this project: o     The module (errorprc) that traps the Cobol error messages:    &nb

Problem: This project demonstrates the use of an OLE Automation object that returns a variant. Resolution: INTRODUCTION ============ This project demonstrates the use of an OLE Automation object that returns a variant. You can use an object reference as a return type in this case to hold an instance of the OLEVARIANT class. Variant string types will get converted to a character array object so check for that type on the return data.                                                 SOURCE FILES: ========= Program Files                     Description ----------------------------     ---------

Problem: Can you create a screenset that has a Cancel button that will terminate some processing code? Some of this text refers to the accompanying demo.        There may be times when your Dialog System application has to execute        some process that you may want to cancel at some point. If your        processing is done in a long-running loop in the COBOL program, then any        button that you may have on a window cannot respond to click events        during that processing.        If you want to have a Cancel button to stop processing, you will need to        break up your long-running process into small units of work, where at the        end of each unit, you will call Dialog

Problem: This demo, "AfterAdvancing", creates a file using the "After Advancing" clause, that includes carriage return, line feed and form feed characters, unlike a program using "after positioning." The print program uses Byte-stream File Routines to read the report file, preserving the PC printer control characters, and providing control of the printer and font used to print the report. Resolution: INTRODUCTION ========== This example illustrates how to use a report file created by a COBOL  program using "after advancing" syntax. SOURCE FILES: ========== Program Files      Description ----------------      ----------------------------------------------------------- Opcw32aa.cbl     osvsaa.cbl OPERATION: ======== The example consists of two programs. OSVSAA.CBL is the program that uses  "after advancing

Problem: Demonstrates the use of the OpenDialog class from the COBOL GUI class library that shows a File Open Dialog Box and displays the file selected. Resolution: INTRODUCTION: ========== Demonstrates the use of the OpenDialog class from the COBOL GUI class library that shows a File Open Dialog Box and displays the file selected. SOURCE FILES: ========= Program Files             Description ----------------------     ----------------------------------------------------------- FileOpenDemo.cbl      COBOL source file. REQUIREMENTS: ========== Installation of the GUI class library source files option during NetExpress setup. OPERATION: ======== Run this program to display a File Open dialog box, select a file, and the file name and path will be displayed. Use of the class library requires you to link with the shared cobol runtime

Problem: Extract of Net Express documentation:                   search on keyword rargument-number Accessing Data on the Command Line There are two main ways in which a program can access data on the command line: ACCEPT data-name FROM COMMAND-LINE. This causes the complete contents of the command line to be moved to data-name. Alternately, you can access individual arguments on the command line, using: DISPLAY ... UPON ARGUMENT-NUMBER ACCEPT ... FROM ARGUMENT-NUMBER Resolution: Code attached to KB:        working-storage section.        01 Args-Work-Area.         03 args-num                pic x(4) comp-x.         03 args-val&nbs

Problem: This demo displays and changes the contents of an environment variable Resolution: INTRODUCTION ========== Displays and changes the contents of an environment variable.      SOURCE FILES: ========= Program Files           Description --------------------     ----------------------------------------------------------- EnvVar.app             Application File EnvVar.cbl               Source File OPERATION: ======== Open the application file. Rebuild and animate the project. The Application Output window displays the environment variables from the COBDIR then displays "Variables not found", & "Not there" ========================================================== Keywords: demons

Problem: This error appeared when trying to publish to LINUX with the UNIX Option in Net Express. The version of Net Express used was 3.1 and on LINUX Server Express 4.0 was installed. Resolution: This will work but ONLY if you have the latest nx31 unix publisher fixpack\\websync installed. Installing this fix patch solved the problem. Old KB# 3995

Problem: This example illustrates how to use two related call-by-name routines CBL_EXIT_PROC and CBL_GET_EXIT_INFO. Resolution: INTRODUCTION ========== This example illustrates how to use two related call-by-name routines CBL_EXIT_PROC and CBL_GET_EXIT_INFO. These routines permit the consolidation of error reporting within a single application procedure. This example also illustrates how to use the x'F5' call-by-number routine. SOURCE FILES: ========= Program Files     Description ----------------     ----------------------------------------------------------- Quitter.cbl          Example program illustrating the use of CBL_EXIT_PROC and                            CBL_GET_EXIT_INFO. OPERATION: ======== The Qu

Problem: View is a 32-bit, character mode, text file viewer. It can be created as a character mode or graphical executable. It uses call-by-name routine x'AF' to initialize Adis, and compiler directive FileType"14" to create a temporary, relative file. Resolution: INTRODUCTION ========== View is a 32bit, character mode, text file viewer. It can be created as a character mode or graphical executable. It uses cal-by-name routine x'AF' to initialize Adis and compiler directive FileType"14" to create a temporary, relative file. SOURCE FILES: ========= Program Files: -------------------     ----------------------------------------------------------- View.cbl                  A character mode, text file viewer. xBorder.cbl             A sub program th

Problem: This demo shows using intrinsic functions to validate Gregorian dates and create a date such as "Monday, April, 09, 2001". Resolution: INTRODUCTION ========== Using intrinsic functions to validate Gregorian dates and create a date such as "Monday, April, 09, 2001". SOURCE FILES: ========= Program Files         Description -------------------     ----------------------------------------------------------- Calendar.cbl          A main program that requires a "verbose" date. The date should have                               the names of week days and months with the week day, month, numeric day          &

Problem: Document and sample code which defines the COBOL CALL statement Resolution: =========== INTRODUCTION ========== This demo shows how to make calls to Btrieve by directly calling the _btrv module as you would make calls to the Btrieve API instead of using the xfh2btr call conversion module and COBOL file i-o syntax. SOURCE FILES: ========= Program Files     Description ----------------     ----------------------------------------------------------- btrvtest.cbl       The demo program. Copy Files: ----------------     ----------------------------------------------------------- btconsts.cpy      Btrieve operation codes. REQUIREMENTS: ========== This demo was tested using NetExpress 3.1, along with either Btrieve 6.15 or Pervasive SQL 7. OPERATION: ======== The program makes 3 calls to _btrv

Problem: This demo demonstrate how to call the File Handler, EXTFH directly from a COBOL program. Resolution: ============ INTRODUCTION ========== This demo demonstrate how the File Handler, EXTFH can be called directly. OPERATION: ======== The zip file consist of 2 samples, one showing how to read and write to an index file while the other shows how you can create and read a line sequential file. NOTE: ==== For more details on how to call the File Handler please refer to the File Handling Programmer's Guide in Chapter 7. ========================================================== Keywords: demonstration, sample, example, demo, extfhdemos.zip demo.ex demo.me demo.ne demo.se Attachments: extfhdemos.zip Old KB# 4006#ServerExpress#COBOL#AcuCobol#RMCOBOL#netexpress

Problem: What does this error mean? Resolution: The MF-code error 14657 = 9/065 file status. You will get a better status code when you define this as follows:    01  Ws-File-Status.            05  Ws-File-Status-1            pic x(01).            05  Ws-File-Status-2            pic x(01).            05  Ws-File-Status-N            pic 9(02) comp-x                redefines Ws-File-Status-2. Thus 9/065 = file locked. With the  lock mode clause, the default lock mode is set t

Problem: This program demonstrates how to use the UPSI external switches and the accept parameters with Net Express. Resolution: INTRODUCTION ========== This program demonstrates how to use the UPSI external switches and the accept parameters with Net Express. SOURCE FILES: ========== Program Files          Description --------------------     ----------------------------------------------------------- PARMPASS.APP      Application to build the PROGRAM1.EXE PROGRAM1.CBL     Source program for PROGRAM1.EXE PARMBASS.BAT      BAT file to be loaded into DEBUG directory where the EXE is loaded or                                 recreated vi

Problem: Release 4.0: We do have Microsoft's Visual Studio.NET 2002, is there a possibility to run Net Express 4.0 .NET? Resolution: No, according to the readnet.txt file included in Net Express 4.0 .NET (as per June 2006) you will need to have an environment basically as follows: Software Requirements    ---------------------    Net Express with .NET is supported on the following operating    systems:     - Windows XP Professional     - Windows 2000     - Windows Server 2003        The following software must be installed:     - Microsoft Visual Studio .NET Premier Partner Edition       (supplied with Net Express with .NET) or any other edition       of Microsoft Visual Studio .NET 2003     - Microsoft .NE