Rocket® COBOL

Problem: Converting a data file from EBCDIC to ASCII that contains packed numeric fields (usage COMP-3) using DFCONV from the command line, or alternatively the File Convert data tool from the Net Express IDE, results on corrupted data in the numeric fields. Resolution: The problem may be that the packet fields are not EBCDIC character data, they are just numeric data that follows a particular format (packet decimal) but it always follows the same format whatever the OS. I will give you an example. If you have the following hexadecimal data from the mainframe: 94 2C What would you say it is? It could be the value 924 in packet decimal format, but it could also be the EBCDIC string "k<". If you tell the File Convert tool that your file is all in EBCDIC, it will take it as the string "k<" and generate its ASCII equivalent, in hexadecimal: 63 BC This is perfectly valid if it really was the string "k<", but if that

Problem: When creating an XML file from a COBOL program, how would you prevent groups/items being output to the XML file?  This may be necessary when the items or groups hold no data at all. Resolution: Define the groups/items in the COBOL program with the COUNT IN clause, e.g. 03 Main IDENTIFIED BY "Main".      05 A PIC X(6) IDENTIFIED BY "A_TAG" COUNT IN A-CNT.      05 B PIC X(6) IDENTIFIED BY "B_TAG" COUNT IN B-CNT.           07 B-ATTR PIC X(6) IDENTIFIED BY "B1_A" IS ATTRIBUTE.           07 B-SUB PIC X(6) IDENTIFIED BY "B_SUB_TAG" COUNT IN B-SUB-CNT.           ... Moving 0 (zero) to the count variables wil stop the associated elements or groups being output to the XML file. Old KB# 58

Problem: Is there a pause, sleep, or wait command in RM/Cobol? Resolution: C$Delay is used to relinquish the CPU for a length of time specified in seconds. Calling C$Delay will allow other programs to run while the original program waits. The amount of delay is not exact. It depends upon the particular machine configuration and the load on the machine. Calling Sequence: CALL "C$Delay" USING seconds "seconds" is a PICTURE 9(n) BINARY, where n can be a digit from 1 to 9. It specifies the length of time, in seconds, to delay. Delays longer than one day are not normally meaningful and should not be used.      Old KB# 6122

Problem: Release 4.0: Receving a return code 14605 for a file operation using a call_by_name CBL_  routine Resolution: 14605 is a decimal number representing the related run time error in two bytes basically in hex format: '390d', the most right byte hex '0d' describes a value of '013' decimal. You can find more information about run time error '013', and all other cases, here: Net Express Help -> Index -> Run-time system -> error messages -> Run-time System Error Messages ->refer to 013 -> File not found If you want to act programmatically take a look here: http://www.microfocus.com/Resources/Newsletters/SupportLine/20051101-index.asp#TechnicalArticles >Interpreting the Return Code of a Library Routine< Old KB# 5796

Problem: trying to use comp-6 directive and getting invalid command line error Resolution: An additional integer  of "1" or "2" is required comp-6"1"   or comp-6"2" Old KB# 5771

Problem: installing netx 3.1 on windows2000 - getting error not enough space on target directory when indeed there is more than enough space available Resolution: in this particular case - the fix was to do a regedit and delete the micro focus folder under hkey_local_machine **if there are no other micro focus products on machine if there are - only delete the net express folder Old KB# 5777

Problem: Is it possible to use Telnet in a COBOL system on the .Net platform. Resolution: Neither COBOL or the .Net Framework (V1 or V2.0) has support for the Telnet protocol. There is however many 3rd party .Net libraries that provide support for Telnet on the .Net platform. Old KB# 5776

Problem: A COBOL program that is built with Oracle Procobol precompiler fails with an RTS114 Error on a SQL SELECT statement. Resolution: This error was caused by a mismatch of Oracle versions. Using the correct version of Oracle client software for the Oracle Server version resolved the problem. Old KB# 5747

Problem: Problem: The install of Net Express 4.0 on a Window XP professional  failed because the Setup reported erroneously an installed Application Server for NE 4.0. Resolution: Workaround: 1. Using regedit, rename the key   HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall to Uninstall-temp 2. Start the NX setup. 3. At the setup welcome screen, rename the key back to Uninstall. Old KB# 5769

Problem: Receving a not found error when doing a invoke such as:-                invoke wordserver "GetSpellingSuggestions"                        using       ws-work                        returning   ws-suggestion Resolution: The problem here is in the method name "GetSpellingSuggestions". This has "get" as the first 3 characters so the COBOL OLE runtime thinks you want to get a property "SpellingSuggestions" rather than do a method call. You can fix this by making a "setdispatchtype" call to tell the runtime that the next call is actually a method c

Problem: Problem with websphere deploying application gets error Resolution: Added MFCobol.jar in the PATH.  Now Websphere will report successful application deployment. Old KB# 5732

Problem: The cookie.js file was correctly deployed to the web server but the cookie used on the page was being passed between the browser and server. Resolution: This issue was caused by the Virus checker that was installed on the webserver machine. The virus checker was preventing the javascript from functioning correctly. Old KB# 5766

Problem: Release 4.0: Creating and maintaining toolbars in Net Express, Dialog system is preferred. Where to find examples and tips? Resolution: (1)  A demo can be found in the Net Express product installation itself: ..\\DialogSystem\\Demo\\Commoncontrols\\Toolbar (2)  Additional, there is a programming tutorial "Adding and Customizing a Menu Bar and Toolbar". It can be found here: Net Express -> Help -> Help Topics -> Content -> Programming -> Dialog System -> Dialog System Guide -> Part 3 Programming Tutorials -> Chapter 21 Old KB# 5779

