Rocket® COBOL

Problem: This example program demonstrates the use of the Net Express call-by-name library routine PC_PRINTER_WRITE. It will read the line sequential file PRNTRECS.DAT and output the records one at a time to the default system printer. This program also demonstrates the use of variable length line sequential files defined with the RECORD IS VARYING IN SIZE clause. Resolution: INTRODUCTION =========== This example program demonstrates the use of the Net Express call-by-name library routine PC_PRINTER_WRITE. It will read the line sequential file PRNTRECS.DAT and output the records one at a time to the default system printer. This program also demonstrates the use of variable length line sequential files defined with the RECORD IS VARYING IN SIZE clause. SOURCE FILES: ========== Program Files           Description --------------------     -----------------------------------

Problem: This program demonstrates how to allow a user to select a font and style for printing using the Windows SDK function ChooseFont in conjunction with the Net Express PC_PRINTER routines. Resolution: INTRODUCTION ========== This program will demonstrate how to allow a user to select a font and style for printing using the Windows SDK function ChooseFont in conjunction with the Net Express PC_PRINTER routines. This function allows you to present a list of available fonts to the user for selection. This can also be done by setting the appropriate printer-flag when using the PC_PRINTER_OPEN call but the ChooseFont function is more powerful. It allows you to present a list of fonts based on certain criteria such as only Truetype, only fixed fonts etc. The criteria flags can be found in the CFDEFINE.CPY copy file. This example will use the selected font to output various text lines to the printer. The lines will be printed in differing point sizes and

Problem: If a calling program calls a program without passing all parameters defined in Linkage section (of called program), then the runtime system may fail with runtime error 114. This will happen when the called program references any LINKAGE SECTION field that has not received a parameter. For example, the following is code in the calling program:                                    CALL "SUBPROG" USING WS-AREA                                                               &nbsp

Problem: You might want to hide or make invisible a control (e.g. input field) in a HTML form based on some values or events. Resolution: The best way to do this is to use JavaScript, a programming language that is common on Web pages. You can have JavaScript to determine when to hide a field. Although you can do many things with JavaScript, it would require you to know about HTML codes as well. The following JavaScript makes input2 invisible when the onclick_func function is executed and the value of input1 is "fano": function onclick_func() { if (document.form1.input1.value == "fano") document.form1.input2.style.display = 'none' } There are so many references of JavaScript on the Internet, and you will be able to find ways to enhance interaction with your web pages. Old KB# 4053

Problem: How to find out the software version of the UNIX product? Resolution: To locate the software version of the cobol unix products installed cat $COBDIR/etc/cobver This will show the software version (see below example: v4.0 SP1) and build version (see below example: 40.03) of the product, as well as any latest fixpack installed (see below example: PTI=Fixpack40.03_10) and if the Enterprise Server Development component is installed (see below example: PTI=ES).   For example: cobol v4.0.00-e PRN=RXCTZ/AAA:9h.N3.40.03 PTI=SP1 PTI=ES PTI=Fixpack40.03_10 If you have more than one version of any of the Micro Focus Unix products, then you'll need to know the exact location of where these products are installed to determine the version of these products. Old KB# 4087

Problem: This program demonstrates how to use the Windows 32-bit API function EnumPrinters to obtain a list of available printers and their associated parameters. This demo works on Windows 95, 98 NT, 2000 and XP Resolution: INTRODUCTION ========== This program demonstrates how to use the Windows 32-bit API function EnumPrinters to obtain a list of available printers and their associated parameters. SOURCE FILES: ============= Program Files                  Description -------------------------     ----------------------------------------------------------- ENUMPRNT.CBL              Main program for this demo EnumprintLocal.CBL        Program that calls the WINAPI function EnumPrinters to list      &nbs

Problem: Does EnterpriseLink support Sun Solaris 10.0? Resolution: Yes.  Solaris 10 is supported. Old KB# 4132#Rumba#EnterpriseLink

Problem: This is an extraction from an EL5.05 log file: 2005/05/16 09:19:06 [0x04cc] Process Session(3579): Session Qj0ZUdbFAzpuCpAF processing request http://localhost:80/stscripts/run.stn/onlineIMSA/ 2005/05/16 09:19:06 [0x04cc] SSSession::reload(6996): Reload current URL 2005/05/16 09:19:14 [0x04cc] Process Session(3579): Session w8I21E67VKFieeiq processing request http://localhost:80/stscripts/run.stn/onlineIMSA/ 2005/05/16 09:19:14 [0x04cc] SSSession::reload(6996): Reload current URL What does the message ""SSSession::reload(6996): Reload current URL" mean? Resolution: The "SSSession::reload(6996): Reload current URL" message is indicating that the URL has been reloaded by clicking on the refresh button or pressing F5, etc. Old KB# 4131#Rumba#EnterpriseLink

Problem: While loading screen using either EL Loader or loader lite ther is noway to specify which protocol to use TN3270 or TN3270E  but there is a option after the project is created. Resolution: At the start of loader in the information page under the category "Display Attributes" there is a checkbox  "Extended mode".    TN3270E is extended mode.    And is this also true for LoaderLite, the "Extended Attributes" check box turns on TN3270E? Old KB# 4134#Rumba#EnterpriseLink

Problem: How to find out which version of Enterprise Link is installed? Resolution: To check which version of ELink you have installed, go to the Web Authors site and look towards the bottom of the screen.  You should see something like: Micro Focus EnterpriseLink 5.0.6 Build Number 6481 on 04/06/06 19:23:36 for Microsoft Windows Old KB# 4133#EnterpriseLink#Rumba

