Rocket® COBOL

This article helps resolve the error message received when installing EntperiseLink. Problem: We are receiving the following error when trying to install EnterpriseLink: Setup previously required to reboot. You must do this before running setup. Resolution: If you get this error after rebooting, this can be resolved by deleting the ENTSetup key in the registry under HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce. Old KB# 14507#Rumba#EnterpriseLink

This article explains what the Rebuild –d option specifies when reconstructing the index of an indexed file. Problem: The –d option specifies that Rebuild should reconstruct the index of an indexed file from the data area. Any corrupt data records are skipped and logged to a file. However, if rebuild is entered at the command line you get: -d [:c] –rebuild corrupt data file What does it do, rebuild the index or rebuild data? Resolution: If the data portion of the file is intact and only the index portion is corrupt, then Rebuild can generate a new index (.idx) file from the data file with no loss of data. If the data portion of the file is corrupt then Rebuild can rebuild a complete new indexed file, both data and index portions, but there will be loss of data as Rebuild discards any corrupt data records that it encounters. Note: When you use Rebuild to generate a new index file from an existing data file, the file can grow in size. One reason i

This article explains how to call COBOL subprograms that are located in different directories to the main calling program when executing from a command prompt. Problem: When executing a main calling COBOL program from a command prompt, how is it possible to enable any called subprograms that are in different directories to be found and called successfully? For example: program1.int resides in c:\\dir1 and program2.int resides in c:\\dir2 and program3.int resides in c:\\dir3 and so on… As it stands, if you were to execute program1.int from a command prompt, when it called program2.int you would get a 173 file not found error displayed as the subprogram is not in the main folder. Resolution: You need to set the COBDIR environment variable if called module is not found in the current directory. This can be done as follows in relation to the scenario described above by creating a .bat file containing the following entries: setlocal set COBDIR=c:\\dir1;c:\\dir2;c:\

This article provoide more information about the Database Connectors Error. Problem: I can be difficult to determine from the file status the reason why an error has occurred. How can I get more information on a problem. Resolution: The Database Connector has been enabled for CTF (Consolidated Trace Facility). To obtain additional output you need to add the eprintf entry as a trace entry. An example trace config file that is enabled for the Database Connectors component is: mftrace.level=info mftrace.emitter.textfile#location=c:\\temp\\logs mftrace.emitter.TEXTFILE#FORMAT=$(TIME) $(COMPONENT) $(THREAD) $(EVENT) $(LEVEL)$(DATA) ## Component Run-time System mftrace.level.mf.rts=INFO mftrace.comp.mf.rts#all=false mftrace.comp.mf.rts#eprintf=true mftrace.comp.mf.rts#memory=false To enable CTF you need to add an environment variable MFTRACE_CONFIG that points to the config file. Incident Number: 2266679 Old KB# 14482

This article explains what to do when AcuXDBC gives the wrong date for a date mask that specifies only the year and month, YYYYMM. Problem: AcuXDBC supports incomplete date types. This feature is documented in Section 3.3.4 of the AcuXDBC User’s Guide as: "It is sometimes desirable to have incomplete date types, for example to have YYYYMM to simply store the year and month. AcuXDBC defaults the month and day to 1, so that incomplete types will be valid. Note that AcuXDBC can handle incomplete date types, but if you have a complete type and invalid date data, AcuXDBC cannot handle the date." However, if only a partial date mask is specified, the unspecified portion does not default to the correct value. For example, with a date mask of YYYYMM and data of 200810, the field might assume the value 2008-OCT-00 (which is not a valid date) instead of the correct value of 2008-OCT-01. Resolution: This is a known issue and has been fixed in Ver

This article explains an error that occurs when the environment points to the wrong assembler. Problem: We have received this error when trying to create an executable on HP/UX: Assembler error: can't open Z for reading: No such file or directory Resolution: This error occurs because the environment is pointing to the wrong assembler (as) . To find the correct assembler look at the file $COBDIR/docs/env.txt. The entry which identifies the required assembler will look something like the following: Assembler: as HP92453-03 UX.11.01.31 PA-RISC 2.0 Assembler as -V 2>&1 < /dev/null |cut -c5-80| head -1 The first line indicates the version certified by Micro Focus for this product. The second line indicates the command to execute on the local machine to see the version of the assembler that’s actually being used. Server Express requires the Hewlett Packard version of the assembler and will not run with a GCC version. If the correct version of t

