Rocket® COBOL

Problem: You may want to know the service pack level you have on Applicaiton Server for Net Express to determine what version of All WebSync WrapPack you want to apply on Net Express. Resolution: One way to determine the level of service pack on Application Server is to look for APSxxAnn.TXT where xx indicates the service pack level and nn indicates the version of Net Express. This text file contains the descriptions of the service pack, and it is copied over during the install of the service pack. If the file is not present, this would indicate there was no service pack applied with Application Server. To make sure this is the case, you can look for CBLRTSS.DLL, right-click on it, click on Properties, click on the Version tab, and see if there is "Special Build Description" in the Item Name list. This item name would specify the RTS WebSync version. If this item name is not listed, this then confirms no service pack was applied for Applcation Server.

Problem: Net Express documentation regards to  File Handler Configuration ---> File Handling: http://supportline.microfocus.com/documentation/books/nx40/fhpubb.htm      ...           Chapter 6: File Handler Configuration                       FH option BASENAME:  BASENAME=OFF is the default setting BASENAME The BASENAME option determines whether filenames specified in tags can be expressed without pathnames. By default, such filenames have to be expressed with full path information as passed to the File Handler by the calling program. By setting BASENAME=ON, it is possible to specify the filename without the path. Syntax: BASENAME={ON|OFF} Parameters: ON Filename tags can be expressed without path information. OFF All filename tags in the configurati

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: "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: This sample Dialog System application loads a PDF file in a Dialog System screenset and calls differents methods of the ACROBAT READER ActiveX control  to action on this activeX Resolution: 1) For further details, please refer to Net Express documentation, mainly: Bookshelf Net Express 4.0     http://supportline.microfocus.com/documentation/books/nx40/nx40indx.htm         Dialog System Guide             http://supportline.microfocus.com/documentation/books/nx40/dspubb.htm                 ....                 Chapter 22: Tutorial - Adding an ActiveX Control                 ... 2) Fo

Problem: This demo, "BeforeAdvancing", creates a file using the "Before 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 "before advancing" syntax. SOURCE FILES: ========== Program Files     Description ----------------     ----------------------------------------------------------- osvsba.cbl         opcw32ba.cbl OPERATION: ======== The example consists of two programs. OSVSBA.CBL is the program that uses  &quo

Problem: A series of nested programs demonstrating the use of COBOL Intrinsic functions Resolution: BUILD W/RELEASE:      Net Express v3.1 with fixpacks as of 05/2002 ============ INTRODUCTION ========== Series of nested programs demonstrating the use of Cobol Intrinsic functions SOURCE FILES: ========== Program Files     Description ----------------     ----------------------------------------------------------- Intrfunc.cbl OPERATION: ======== Simply rebuild project and follow program's instructions NOTE: ==== For more information on the COBOL Intrinsic functions please refer to the COBOL Language Reference. ========================================================== Keywords: demonstration, sample, example, demo, intrfunc.zip demo.ex demo.me demo.ne demo.se Attachments: intrfunc.zip Old KB# 4010

Problem: This example illustrates how to use COBOL syntax to create and access a Btrieve database. Resolution: INTRODUCTION ========== This example illustrates how to use COBOL syntax to create and access a Btrieve database. SOURCE FILES: ========= Program Files         Description -------------------     ----------------------------------------------------------- Create.cbl              Example program that creates a Btrieve database. Multiuser.cbl           A Multi-user example program that retireves records in a Btrieve database. REQUIREMENTS: ========== You will need a 32bit version of Btrieve installed in order to use this example. Pervasive 7 was used to develop and test these example programs. Both of the example programs need a directory to be cre

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

Created On:  19 June 2006 Problem: This demo returns information about the operating system environment via the library call CBL_GET_OS_INFO. This demo also demonstrate the usage of the Library Routine Type definitions and Call Prototypes. Net Express contains two copyfiles; one contains data items used by the library routines specified as type definitions, or TYPEDEFs, while the other contains call prototypes for the library routines. These can be used in your COBOL programs to enable the Compiler to validate all calls to these routines. Resolution: INTRODUCTION Returns information about the operating system  environment via the library call CBL_GET_OS_INFO.  This demo also demonstrate the usage of the Library  Routine Type Definitions and Call Prototypes.  Net Express  contains two copyfiles; one contains data items used by the  library routines specified as type definitions, or TYPEDEFs,  while the oth

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: The Micro Focus graphical, shared run-time system, character mode application fonts provide the means to obtain a large, nearly full screen window for character mode applications. Resolution: INTRODUCTION ========== The Micro Focus Graphical, Shared Run-time, character mode application Fonts provide the means to obtain a large, nearly full screen window for character mode applications. SOURCE FILES: ========= Program Files         Description -------------------     ----------------------------------------------------------- Tictac.cbl               Use this program to sample the Fonts and gain familiarity with the Shared                              &nbs

