Rocket® COBOL

Created On:  19 March 2010 Problem: Compiling This error occurs while Animating a COBOL program. This error occurs when the user has set the COBTERMINFO environment variable to point to a customized terminfo file. Resolution: When running under the control of the Animator any screen output is cached in memory. If you swap to the user screen (i.e. by pressing F2 or by executing an ACCEPT), the contents of the cached screen are displayed. The program has no terminal of its own because it's under the control of the animator. So, when the program writes to the terminal, it is actually passing terminal sequences to the animator to be decoded and cached. The Animator uses a generic terminal definition called 'mfdebug', which defines all the capabilities required This error only occurs if a customer is using a different terminfo directory, or has deleted some files from the Micro Focus provided one. When a process is being debugged by Animator, if the application then

Created On:  20 October 2009 Problem: In a migration project the WRITE statement behaves differently from the origin. Resolution: The WRITE statement changes its behavior dependent on the selected dialect. When using:      $set dialect"OSVS" or      $set dialect"ENTCOBOL"the statement            WRITE RECwill delete the REC in       FD  MYFILE LABEL RECORDS OMITTED.01 REC PIC X(80).accordingly to the OSVS COBOL resp. Enterprise COBOL on the mainframe. When using      *set dialect"MF"the statement            WRITE RECwill keep REC unchanged. If the dialect is unsupported, where the sources came from, either choose a better dialect to be closer to the origin or some code may need to be added to the WRITE statement. Incident

Created On:  07 June 2010 Problem: The following error is encountered when attempting to install or upgrade Web-to-Host 6.0:“Error 2753.The File 'nmservicemanager.exe.2E19ED1F_0A9B_43F4_BA8B_60F8E67C8891' is not marked for installation.” Resolution: This problem is encountered when a previous installation of Web-to-Host software on the workstation cannot be uninstalled. Please perform the following steps in order to resolve the issue: • Download and install Microsoft Windows Installer Cleanup Utility on the workstation.• Close all open Web-to-Host sessions.• From the program list, launch Microsoft Windows Installer Cleanup Utility • Remove all detected versions of Web-to-host software and reboot the workstation.• Launch the session to fire off web-to-host install again Microsoft Windows installer utility download link: http://support.microsoft.com/kb/290301/en-us Incident #2456965 Old KB# 31182#Rumba#OnWeb#Web-to-Host

Created On:  8 June 2010 Problem: The Net Express documentation shows that the display method can be called on the Java Exception object in order to output the error text to the console.     entry "Jexception" using lnkException.           invoke lnkException "display" How does one modify this example so that the text can be accessed in a move statement to a COBOL pic x field? Resolution: The javasup class must be used to accomplish this task. Try the following as the main program:      $set ooctrl ( p-f)       program-id. ExceptionCatcher.        class-control.           SimpleClass is class "$JAVA$SimpleClass"           EntryCallback is class "entrycll"  &n

Created On:  7 June 2010 Problem: When calling a COM interface that was generated using the IMTK, (Interface Mapper Toolkit), from a .NET client program sometimes the error "MFCLBINP Error 402" is reported when the interface method is called.This occurs when the unmanaged COBOL program which will be called by the COM interface is a Dynamic Link Library (.DLL) and it is not linked to the multi-threaded runtime system. Resolution: This only occurs if a .DLL is being called. .int and .gnt programs do not exhibit this behavior.Please ensure that the .DLL to be called from the generated COM interface is linked to the multi-threaded run-time system.If this .DLL is created in a Net Express project then using the IDE, select Project->Build Settings->Link Settings and check the Multi-threaded option.If you are creating this .DLL using cbllink then use the option -rM. Incident #2452152 Old KB# 31154#COM#402#MFCLBINP#IMTK

Created On:  8 June 2010 Problem: This example shows how to create and populate an ADO.NET Dataset in a VB.NET program and then pass the dataset as an argument to a COBOL .NET class. Resolution: The attached example PassDSVB.zip contains two .NET projects and a solution file.The example was created using Visual Studio 2008 and Net Express 5.1.Running the example requires that an instance of SQL Server be running and that the Northwind sample database be present.Unzip the example to your hard drive C:\\ while retaining the folder structure in the .zip file.You will end up with two folders:C:\\PassDSVB and C:\\PassDSCOBStart Visual Studio 2008 and open the solution file C:\\PassDSVB\\PassDSVB.slnSelect Build Solution from the Build menu.Open up the source file PassDSVB.vb and view the code for the method Button1_Click.The connection to SQL Server uses the Server alias ".".Please change this if necessary to the instance name that you are using.Step into the code usin

