Browse all forums dedicated to the Rocket® COBOL product family.
Recently active
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
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 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
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: 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: When I read a record WITH LOCK, I would like to be able to re-write the same record without releasing the lock. My understanding is that the re-write releases the lock, so I execute another read with lock immediately after the rewrite. Is this possible, and if so, what is the proper syntax? Resolution: If you use single record locking in your program, a rewrite of a record that has just been read with lock will then be unlocked. Therefore, you should use multiple record locking if you want a rewrite following a read to keep the record locked. You can then use the UNLOCK statement to release the lock. You will have to do a READ WITH KEPT lock in this scenario. If you rewrite a record that was read without a lock, you would have to compile with the WRITELOCK compiler directive in order for the REWRITE to keep a lock on the record. The attached project has a cobol.txt file with that directive so that you can test WRITELOCK b
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: The example program, "CONVERTING.cbl", illustrates how to use an "inspect ... converting" statement to translate EBCDIC numeric display values to equivalent ASCII numeric display values. Resolution: ============= Two Net Express project files, CONVERTING.APP and CONVERTING.OLD, are present in the project directory. The CONVERTING.APP file is a Net Express 4.0 project file. The CONVERTING.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 (CONVERTING.V40) and change the file extension of the 3.1 project file from "OLD" to "APP". INTRODUCTION ========== The example program, "CONVERTING.cbl", illustrates how to use an "inspect ... converting" statement to translate EBCDIC numeric display values to equivalent ASCII numeric display values. The example program is an ASCII program. A character data item in working-storage has an EB
Problem: How to compile from a command line, using the NoQuery Compiler directive to suppress the prompt for any missing copy files. Resolution: INTRODUCTION ============ When compiling from a command line, use the NoQuery Compiler directive to suppress the prompt for any missing copy files. An 8-S error will be reported: * 8-S******************** ** Unknown COPY file MYBOOK.CPY specified * Checking complete - errors found but the compile will continue to completion. SOURCE FILES: ========= Program Files Description ---------------- ----------------------------------------------------------- CblMain.cbl Example program using a copy statement to retrieve a COBOL copy book. Batch File: ---------------- &nbs
Problem: Release 4.0: How to get rid off the message after every compilation of any program: The Micro Focus COBOL RTS has detected an RTS error number 173, and has coredumped the process into E:\\NETEXPRESS\\DUMP\\cblcore Resolution: Go to Options -> Animate -> and under Error Handling: Error handling when running programs outside of the IDE change the Core Dump in the drop down menu to Default. Old KB# 4041
Created On: 19 June 2006 Problem: CBL_GET_PROGRAM_INFO, Example #1: The Main program calls the DLL by name and then uses the call-by-name routine to recover the entry point names in the DLL. The results are displayed on the screen. Resolution: INTRODUCTION ========== The Main program calls the DLL by name and then uses the call-by-name routine to recover the entry point names in the D. The results are displayed to the screen. SOURCE FILES: ========= Program Files Description ---------------- ----------------------------------------------------------- main.cbl Main COBOL program. c2cbldll.cbl COBOL supprogram with many entry points. Copy Files ---------------- ----------------------------------------------------------- gtpgminf.cpy OPERATION: ======= Rebuild program. All of the necessary directives are located at the top of the program. Start animating the MAIN and then say run. The Animator application window will display the entry points contained in c2cbldll. In
Problem: Example of the COBOL sort using two ways: a sort with Using and Giving and a sort with an Input Procedure and an Output Procedure Resolution: INTRODUCTION ========== This program shows an example of SORTing a file using two methodolgies, a SORT with USING & GIVING and a SORT with an INPUT PROCEDURE & OUTPUT PROCEDURE. SORT examples making use of combinations of these methodologies (i.e.SORT with INPUT PROCEDURE & GIVING) are not shown, but can be easily created using the examples given in this program.*
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: 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: 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: 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: This example shows how to use X'91" function 69 to Scan a directory (Note that these routines have been superceded by a set of CBL_ routines.) Resolution: INTRODUCTION ========== Example of using X'91" function 69 to Scan a directory. SOURCE FILES: ========= Program Files Description ---------------- ----------------------------------------------------------- Dirlist.app Application File Dirlist.cbl Source File Copy Files: ---------------- ----------------------------------------------------------- Shifty.cpy Copy File OPERATION: ======== Open the application file. Rebuild and animate the project. The A
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
Problem: This program displays a list of Run-time error numbers and ERRORLEVEL values. The displays are re-directed to a text file by the OutDD Compiler directive. Resolution: INTRODUCTION ========== SOURCE FILES: ========= Program Files Description -------------------- ----------------------------------------------------------- ErrLevel.cbl This program displays a list of Run-time error numbers and ERRORLEVEL values. The displays are re-directed to a text file by the OutDD &n
Problem: Shows the use of CBL_ALLOC_MEM, CBL_GET_SHMEM_PTR, CBL_PUT_SHMEM_PTR, CBL_EXEC_RUN_UNIT and CBL_FREE_MEM Resolution: INTRODUCTION ========== The Multiple Run Unit (Mru) demo illustrates how you can start multiple, concurrent run units, each with a separate, window display. SOURCE FILES: ========= Program Files Description ---------------- ----------------------------------------------------------- Ru0.cbl Main program that starts and stops the other run units. Ru1.cbl (Subordinate run units that function (once Ru2.cbl -(started) independent of one another and Ru3.cbl &
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: 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: 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: 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
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.