Problem: This project illustrates how to use Byte-stream File Routines to access and traverse an indexed file and summarize the records in the file by record code. Routines used: CBL_OPEN_FILE, CBL_CLOSE_FILE, CBL_READ_FILE, CBL_START_FILE Resolution: INTRODUCTION ========== This project illustrates how to use Byte-stream File Routines to access and traverse an indexed file and summarize the records in the file by record code. SOURCE FILES: ============= Program Files          Description --------------------     ----------------------------------------------------------- XCreateFIDX.cbl     This program creates an indexed file (FLIndex.dat/.idx) containing thirteen                                &n

Problem: OLE demo that calls Microsoft Word and does a find/replace Resolution: INTRODUCTION ========== This demo shows how to write an OLE Automation client to Word 97 in a series of simple stages. DESCRIPTION ========= This demo shows: o     How to start and stop Word 97 from COBOL o     How to load a document into Word 97, edit and print it. o     How to deal with exceptions and events generated by Word 97. There are five versions of the program provided, each showing how to do more with Word 97 from COBOL. SOURCE FILES ========= README.TXT WORD1.CBL WORD2.CBL WORD3.CBL WORD4.CBL WORD5.CBL WORDEVT.CBL WORD97.APP REQUIREMENTS ========== Microsoft Word 97 should be installed. OPERATION ======= The demo comes in the following stages: 1. WORD1.CBL - This first demo shows how to start and stop Word from COBOL. Word will not become visible, so you need to w

Problem: Using display statements to track a COBOL program's activity has been pretty routine for as long as there have been programmers using the COBOL programming language. This example illustrates how you can use display statements in a COBOL DLL program. Resolution: BUILD WITH RELEASE:     NetExpress 3.1 SP1, 4.0 all04n40.exe ============== Two Net Express project files, DLLDisplays.APP and DLLDisplays.OLD, are present in the project directory. The DLLDisplays.APP file is a Net Express 4.0 project file. The DLLDisplays.OLD file is a Net Express 3.1, SP1 project file. If you are working with Net Express 3.1 rename the 4.0 project file (DLLDisplays.V40) and change the file extension of the 3.1 project file from "OLD" to "APP". INTRODUCTION ========== Using display statements to track a COBOL programs activity has been pretty routine for as long as there have been programmers using the COBOL programming langu

Problem: CBL_GET_PROGRAM_INFO, Example #2: Trace back the Call/Perform Stack Resolution: INTRODUCTION ========== Simple demonstration of call by name routine cbl_get_program_info. SOURCE FILES: ========= Program Files     Description ----------------     ----------------------------------------------------------- Main.cbl              the trigger program  that starts by call SubOne program. Subone.cbl         Calls Subtwo program. Subtwo.cbl         Calls Subthree program. Subthree.cbl       Calls Subfour program. SubFour.cbl        Calls Subfive program. Subfive.cbl          Makes the call to cbl_Get_program_i

Problem: COBOL program calling Btrieve 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. A file is created, opened, and

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: 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: This is an amended version of the Excel demo from Net Express. It shows how you insert page breaks into an Excel spreadsheet from a COBOL program using OLE Automation. Resolution: ========================================================== Keywords: demonstration, sample, example, demo, excelpage.zip demo.ex demo.me demo.ne Attachments: excelpage.zip Old KB# 4005

Created On:  05 January 2012 Problem: We crashed when using fsmgr and received the return code 10053.  Why is this? 4:35:29 24.05.2006 CCITCP (tcpnet.c $Revision: 4.130 $:0066) 20000 E send(), called in mFt_net_Send_Header, failed with return code 10053. 04:35:29 24.05.2006 CCITCP (tcpnet.c $Revision: 4.130 $:0066) 20000 E send(), called in mFt_net_Send_Header, failed with return code 10053. 04:36:41 24.05.2006 CCITCP (tcpnet.c $Revision: 4.130 $:0066) 20000 E send(), called in mFt_net_Send_Header, failed with return code 10053. Resolution: The error 10053 almost always occurs because the remote end fails to respond with an acknowledgement of a data packet that has been sent to it. This error is not generated until retries have been attempted and the lack response to all of them has timed out. In the really old days of DOS TCP/IP stacks and Windows 16-bit applications the stacks could sometimes get confused and issue this error timed from the initia

Problem: JCL with FBA report file 139 length error on the file open.   Resolution: After  DIALECT(OS390) add  NOADV and AMODE(31). Old KB# 4022

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 demo environment is used to demonstrate how to create/incorporate custom tools in the Net Express IDE. Resolution: INTRODUCTION ========== This demo environment is used to demonstrate how to create/incorporate custom tools in the Net Express IDE.  In this case the Tool is used to add a line number to a program and also to add a comment in column 73-80. SOURCE FILES: ========= Program Files         Description -------------------     ----------------------------------------------------------- reseqnID.cbl          Source of Tool to be used within the IDE CobolPgm.cbl         COBOL Skeleton Program Resource Files: -------------------     ----------------------------------------------------------- buildtool.bat     &nb