Created On:  16 June 2010 Problem: The products named "Server Express" and "Server for COBOL" have an install script named "install".  Inside this script, there is a "tar" command to extract files.  On Solaris 10, the install script fails because the tar command cannot successfully un-tar the files.  It reports this error repeatedly: tar: ././@LongLink: typeflag 'L' not recognized, converting to regular fileAfter which the script might say: "Failed to untar due to lack of disk space."or "install error, check disk space/permissions and try again" Resolution: Edit and modify the "install" script, replacing the tar command with the alternative tar utility named "gtar".On Solaris, the "gtar" command is usually found at:   /usr/sfw/bin/gtarIf not, search for "gtar" elsewhere on your Solaris system, or contact Solaris support and ask

Created On:  8 June 2010 Problem: Question on use of C# string specifier @:In the C# code snippet below:            DirectoryInfo info = new DirectoryInfo(@"C:\\Documents and Settings");The @ specifier indicates a verbatim string in C#. Resolution: Here is the definition from the C# programming guide: Use verbatim strings for convenience and better readability when the string text contains backslash characters, for example in file paths. Because verbatim strings preserve new line characters as part of the string text, they can be used to initialize multiline strings. Use double quotation marks to embed a quotation mark inside a verbatim string. The following example shows some common uses for verbatim strings: C#  Copy Code          string filePath = @"C:\\Users\\scoleridge\\Documents\\";         //Output: C:\\User

Created On:  15 June 2010 Problem: I am using an ODBC enabled tool that requires an ODBC version x compliant driver.  What version of ODBC does Relativity support? Resolution: What version of ODBC does Relativity support?Relativity is ODBC 2.0 compliant.  However, it does implement some SQL grammar and scalar functions from later versions of the ODBC standard.The following SQL statements are supported by Relativity:CREATE INDEXCREATE TABLECREATE VIEWDELETEDROP TABLEDROP VIEWINSERTSELECTUPDATEThe following SQL clauses and predicates are also supported:AVGCOUNTMAXMINSUMBETWEENHAVINGEXISTSINUNIONUNION ALLGROUP BYORDER BYAdditionally the following ODBC scalar functions are supported:CONCATCONVERTCURDATECURTIMEDATABASEDAYOFMONTHDAYOFWEEKIFLCASELEFTLENGTHLOCATELTRIMMODMONTHNULLQUARTERRIGHTRTRIMSUBSTRINGUCASEUSERYEARFor more information regarding Relativity's supported SQL grammar, please see the Relativity Data Client help file.For detailed information about the arg

Created On:  8 June 2010 Problem: OpenOffice is a suite of application tools that provide a freeware alternative to using Microsoft Office.The Calc application is the alternative to Excel.OpenOffice has a COM interface but it is not compatible with the COM interface provided by Microsoft Office.A sample is needed to show how to access and manipulate a Calc spreadsheet using COM from a Net Express client so that the spreadsheet is saved as an Excel compatible format. Resolution: The following is a sample Net Express program which will create a Open Office Calc spreadsheet using the COM interface and then save the spreadsheet as an Excel compatible document:      $set sourceformat(variable)                                            &n

  Problem: My current index files are not file version 4. Should I upgrade these index files to file version 4?   Resolution: By upgrading to file version 4 you can take advantage of two very important enhancements. 1.  The ability to create large files (greater than 2GB)2.  Atomic I/O (eliminates most file corruption)Large File SupportThere are several steps to adding support for large files for existing index files: 1. The first step is to make sure that the operating system supports the creation of files greater than 2 GB. This may involve changing the file system, a kernel setting, or even the ulimit associated with a user account shell. Your systems support person will need to accomplish this as each operating system may handle it differently.2. Next, edit the default configuration file (runcobol.cfg) located in the RM/COBOL installation directory (usually /usr/rmcobol). Add the following two records to that file:RUN-FILES-ATTR LARGE-FILE-LOCK-LIMIT=