This article provides instructions on how to extract the installation media from the downloaded UNIX gunzip tar archive. Problem: After downloading a UNIX gunzip tar deliverable, follow the steps below to decompress the deliverable and create the installation components. These instructions assume that gunzip has already been installed. The gunzip tool is available at www.gzip.org, both in source form and as executable files. This tool runs on a number of platforms, including Windows. Note that other Windows ZIP tools can also decompress a gunzip tar file; however, you should be careful when extracting files from the resulting tar file. Make sure that any tar file CR/LF conversion option is turned off. Resolution: Save the License Certificate attached to the electronic delivery email. Following the download, change the working directory to the directory that contains the deliverable. The deliverable will have a name in the form deliverable.tar.gz, w

How can you create a batch file transfer using RUMBA AS400 File transfer? Problem: Users of RUMBA AS400 File transfer want File Transfer sessions to run unattended. They may do so by taking advantage of the Batch File Transfer feature in Rumba. Resolution: You can create a File Transfer from/to an AS/400 that runs in batch mode from the command line, with no input required. Batch File Transfers can be scheduled to run at certain times of day. To create a Batch File Transfer: Configure an AS/400 File transfer profile, including the query that selects the information you need. Test to ensure it works properly. Save this profile. By default, the file extension is .RTO. From the AS/400 File Transfer window, go to Transfer > Batch... Click on the Add Transfer button (this can be found next to the X and the up and down arrows), and select the .RTO file you created on step 2. Click Save As... to save the batch transfer. This will create a file

This article provides information on the location of the vutil error code table and an example of using the table in problem resolution. Problem: When performing a file operation using vutil or vutil32, an error may be encountered. For example, the following vutil command vutil -info MYFILE may result in the following error: MYFILE: File broken (code 69) Understanding what “code 69” means would be helpful in resolving this error. Resolution: Vutil error codes are the same as the Vision file secondary error codes for error 98. The list of error codes may be found in the ACUCOBOL-GT Appendices Version 8.1, Appendix E: File Status Codes, E.3 Vision Secondary Error Codes for Error 98s. For this example, the entry in the list of errors would be: 69 A Vision 4 or 5 index segment is not found during an open. This error code is specific to Vision 4 or 5 files that consist of two parts, a data segment and an index segment. T

This article explains what to do when Animator starts in an X window and the font size is too small. Problem: Background information: Animator will start in an X window under the following circumstances: When you are using Server Express on UNIX or Linux, and When the DISPLAY environment variable specifies a valid X terminal, and When starting Animation using: the “cobanim” command, or the COBSW= A environment variable, or just-in-time debugging, or CBL_DEBUGBREAK, or Debugging Services and Applications on Enterprise Server using the cobesdebug utility The problem is that the Animator window may be too small for practical use. Resolution: Animator opens “xterm” in an X terminal window. Animator does not specify any particular font, so xterm will use the default font configured within X. To change this X default, you could edit/create a file named .Xresources in your home directory. It should resemble t

Problem: In Net Express with .Net version 5.0 a CALL “MethodName” could be used to call a static method. When the method is defined in the same project, it still works unchanged with Net Express 5.1. When the called method has been placed in a different project, compiling this code in Net Express 5.1 results in: warning COBCH0987: Could not find method 'METHODENNAME' with this signature - will generate dynamic call. Executing the program gives the message: RTE 173: Program not found. Resolution: It is not recommended to CALL a method. An INVOKE is the correct way to start a method. There might be existing programs which CALL methods, and for these programs there is a way doing it in Net Express 5.1: A change can be made in the CALL allowing a dynamic CALL to unmanaged code, for example, CALL VariableName, which disallows the old behavior at CALL “MethodName”. The following steps are necessary for static COBOL methods to be

This article discusses the following error: RM-AddOnInit failed in the wow Runtime dll and WOW MFC Runtime (wowmfcrt.dll) load failure Problem: When attempting to run a WOW Extensions v12 application on Windows 2000 (thick or thin client) you experience the following errors: RM-AddOnInit failed in the wow Runtime dll” and “WOW MFC Runtime (wowmfcrt.dll) load failure Resolution: Deploy the attached uxtheme.dll into the directory containing the wowmfcrt.dll. This DLL provides stubs for the theme functions used by the WOW runtime. Note: The un-themed WOW runtime references these function but does not attempt to call them as Microsoft doesn’t provide theme support on Windows 2000. Incident Number: 2284518 Old KB# 14451

This article explains the error message "LMF 004: You have exceeded the license limit for this product". Problem: We received the message "LMF 004: You have exceeded the license limit for this product". Following this message, a further message indicates the number of license units in the license database, all of which are in use. For example: "No more licenses for this product are available. All of the 0002 license units in the license database are in use. You may continue using this product after this message as a temporary unlicensed user." Resolution: It is possible that the number of licenses available has been exceeded, in which case you will have to contact your sales representative in order to purchase more licenses.  However, if you believe that you have not exceeded the licenses available, it may be possible that a rogue process is still running behind the scenes and is still making use of a license. To check the state of all processes running do one of

