Rocket® COBOL

Problem: This program demonstrates the use of the Net Express library routine PC_PRINTER_INFO to get the current configuration information for a specified open printer. It will return a native device context handle, and other information that can be used to enhance the printing of a document by calling native WINAPI graphics functions directly. Resolution: INTRODUCTION ========== This program demonstrates the use of the Net Express library routine PC_PRINTER_INFO to get the current configuration information for a specified open printer. It will return a native device context handle, and other information that can be used to enhance the printing of a document by calling native WINAPI graphics functions directly. SOURCE FILES: ========= Program Files         Description -------------------     ----------------------------------------------------------- PRNTINFO.CBL    

Problem: If you receive the following error when trying to run an executable on a machine running Application Server for Net Express 4.0: Dynamically Bound RTS Runtime DLL 'CBLRTSS', version 4.0, entry point CBL_CTF_TRACER_GET not recorded in registry, not found or incompatible with requirements of dynamically bound COBOL program. Dynamic binding of RTS requires: Any Runtime DLL, at least Version 4.0 Resolution: One likely cause of this error is the version of Application Server you are running. This Knowledge Base article was raised from an Incident where the Websync WrapPack all07n40.exe had been applied to Net Express 4.0 on the development machine. The executable was rebuilt on that machine and ported to the machine running Application Server for Net Express. However, the equivalent Application Server Service Pack, aps09a40.exe, had not been applied to the Application Server environment. Also, we noted during testing that in one instanc

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: Trying to anim Pro*COBOL programs  results in a blank screen.  Animating pure COBOL program works fine. CTF and truss traces show a 115 error in dispatch.gnt and then the process appears to hang. Resolution: The problem can be resolved by applying an IBM patch to AIX for APAR IY80008. Apparently the issue shows up when the bos.rte.libpthread package is version 5.3.0.30. If you use 5.3.0.0 debugging works correctly. The issue does not show up on our AIX 5.1 or AIX 5.2 machines, which use an older still version of libpthread. You can find a little more information on the problem via this link: http://www-1.ibm.com/support/docview.wss?uid=isg1IY80008 There's another link at the top of this page to go to a download page to get the fix. Old KB# 4116

Problem: How to set a Conditional Breakpoint in Animator. Resolution: You can set a Conditional Breakpoint in Animator.  This is not the same as a hard breakpoint.  A hard breakpoint occurs when Animator executes a specific statement.  A Conditional Breakpoint is a test of a data-item.  When that test becomes true, execution stops.   Below are some valid examples of breakpoints that may be used by animating our demonstration program pi.cbl. PI > 3.14      N < 25    STRING  =  "entrypoint"   loop-counter > <value> When the breakpoint is set, the COBOL line will be highlighted. Remember, you do not specify the word "if" when setting the breakpoint. Old KB# 4070

Problem: You may find that even though you didn't set the configuration option    LOG=ON in your extfh.cfg (or the file specified in your EXTFH environment variable, see knoledge base article 22486) Resolution: The file handler configuration option LOG specifies whether any unusual file-related situations, such as corrupted files, or automatic file recovery, are noted in a log file for later examination. The configuration option LOGFILE specifies the name for the log file, by default the name is XFHLOG. In the latest versions of the product LOG=ON by default. But the documentation hadn't been updated accordingly (Server Express 4.0 rpi 1058489) but this should be fixed in Server Express 5.0. To display the file contents, you should use the cobfhprint tool which should create a file called XFHLOG.TXT containing information from the XFHLOG file.     cobfhprint XFHLOGfilename Currently there are two defects associated wit

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

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: 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: 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: 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: 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: 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: When my screen appears I can't enter ^, when I do I receive a message at the bottom of the screen The keystroke has no meaning here. Resolution: The following code in an ADIS program will disable the Shift-6 "^" key and that will replicate the behavior that the customer is seeing. 01 set-bit-pairs                           pic 9(2) comp-x value 1. 01 data-key-control.                                              03 data-key-setting                pic 9(2) comp-x  value 0.   &nbsp

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