Created On:  16 July 2010 Problem: Using Syncsort software to sort Micro Focus COBOL modules, the Syncsort software is migrated to the Synsort DMExpress software. Unfortunately, it is not possible for Micro Focus modules to call DMExpress. Resolution: With the old Syncsort software when linking Syncsort to COBOL programs, the CALLSORT compiler directive is used with or without the value EXTSM ( cob –C CALLSORT or cob –C CALLSORT=EXTSM ) However, with DMExpress software , the CALLSORT compiler directive must be set to EXTSM1 ( cob –C CALLSORT=EXTSM1 ) and the executable must be generated with-IEXTSM1 ( upper-case “I” ) Incident #2453981 Old KB# 31186#SYNCSORT#Merge#Sort

Created On:  7 June 2010 Problem: When working with COBOL files that are defined as Heap Files using the Filetype"14" directive, a close on the file would sometimes result in a bad file status such as a 9/013 "File not Found" error being returned.There is a problem with the logic in the File Handler for the CLOSE statement handling of Heapfiles where the return-code was being checked prior to the actual close operation being performed. This means that if there was a bad status code from a previous operation in the File Handler then the error would actually be reported for the close because the status code area was not cleared out. So the close wasn't really failing, it was just been reported as bad because there was another operation that actually failed. Resolution: This problem has been fixed in Net Express 5.1 Wrappack 4 Hotfix 5 and above. Incident #2448545 Old KB# 31153

Created On:  16 June 2010 Problem: I need a display that is larger than the default 80 columns by 25 rows. Resolution: You can use the TERM-ATTR "COLUMNS" and "ROWS" configuration keywords to increase the number of columns and rows that the Runtime will display on the terminal.  These configuration records will need to be added to your RM/COBOL Runtime configuration file or placed in a new RM/COBOL configuration file.For example, the following record in your configuration file will yield a screen that is 100 columns wide with 30 rows: TERM-ATTR COLUMNS=100 ROWS=30For more information regarding terminal configuration, please see "Chapter 10: Configuration" in the RM/COBOL User's Guide.  You can obtain the RM/COBOL User's Guide from our web site at:  http://supportline.microfocus.com/Documentation/RMCobol.asp Incident #2457869 Old KB# 31190

Created On:  8 June 2010 Problem: An application defines multiple ISAM files some of which are in the default format of IDXFORMAT"3" and some of which are in the large format of IDXFORMAT"8". How does one specify multiple IDXFORMAT file types within a single application? Resolution: Multiple IDXFORMAT file types can be specified within a single application either in the file handler configuration file, EXTFH.CFG or within the application source code itself using the IDXFORMAT compiler directive.Example:Program source code is as follows:     id division.     program-id.   testfile.     file-control.         select default-isam1 assign to "DISAM1.DAT"                               &nbsp

Created On:  8 June 2010 Problem: While using Visual Studio to develop managed COBOL applications the Intellisense of Visual Studio stops working. Resolution: The items to check in the Visual Studio IDE are the options for the Text Editor under Tools->Options. Under heading COBOL->General, Auto list members and Parameter information should be checked and under Miscellaneous, AutoOutlining, Customize Editor for COBOL and Enable background...should all be True.You might try toggling these off and on so the IDE recognizes them. Incident #2287744 Old KB# 31159

Created On:  14 June 2010 Problem: I am unable to connect more than ten WOW Thin Client sessions to my Linux server. Resolution: This issue is caused by a change to the xinetd service daemon defaults on some Linux distributions.The "per_source" attribute specifies the maximum number of instances allowed to a single source IP address.  On some Linux variants this default is set to a value of 10. In order to address this issue you will need to modify your "rpcplus" xinetd configuration file ( /etc/xinetd.d/rpcplus ) and add the "per_source" attribute.  For example: service rpcplusper_source  = UNLIMITEDYou will need to restart the xinetd daemon after making these changes.  Please check your Linux distribution's manuals for information on how to restart xinetd. Incident #2447770 Old KB# 31178

Created On:  2010-04-27 Problem: How do you receive a variable length string in a COBOL program? Resolution: The receiving field must be defined as PIC X ANY LENGTH from the Linkage Section as shown below:  LINKAGE SECTION.  01 Field-Name PIC X ANY LENGTH.  There is a sample project attached to this Knowledge Base article. Incident #2358782 Attachments RecAnyLen.zip Old KB# 31084

Created On:  2010-04-27 Problem: How do you cause a COBOL DLL to be animated automatically when it is called without code change? Resolution: The usual method to cause a Cobol subprogram to be animated automatically when it is called is to insert a CALL “CBL_DEBUGBREAK”. The old way of setting the Cobol switch A still works in Net Express (i.e. COBSW= A) Incident #2355590 Old KB# 31085

