Browse all forums dedicated to the Rocket® COBOL product family.
Recently active
Problem: File routines, such as CBL_DELETE_FILE, CBL_RENAME_FILE, and CBL_COPY_FILE, in Net Express 4.0 fails to find filenames that are prefixed with a dash "-", e.g. -TEST.TXT These CBL_ routines fail with a non-zero return code, which can be interpreted as the routines were unable to find -TEST.TXT. Resolution: This problem has been fixed since All WebSync WrapPack v4.0.007 (all07n40.exe). Old KB# 3969
Problem: Net Express 4.0 Client found that when compiling a COBOL program in Vistual Studio they got the the following error(s): Failed to find the system program EXTSM Failed to find the system program EXTFH Resolution: Net Express was installed first. Then the latest wrappack for Net Express was installed. Then Net Express with .NET was installed from the installation CD. Applying the latest wrappack for Net Express with .NET fixed the problem. Old KB# 3924
Problem: Release 4.0: The problem is caused when a COBOL program encounters a problem and a STOP RUN is made then consequently the Java runtime is terminated. How can you prevent STOP RUN from doing this? Resolution: The use of SRV_CTL_NOSTOPRUN does prevent the JVM from terminating when using RuntimeSystem.cobcall. Old KB# 3929
Problem: Unmanaged Cobol class has a method returning "pic x" data. Unmanaged Cobol class is compiled to dll and registered (regsvr32) regarding to rules "to use rcw to call unmanaged Cobol". A VB.NET application invokes the Cobol class (added to vb.net application references as COM) and succesfully receives the returning "pic x" data. In Unmanaged Cobol, method's returning data type is changed to "pic x(4) comp-5" to return integer value to vb.net app. Cobol app is rebuilt, unregistered and registered again. Cobol COM is removed from vb.net app references and added again to expose returning value data type change to vb.net. But returning value data type change doesnot expose to vb.net app, vb.net app still recognises the data type as string not integer. What may cause such behavior? Resolution: This behaviour is caused by the way that COM describes its interfaces. When you change the ret
Problem: Release 4.0: Is there a problem using CBL_CHECK_FILE_EXIST also CBL_COPY_FILE in regard to pathnames including spaces, not getting back a return code consistently? Resolution: Basically, there is no problem using CBL_CHECK_FILE_EXIST, also CBL_COPY_FILE to get back return codes correctly. Please check attached demo file to get more information about. This demo program1.cbl shows how you can use a spacey pathname pointed to drive E:. (If you do not have an E: drive change it to a drive you want). Attachments: CBLSPACE.zip Old KB# 3917
Problem: How to change the settings for MS Word document's orientation, margins, and font Resolution: There are few demo projects in Net Express, which shows how to use Microsoft Word with Cobol applications, and they are located in C:\\Program Files\\Micro Focus\\Net Express 4.0\\Base\\DEMO\\COMDEMOS\\WORD. The programs may not show you how to change the settings you wish to change, but they show you how to change MS Word settings in general. You can have a look at MSWORD.CPY in the same folder to discover other numerous methods to change MS Word's settings or properties. We do not provide any documentation on how to use MS Word from Cobol. You need to know Object-Oriented Cobol and methods and functions available in MS Word. The attached demo (WORD3.CBL) is taken from the Word demo folder and modified to set orientation, margins, and font. Go to the Microsoft MSDN site (http://msdn.microsoft.com) to see the complete documentation on these MS Word fu
Problem: what is the max length of an 01 level? Resolution: Limits on the Size and Number of Data Items The following table shows the maximum size and number of data items. Data Item Maximum Size or Number ______________________________________________________________ Alphanumeric/Group 256 Mbytes Alphanumeric Edited/ & Numeric Edited Can consist of 32 parts, each of which can contain up to 16 occurrences of a single edited character type subject to a total size of 512 bytes Numeric 18 digits COMP/COMP-5 format 8 bytes EXTERNAL data item No specifiable limit ACCEPT FROM CONSOLE Limits (if any) are imposed by the operating system. ANSI DISPLAY No limit, on this COBOL system: Old KB# 3845
Problem: The Migration Development Toolkit is an addpack which eases migration from the mainframe to Enterprise Server in migration scenarios. It was designed to be used with Net Express 4.0 but not Studio 5.0. Resolution: When installing it on Studio 5.0 you will need to install the files attached to this KB. They are: PCOMMAIN.DLL, PCOMUTILS.DLL, YGREP32.DLL and several .DIR files. Attachments: Temp.zip Old KB# 3847
Problem: Method to eliminate 'This web service is using http://tempuri.org/ as its default namespace' message. Resolution: In .Net use a Class Attribute to specify the Namespace that the WebService is in. Example code (changes are highlighted with MFTECH in cols 1-6) to set this is:- $set sourceformat"variable" class-id. Service1 as "Service1" inherits CLASS-WEBSERVICE. environment division. configuration section. repository. interface INTERFACE-ICONTAINER as "System.ComponentModel.IContainer" &
Problem: A program uses the SPZERO compiler directive. The directive causes space characters in numeric data items to be treated as zeroes. While performing the STRING operation on a string and a numeric data item and displaying the result, outputs spaces rather than zeroes for the numeric data item. Resolution: The SPZERO directive treats spaces or undefined numeric data items as zeroes, 'internally'. This allows the data item to be used in IF statements, MOVEs and calculations. Perform a literal move to the data item to be able to STRING and DISPLAY the zeroes. MOVE zeroes TO ws-num. DISPLAY ws-num. Old KB# 3871
Problem: You can get a 173 Error Exception in .Net is you attempt to call a program that resides in a different namespace if that other assembly has not already been loaded. Resolution: You can fix this by adding the namespace to the call:- call "namespace1.program1" using ..... Old KB# 3887
Problem: CBL_COPY_FILE returns a status code of 14596 Resolution: The filename parameters that are passed to the CBL_COPY_FILE routine (and other CBL file related APIs) need to be space terminated. Ensure that you initialise the variables and make them longer than the filename you intend to use. Old KB# 3898
Problem: This oocurs when trying to do a call 'cbl_alloc_mem' The error returns - 173 module not found 'cbl_allo' The message on the 173 error displayed a truncated name such as cbl_allo Resolution: This error was encountered in a program that had a mixture of mainframe and pc coding and a mainframe dialect was being used. If this occurs use the NOMAPNAME directive and this will stop the truncation of called program Old KB# 3906
Problem: The following commad will give you information about what is the list of imports for a particular .exe or .dll. Resolution: At the command prompt: link /dump /imports prog.exe > report.txt notepad report.txt report.txt will show cblrtss.dll if prog.exe is pulling the Micro Focus single threaded runtime, or cblrtsm.dll if prog.exe is pulling the Micro Focus multithreaded runtime. report.txt should also show other dlls that are been pulled when prog.exe is loaded. The same command would work the same for prog.dll instead of prog.exe. Old KB# 3878
Problem: I've compiled my application with SQL(TRACELEVEL=n), yet I cannot find the resultant log file (OpenESQLTrace.XXX.log). Resolution: OpenESQL requires write permission to the current directory to create the OpenESQL trace file. If running from within the Net Express IDE, this will be the project directory. If the current directory is not writeable, OpenESQL will attempt to create the log file in the directory pointed to by the TEMP environment variable. See http://supportline.microfocus.com/mf_kb_display.asp?kbnumber=20008 for further details on OpenESQL tracing. Old KB# 3899
Problem: You will encounter a problem when installing Application Server if setup detects an existing installation of Application Server. Resolution: Run Regedit. Rename: HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall To: HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall-temp Note: Do not open the Uninstall key. Right mouse click the Uninstall key name and click the Rename button in the context menu. Type the new name and press Enter. Close Regedit. Rerun Install. At "Welcome" screen, run Regedit and rename Uninstall-temp to Uninstall. Close Regedit. Continue with installation. Old KB# 3885
Problem: You can use embedded printer escape sequences when printing using the syntax such as:- SELECT PRINTFIL ASSIGN TO PRINTER WS-PRINT-NAME ORGANIZATION LINE SEQUENTIAL FILE STATUS IS FILE-STATUS. WS-PRINT-NAME contains "\\\\PRINTSERVER\\printername". and standard COBOL File IO. Some printer ignore the control characters. Resolution: This is caused by the COBOL file handler inserting a NULL character before each control character. Some printers just ignore these extra null characters so they continue to work but some printers don't int
Problem: Currently the field value is erased, is there a way to keep the old value and allow an overwrite using adis and the accept statement with screen sections? Resolution: Use the WITH UPDATE option in the Accept statement- From the on-line docs for Format 5 of the Accept statement- If the UPDATE option is not specified, a data item for data entry is displayed initially as spaces, if you set the MS Compiler directive when you submit your source code to your COBOL system. (If the MS directive is not set, the display of initial data is a configuration option.) If the UPDATE option is specified, initial data of the data item for data entry is displayed. Old KB# 3874
Problem: A COBOL app in Net Express 4.0 outputs to a file. How do you write to the file using different Font sizes? Resolution: There is no way to select/change the font (size) of the text being output to the file. You are simply outputting text. There are PC_PRINTER_ routines in Net Express that allow you to specify the font and size to be used by the printer to print the file. Please refer to the online documentation for these library routines. Old KB# 3861
Problem: When using the .Net Framework email classes in the System.Net.Mail namespace, the method to specify that the format of the mail is HTML. Resolution: Use the "IsBodyHTML" property on the System.Net.Mail.MailMessage class. $set sourceformat"variable" program-id. Program1 as "SMTP.Program1". environment division. configuration section. repository. class cMailMessage as "System.Net.Mail.MailMessage" class cMailAddress as "System.Net.Mail.MailAddress"  
Problem: Ensuring that programs are ANSI'85 compliant and setting this directive ANS85, but do not get error messages for syntax elements which are NOT represented in ANSI'85-COBOL. Resolution: The ANS85 directive adds the ANSI'85 COBOL features to a selected language level. Please use the directive DIALECT"ANS85" to restrict the COBOL features to ANSI'85. Old KB# 3855
Problem: What can you do if the toolbar under the pulldown menus of the IDE is missing or hidden? Resolution: Click on the 'View' pulldown menu and then click on 'Dockable windows'. Tick on the 'toolbar' option. This should bring back the toolbar that was hidden. Old KB# 3901
Problem: Application von SX4.0 SP2 für Server Unixware 7.1 Problem: Aufruf eines prozeduralen Cobol-Programms von JAVA über das JNI, nachgestellt an Hand des Testbeispiels calc_pi aus dem DEMO Verzeichnis PI des Net Express 4.0: Das Programm funktioniert unter Windows 2000 sowohl von der Kommandozeile als auch im Fenster. Das Programm wurde auf ein Unixware System portiert und dort mit dem Programm cobjrun in einer Terminalsession ausgeführt. Es funktioniert. Nun wurde die Klasse calc_pi innerhalb von Tomcat ausgeführt. Tomcat selbst wurde mt cobjrun gestartet. Es kommt die folgende Fehlermeldung: Exception in thread "main" java.lang.UnsatisfiedLinkError: no libcobjvm_unx_142 in java.library.path at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1517) at java.lang.Runtime.loadLibrary0(Runtime.java:788)
Problem: If you are using extfh using direct calls how can you determine the record size of a file ? Resolution: To get the record size you would need to use the Special Operation opcode 06. This will return record length for files that have file header information. This is documented in the file handler documentation supplied with the product. Old KB# 3891#AcuCobol#RMCOBOL#COBOL#netexpress#ServerExpress
Problem: when trying to create a new project, I receive the following: General failure: could not create project. Resolution: In this case - the user needed write access to folder where project was being created Old KB# 3848
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.