This article describes a scenario that uses the XFD_MAP variable and provides an example for using one XFD for more than one file or table. Problem: In this scenario, the use of a single XFD is desired rather than many XFDs, one for each of several different tables. The table names have the pattern "???MYHIS" where each "?" represents a variable character in the table name. However, putting "*MYHIS=[abcmyhis.xfd]" in the ACUFH configuration file (mfdbc.conf) does not work. What values should be in the SELECT for the ASSIGN TO and the $XFD FILE= directive in the FD for this to work properly? Resolution: The following is a step-by-step explanation: The program has a SELECT for a file ABCMYHIS, with a variable assigned, something like this:SELECT ABCMYHIS ASSIGN TO WS-ABCMYHIS-NAME ... Immediately before the FD, there is an XFD FILE directive, which is required because of the variable ASSIGN:$XFD FILE= ABCMYHI

This article describes how to enable Windows XP and Vista themes. Problem: WOW Extensions has a default look and feel based upon Windows 98 controls. This can make an application developed using WOW Extensions to look quite dated. Resolution: Windows XP and Vista interface provides a more modern look and feel, i.e. themes. You can enable the theme support by simply replacing the existing wowmfcrt.dll with the one attached in this article. Note: Theme support has been provided via Microsoft’s manifest technique. This technique has some known problems with redrawing certain controls and container controls. It is highly recommended to backup your existing wowmfcrt.dll and aggressively test your application to ensure that the interface behaves as you expect, changes may be required to provide workarounds for unwanted behavior. Theme support is provided “as is”. This DLL is only suitable for version 12. Incident Number: 2282338 C:\\wowmfcrt.zipDate: Name: Description of change: Date:

This article explores the licensing error ASLM - You need to rerun as root (No Error Number). Problem: This message was received after a reboot and when trying to run a program. The message does not include any error number as with a similar message relating to the semaphore file /var/aslmfsem. Resolution: This error is caused by the absence of or incorrect permissions pertaining to the file /var/.mng2sys. > ls -la /var/.mng2sys -rw-rw-rw- 1 root root 56 Jun 29 15:32 /var/.mng2sys The problem can be resolved by running a program as 'root'. For example: > cobrun hello ASLM: You need to rerun as root > echo $COBDIR /home/products/9i.T4.40.03 > su Password: # export COBDIR=/home/products/9i.T4.40.03 # export PATH=$COBDIR/bin:$PATH # export LD_LIBRARY_PATH=$COBDIR/lib # cobrun hello hello # exit exit > cobrun hello hello Old KB# 14485#COBOL#Licensing#ServerExpress

This article explains an error that occurs if a COBOL program using XML is not linked to shared runtime. Problem: When linking a COBOL program to an EXE you can get the following error message: LNK2001: unresolved external symbol _CBL_XMLIOOr LNK2001: unresolved external symbol _CBL_XMLIO_INTERFACE Resolution: This error occurs if you attempt to link a COBOL program that contains XML syntax to the static COBOL runtime. COBOL programs that use XML need to be linked to the shared runtime. If you change the build setting for your EXE then it should link correctly. Incident Number: 2284296 Old KB# 14492

This article explains what to do if AcuXDBC sends you the error message “Too many columns NNN (max: 256)." Problem: When trying to access a VISION file through AcuXDBC that has more than 256 fields (columns) — the default maximum number of columns allowed — a user receives a “Too many columns NNN (max: 256)” error message. Resolution: The user can change the default of 256 columns in the “Advanced” tag of the data source name (DSN). The Maximum Columns field on this tag can be set to up to 8191. Incident Number: 2284263 Old KB# 14471

This article explains why the ViewNow X server does not honor the –geometry parameter when starting X clients. Problem: When X clients are started with the –geometry parameter, ViewNow X server doesn’t honor the position information given. Why is this? Resolution: In ViewNow X, the –geometry flag is overridden by settings in the server which are intended to prevent windows from inadvertently obscuring each other. These settings can be changed to prevent this behavior by performing the following steps: Launch the ViewNow X control panel. From the Start menu, go to Start > Programs > ViewNow > X Windows > Control Panel. Alternatively, launch \\Program Files\\NetManage\\APPS\\X\\CPanel.exe from the command line. From the Options menu, select “Window…” On the Window Management dialog, uncheck the “Cascade Windows” option. Click OK to dismiss the dialog. Re-launch the ViewNow XServer. Subsequent invocations of X clients with the –geometr