Created On:  2010-04-27 Problem: We are receiving an Access Violation or a loop occurs when PCOMMAIN precompiles from a directory structure that contains a space in its name. Why is this? Resolution: This is a known issue with PCOMMAIN in Migration Software Development Kit for Net Express 5.0, and the workaround is to avoid any spaces in the name of the working directory. Incident #2425614 Old KB# 31082

Created On:  21 May 2010 Problem: How do you setup a CTF Trace while running a Net Express application? Resolution: To run the trace:1.  Create a file called ctf.cfg with the following entries: mftrace.level=debugmftrace.dest=BINFILE ## Emitter BINFILEmftrace.emitter.binfile#location=.\\ ## Component Run-time Systemmftrace.comp.mf.rts#all=true ## Component External File Handlermftrace.comp.mf.mffh.xfh#bsio=truemftrace.comp.mf.mffh.xfh#mem=truemftrace.comp.mf.mffh.xfh#base=truemftrace.comp.mf.xfh.mfh.xfh#file:*=true 2.  Set the environment variable MFTRACE_CONFIG: set MFTRACE_CONFIG=.\\ctf.cfg 3.  Run application. One or more files with the extension .ctb will be created. Incident #2454368 Old KB# 31075

Created On:  2010-04-27 Problem: A COBOL subprogram that used to run successfully with the old Micro Focus Workbench now fails with RTS 114 after it was recompiled with Net Express. The program is compiled with INITCALL"STE.DLL", which is a C DLL. Resolution: To resolve this problem is to load the DLL as follows:1. Define a PROCEDURE-POINTER field, for example, 01 MyDllPtr PROCEDURE-POINTER.2. Insert a SET ... TO ENTRY ... statement at the beginning of the PROCEDURE DIVISION, e.g. SET MyDllPtr TO ENTRY "STE.DLL" Incident #2419099 Old KB# 31083

Created On:  2010-04-30 Problem: When Using OpenESQL and explicitly qualifying the ODBC table causes SQLCODE=-206 at execution, is there an equivalent to the DB2(QUALIFIER=xxx) directive when using SQL(DBMAN=ODBC)?The following code snippet causing SQLCODE -206 during execution:$SET SQL(DBMAN=ODBC)EXEC SQL SELECT TABLE1.COL1 INTO :WS-COL1FROM DB2PROD.TABLE1END-EXEC Resolution: If all applications use the same schema, set the CURRENTSCHEMA CLI parameter in the DB2 ODBC Driver. If they do not use the same schema, you can add a EXEC SQL statement to set the CURRENT SCHEMA in the application itself.For example:EXEC SQL SET CURRENT SCHEMA = 'DB2PROD' END-EXEC. If compilation error occurs, set the CURRENT schema as a dynamic SQL statement move "SET CURRENT SCHEMA = 'DB2PROD' " to stmtbufEXEC SQLEXECUTE IMMEDIATE :stmtbufEND-EXEC Incident #2449126 Old KB# 31080

Created On:  2010-04-30 Problem: When compiling BMS maps using the command line tool mfbmscl in Net Express 6.0, we are getting message ‘DFHMDF LABEL TOO LONG’ . In Net Express 6.0 IDE, we have enable option “Allow long macro label names” on the Project Build Settings, BMS Advanced tab. What is the equivalent command line option is for the “mfbmscl” BMS compiler? Resolution: The equivalent command line option is called "High level assembler features" in Net Express 6.0. To solve the problem with long labels use the additional directive/HLL when compiling BMS using command line tool. Old KB# 31081

Created On:  2010-04-22 Problem: Customers may have file or library names that contain the “.” character in the name.  When attempting to download a library name that contains the “.” character the following SQL error is encountered: [Micro Focus] [RUMBA Data Access]  Syntax error or access violation. SQLSTATE   = 42961[ : The relational database is not the same as the current server.  SQLCODE=  -114.  :  Relational Database XXXX                 SSSSSSSS is not the same as server.    In the above example error XXXX would be the characters preceding the “.” character in the library name and the SSSSSSSS would be the system name. If attempting to download both a file name and library name that contain the “.” character the following SQL error is encountered: [Micro Focus] [RUMBA Data Access]  Syntax error or access violation. SQLSTATE&n