Problem: Is there a compiler directive that will display information regarding data-items? Resolution: The DATAMAP directive causes the Compiler to output information on the data items; both those that you have specified, and those automatically generated by the Compiler, such as the data area for the RETURN-CODE special register. The information is output at the end of the list file. The information on the data items is output in the same order as they are encountered in your program by the Compiler. The first line is the program-id of the program to which the data items belong. This enables you to see the relevant data items for nested programs, or for the various areas of OO class programs (classes, object methods, and so on). For each data item, the following information is listed: The line number The data name The address of the data item, that is the offset from the beginning of the program's data area The size of the data item in bytes The

Problem: Release 4.0 With SP2 for Server Express the treatment of VALUE clauses in the FILE SECTION has changed. Before it was used during program start up to initialize the data items with the desired values (line in WORKING-STORAGE), now it is ignored. Because this behaviour is documented, it cannot considered to be a bug. Questions: Is it possible to get the old behaviour back (maybe by a compiler option)? Or what else solution can you provide to make our old programs run as before? Example: 000100 IDENTIFICATION DIVISION. 000200 PROGRAM-ID.    A. 000300 ENVIRONMENT DIVISION. 000400 INPUT-OUTPUT SECTION. 000500 FILE-CONTROL. 000600     SELECT FQS001 ASSIGN TO XX 000700            ORGANIZATION IS LINE SEQUENTIAL. 000800 DATA DIVISION. 000900 FILE SECTION. 001000 FD  FQS001. 001100 01  RQS001    PIC X(80)&nb

Problem: CBL_YIELD_RUN_UNIT was present in Object COBOL Developer Suite, but did not appear to work. Has the situation changed in Server Express? Resolution: CBL_YIELD_RUN_UNIT is now functional in Server Express. It yields the remainder of a run-unit's time-slice to unspecified run-units. On some environments this can result in a one-second pause. Old KB# 4078

Problem: This particular may be encountered when running programs after having migrated from OCDS 4.1.30 to OCDS 4.1.40 or 4.2 or to any version of Server Express. Resolution: The error "libfhutil.so.2.0: open failed" is normally due to the fact that this library file, used in the old file handling utility (fhutils) was dropped in OCDS 4.1.40 and support for it was removed in all successive versions of the product and all versions of Server Express.  It was replaced by the Rebuild utility which carries out the same functions (and more) with better performances and the ability to handle larger files.  Having being replace with the Rebuild utility, it will therefore be necessary to recompile / relink all the object and executable files. Further information pertaining to the old file handling utility and the necessary steps to migrate to the new Rebuild utility can be found In the online manuals "Programmer's Guide to File Handling" and "Migrati

Problem: The example program illustrates how to use the CBL_LOCATE_FILE call-by-name routine. Resolution: ============== INTRODUCTION ========== The example program illustrates how to use the CBL_LOCATE_FILE call-by-name routine. SOURCE FILES: ============= Program Files     Description ----------------     ----------------------------------------------------------- CblMain.cbl        Example program that uses CBL_LOCATE_FILE to locate Mfnetx.exe REQUIREMENTS: ========== This example was created and Animated using NetExpress 3.1, Service Pack 1. OPERATION: ======= Check and Animate the example. Examine the variables returned by the call to the routine. NOTES: ==== "status-code" provides an overall indication of the success or failure of the routine. "exist-flag" indicates whether the file was or was not found. "path-f

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

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: How do you create a MFDEBUG log file? Resolution: The MFDEBUG.LOG is really designed for MF use rather than Customers. It is a dump which shows the state of the machine when a COBOL program crashes. Development can decode this and sometimes use it to help pinpoint problems in the runtime. The log file is created automatically and is copied to the working directory. Old KB# 4020

Problem: This demo demonstrates how you can create a zip file or add to an existing zip file from a COBOL program. Resolution: INTRODUCTION ========== This demo demonstrate how you can create a zip file or add to an existing zip file from a Cobol program. SOURCE FILES: ========= Program Files     Description ----------------     ----------------------------------------------------------- zip.cbl Copy Files ----------------     ----------------------------------------------------------- minwin.cpy wintypes.cpy winbase.cpy REQUIREMENTS: ========== This demo uses the Big Speed Zip DLL shareware from BigSpeedSoft. OPERATION: ======== Simply rebuild the application and run or animate NOTE: ==== This demo was originally developped by one of our customers, Mr. Gary Holness. Thanks Gary. ========================================================== Keywords: demo

Problem: Release 4.0: This error appeared when trying to compile any program within Net Express, including the demos provided with Net Express. Resolution: The problem appeared a corruption. A simple deinstall and reinstall didn't work here. Nor cleaning the registry entries. Somehow something on the system completely corrupted the programs within Net Express. The only solution to this problem was to get the backup of the  previous week and the corruption disappeared. Old KB# 4040#RMCOBOL#COBOL#ServerExpress#netexpress#AcuCobol

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: You may have problem applying Net Express 4.0 wrappack with all07n40.exe hanging during the installation of the IDE fixpack. If you are running source control software (eg 'Perforce' ), this could be causing the wrappack to hang. Resolution: It looks like it is the Source Code Control software on the machine could cause the problem. Go into the registry and look at HKEY_LOCAL_MACHINE\\SOFTWARE\\SourceCodeControlProvider and rename the key ProviderRegKey to something like ProviderRegKeyxxx, then it won't find it and try to make it available. If the NX 4.0 IDE FixPack then goes in ok you should be able to run Net Express. What Source Code Control software do you have installed? Also, you could try uninstalling and reinstalling the SCC software and see if it works. If it doesn't then renaming the key will at least mean they can coexist even if they can't communicate. Renaming the key in the registry should resolv

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