Problem: Is there any set of specific directives recommend whent converting from mainframe COBOL370 programs to Microfocus COBOL Net Express? Resolution: The list of directives should match the mainframe compiler version currently being used. Micro Focus creates a standard for that Dialect, but that does not mean it will match the specific environment completely. Look at Net Express Help > Start Here, Migration Cookbook, Chapter 6 Directives and Dialects for the directives associated with each Dialect. Obtain the list of directives that are used when compiling on the mainframe and match them to one of the dialects and then add/remove additional directives as needed. There is no list other than using the DIALECT(XXX) directive where XXX indicates a specific dialect. There are simply too many combinations of language elements that would enable a simple list of directives to work in all cases. This being understood the only generic list would be that provid

Problem: How can access the Vtable from a COM DLL? The VTable is the low level interface  that a COM Object Object exposes. Its structure is similiar to a C Object. Resolution: If you already have a COBOL OLE Domain object you could use the COM Class library IUnknown "fromDomainObject" class method and QueryInterface to get the COM Interface (vtable) you want. Alternatively you could CoCreateInstance and QueryInterface COM API calls. If possible its far better to use a automation object so you can invoke on it. Thats far more forgiving and simpler from COBOL. Old KB# 5727

Problem:   Is Visual Studio 2005 supported in Net Express 4.0? Resolution: Currently the Net Express 4.0 product works with Visual Studio 2003. The Net Express  5.0 version works with VS 2005. Old KB# 5768

Problem: Ther screenset uses the Datepicker component and the screenset needs to be informed back of any update which occured in the component comment below used with the demo delivered in Netx: [Net Express]\\DialogSystem\\DEMO\\COMMONCONTROLS\\DATETIME Resolution: 1) set a CALLBACK on the p2ce-losefocus event           MOVE '"' & ProgramID & z'p2ce-losefocus"' TO MessageName           INVOKE EntryCallBack "new" USING MessageName                                  RETURNING aCallback           MOVE p2ce-losefocus TO i           INVOKE aDatePicker "Set

Problem: Net Express 4.0: SWITCH-0, SWITCH-1, SWITCH-2,..,SWITCH-8  are coded in the SPECIAL-NAMES paragraph of the CONFIGURATION SECTION of a COBOL program. The program tests to see which switches are ON and behaves accordingly. The program is built as an .int or .gnt. How would you set there statuses from the Net Express command prompt, so that they are passed as parameters when the program is 'run'? Resolution: The status of the switches are set and passed to the program, at the time of program execution from the command prompt, with the following command: run ( 0 1 2) Program This sets the programmable switches SWITCH-0, SWITCH-1 and SWITCH-2 to ON and passes these settings to the program "Program", built as an .int or .gnt. Old KB# 5737

Problem: How do you apply XP Theming to a Dialog based application? Resolution: The XP Appearance is controlled by the Operating System and needs to be enabled for an application. The simplest way to do this is to have a manifest file in the same directory as the application. This is a file that matches the exe name with a .manifest extension. The customer.zip attached is an example of this method. You need to look in the release directory for the file. The other approach is to build the Manifest into a resource in the EXE. The other attachment is an example of this approach. Edit the RC as text to see what is required. These apps can also be run on pre-xp systems. The manifest ensure that that XP Theming controls library is loaded and used by the operating syste. We would recommend that the customers test their apps with theming applied so ensure that visually they look ok. Attachments: customer.zip Old KB# 5740

Problem: What is the return code of the projmake utility when a project fails to build or open? Resolution: The prokmake utility sets return-code = 1 for any error found.   You cannot specify a return-code for each type of error. Old KB# 5760

Problem: Cobol calling JAVA first call Resolution: Add the JAVA\\BIN\\classic or client directory that contains jvm.dll to the PATH environment Old KB# 5788

Problem: This error: "The program ... has been modified since the last compile. This may lead to unpredictable results when browsing and animating." is produced after a compile of the program. Resolution: the "$" should be in card column 7.      1          $set sql(dbman=odbc)      2        ****************************** Like this:      1        $set sql(dbman=odbc)      2        ****************************** Old KB# 5772

Problem: Is Dialog System dsbrowse included in Application Server runtime environment Resolution: DSBROWSE.gnt in included in our application server (version 4.0). The location of the Application Server directory may need to be on the COBDIR directory. The gnt format modules are located via the COBDIR environment variable. Alternatively you could link dsbrowse.obj into the main application exe. Old KB# 5744

Problem: When we try to run our application on the Net Express development machine we get the following error: ASLM: Semaphore failure. ASLM: Errno 1000 Why is this? Resolution: This indicates that the Net Express runtime license cannot be found.  On the development machine please ensure that your application is linked with the dynamic option and/or that PATH/COBDIR are set to point to the location of Net Express. Old KB# 5720

Problem: Net Express 4.0 How can you stop the run-time from checking if numeric data items have valid numeric data and stop the warning message "numeric field contains invalid data" Resolution: By default this checking is always ON, but you can override this by turning off the 'F run-time switch': - At the Net Express command prompt - set cobsw=-F; or - In the IDE, from the menu - 'Project' > 'Properties...'. Click on the 'Application...' in the Project Properties dialog and go to the 'Program Execution' tab. Under 'Error Handling', uncheck the checkbox for 'Validate numeric fields'. Old KB# 5739