This article explains how a core dump can assist when a program abends. Problem: What can be done to produce a core dump file when a fatal error occurs in a COBOL program running under Server Express on UNIX? How can a core dump file to assist with problem resolution be produced when a program abends? Resolution: There is a run time configuration parameter that can be set to generate a core dump. By default a core file is never produced, if this parameter is set the runtime system produces a core file when any system signal is received that would normally produce a core file on the host system, for example, SIGILL, SIGSEGV (which would usually produce a ime system error 114), and so on. To generate a core dump add the runtime tunable core_on_error to the run-time configuration file. For details on the run-time configuration file and runtime tunables, see the chapter Runtime Configuration in the Server Express User's Guide. Example: Edit a file /tmp/mycon

This article describes how to include the <xml version="1.0" > header in COBOL output when using XML Syntax Extensions. Problem: When using XML Syntax Extensions, the COBOL output does not include the <xml version="1.0" > header. Resolution: The <?xml version="1.0"?> header is actually an XML Processing Instruction so you need to output it using the Syntax for Processing Instructions. For example: $set preprocess(prexml) o(foo.pp) warn endp select xml-stream assign "out.xml" organization is xml document-type is omitted file status is xml-bookdb-status. xd xml-stream. 01 xmls-group identified by "group". 05 xmls-Number pic 9(18) identified by "elementNumber" is attribute. 05 xmls-Alpha pic x(80) identified by "elementAlpha". working-storag

This article describes a possible reason for the run-time system error 9/107 and a potential work around. Problem: COBOL programs were compiled using the CREATEXFD and CALLFH (ACUFH) directives as required for Database Connectors. An XFD file was generated. The database being accessed was Oracle 10g.The program received a 9/107 error on OPEN OUTPUT, but a table was created in the database. The Consolidated Trace Facility (CTF) log (rts32.textfile.PID.log) revealed the following generated SQL: CREATE TABLE ... succeedsALTER TABLE MYTABLE ADD CONSTRAINT iMYTABLE_0 PRIMARY KEY () ... fails: ORA-00936: missing expression Resolution: Examining the COBOL program source revealed that the VAR-LENGTH XFD directive had been misplaced, causing the Compiler to generate an invalid XFD file. Note the difference in the position of the VAR-LENGTH directive in the examples below. Example 2 shows the correct location. Example 1 03 MY-SERVICE REDEFINES MY

This article explains how to use the ANY LENGTH clause to define the incoming string in the sub program. Problem: Is it possible to to pass strings to a sub-program without the sub-program knowing the length of the passed string? Resolution: Use the ANY LENGTH clause to define the incoming string in the sub program. The attached example defines a user function, MyFunc, which receives strings of any length and calculates the length based on the position of the last non-space alphanumeric character in the string. The MyMain.cbl program uses two different variables, one defined as a PIC X(20) and the other PIC X(378). These variables are assigned string values and the MyFunc function is called twice, once for each variable. Myfunc defines the incoming linkage item as PIC X ANY LENGTH, allowing it to receive varying length strings. Incident Number: 2266912 Old KB# 14479

The RM/COBOL v12.02 Linux install script fails with a cpio error: Premature end of file. This article explains what to do when this happens. Problem: The version 12.02 installation script, (install.sh), does not properly recognize the Linux 32-bit platform. Therefore, the script chooses the incorrect options for cpio. These incorrect command-line options for cpio cause the “Premature end of file” message. Resolution: The attached zip archive, install.sh.zip, contains a modified installation script (install.sh) that will detect the Linux 32-bit platform and set the proper cpio command-line options. Download this modified script and use it to replace the install.sh file contained in the RM/COBOL downloaded installation media. Incident Number: 2260814 Old KB# 14467

This article describes how to resolve an XML-code 201 error for XML PARSE when parsing data that contain German umlauts, French accented characters, or a charater that has an ANSI code larger than 0x79. Problem: When parsing data that contains German umlauts, e.g. äöüÄÖÜ or ß, French accented characters, e.g. àÀéèÉÈ, or a charater which as an ANSI code larger as 0x79 XML PARSE delivers an XML-code 201, which is "Miscellaneous XML document parsing errors". <ROOTELEMENT><GermanWords>Ärger Öse Übel -</GermanWords><ABitFrench>ètè means summer</ABitFrench></ROOTELEMENT> Resolution: These characters require the ISO8859-1 encoding specified in front of the root element: <?xml version="1.0" encoding="ISO8859-1"?><ROOTELEMENT><GermanWords>Ärger Öse Übel -</