Quantcast
Channel: RM/COBOL Knowledge Base
Viewing all 82 articles
Browse latest View live

What is the format of the catalog file that is used by Relativity?

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by Adrian.Bean on 7/8/2015 3:30:47 PM

Problem

A user is trying to open a Relativity catalog, but is getting format errors within the designer tool. Why is that happening?

Resolution

As part of the process of creating a Relativity catalog, the file manager needs to be identified. For the majority of cases, this is the RM file handler as the data files are RM files. It is possible to configure Relativity to access MF files, so the file handler needs to be set to the MF file handler.

Once the catalog file handler has been set, not only are the data files accessed using the specified file handler, but the catalog is also created using that file handler. This means that if the MF file handler is used, the catalog is created in the Micro Focus format, not in the RM file format.

When the catalog is deployed, or the location is moved (eg moved from a development machine to a deployment server), the same version of the file handler needs to be present so that the catalog is correctly accessed.

Incident #2827659

Tags: RM Cobol, Relativity

What is the correct way to configure/debug WOW Thin Client on a UNIX system?

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by Steve Jolivet on 7/20/2015 7:56:05 PM

Problem:

What is the correct way to configure/debug WOW Thin Client on a UNIX system?

Resolution:

First, make sure that you are using the version of WOW Thin Client on the Windows system that matches the version of the runtime. You cannot mix versions.

Next, make sure you are using a Runtime Plus version or Development version of the runtime on the UNIX/Linux system. The Runtime Plus and Development versions support Thin Client, while the regular Runtime does not. If unsure, contact Support and give us the serial number; we can check for you.

For normal execution:

1. Make sure the rpcstart script has execute permissions. For this example, it is located in the /usr/rmcobol directory and should look like this:

#!/bin/sh

#

TERM=dumb; export TERM

RM_LOAD_WOW_CLIENT=yes; export RM_LOAD_WOW_CLIENT

cd /usr/rmcobol && runcobol ./helowrld.cob k

(You can locate the rpcstart script anywhere, but make sure the rpcplus.ini file is in the same directory, and have the script change to that directory before executing the runcobol command.)

2. The entry in the /etc/inetd.conf file should look like:

rpcplus stream tcp nowait root /bin/sh rpcplus /usr/rmcobol/rpcstart

3. Whenever you change the inetd.conf file, you have to restart the service. This can be accomplished by using the command:

kill -HUP <pid>

Where <pid> is the process id of the inetd process. Use this command to determine whether inetd is listening:

netstat -a | grep "rpcplus"

This command should show an rpcplus port in a LISTEN state.

4. From the Windows system, make sure you can successfully ping the UNIX server.

For debugging:

1. Look at the rpcplus.log file for error messages. If nothing is obvious, continue.

2. Create a script file called "debugrpc" in the /usr/rmcobol directory, with the following contents:

#!/bin/sh

#

TERM=dumb; export TERM

RM_LOAD_WOW_CLIENT=yes; export RM_LOAD_WOW_CLIENT

cd /usr/rmcobol && ./runcobol ./helowrld.cob A=D

(You can use a program other than helowrld, but if it is not in the current directory, use the full path to it. Also, you can locate debugrpc in another directory, but you must put a copy of the rpcplus.ini file in the same directory, and change to it before executing the runcobol command.)

3. Modify the rpcplus.ini files on the server and the client systems to use a port not listed in the /etc/services file.

4. Make sure the debugrpc file has execute permissions, then type:

./debugrpc

When you hit the return key, it should sit there and wait for a client. If so, start the client. If not, send the error message and the log file to support@liant.com. If the client does not start, send a screenshot of the error it reports.

    

Old KB# 6441

How do I address an "unauthorized use of runtime/compiler (Loc 810)" error message?

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by Steve Jolivet on 8/10/2015 7:27:01 PM

Problem:

If the RM/COBOL runtime, or, compiler abnormally terminate, then, the use counting mechanism can become corrupt.  This scenario will cause any future instances of the runtime/compiler to fail with a "unauthorized use message (loc 810).

Resolution:

The full text of the Loc 810 error is : System function error (Loc 810) - Semaphore OK but shared memory marked bad.

The "rmucutil" utility will show that there is a shared memory issue. Either reboot or reset the locked "shared memory" to resolve the problem.

Below is the syntax for the "rmucutil" utility, located in your RM/COBOL installation directory:

rmucutil xx-xxxx-xxxxx-xxxx runtime|compiler details

The "rmucutil" utility will show that there is a shared memory issue. 

If the output shows there is a shared memory or semaphore issue, you can clear shared memory and semaphores manually if the ipcs (for Inter Process Communication Status) commands are available on your operating system. The following information outlines the process used to locate and remove the semaphore used by runcobol: 

To remove the semaphores and shared memory, you are looking for the ID's attached to the following values: "524d". You should be able to use the following shell script or type in the commands manually (ipcrm -m id -s id). 

ipcrm `ipcs -m | grep '524d' | grep -v grep | awk '{print "-m", $2}'` 
ipcrm `ipcs -s | grep '524d' | grep -v grep | awk '{print "-s", $2}'` 

The other alternative is to reboot the system.

Please ask your customer not to use kill -9 (SIGKILL) to terminate runcobol processes, or the rmdaemonR, this signal will not allow processes to clean up and will probably leave shared memory or semaphore locked, which will prevent new RM/COBOL processes from starting. It is most likely the cause of this problem.

We recommend using SIGTERM (-15) as this signal will shut down the processes safely, allowing the runcobol or rmcobol command to close files and the rmdeamons to clean up semaphore and shared memory segments.

If no semaphore or shared memory segment problem is reported by rmucutil, please have your customer send us the output that is reported and the output of the following command on their system:

uname -a

**If the recommendations above do not resolve your issue, please contact Micro Focus Customer Care for additional assistance.

Unable to locate the Relativity Data Client, Data Server, or, Data Manager in ODBC Administrator

$
0
0
Revision 2 posted to RM/COBOL Knowledge Base by Steve Jolivet on 10/8/2015 3:26:25 PM
Created On:  21 December 2010

Problem:

We have installed the 32-bit Relativity Data Client, Data Server, or, Data Manager on a 64-bit Windows machine.  After the install, the Data Client, Data Server, or, Data Manager are unavailable in the ODBC Administrator located in the Windows Control Panel.

Resolution:

The 32-bit Relativity Data Client, Data Server, and, Data Manager are 32-bit ODBC drivers.  Therefore, you will not find them listed in the 64-bit ODBC Administrator.  The 64-bit ODBC Administrator can be found in the Administrative Tools area of the Windows Control Panel.

In order to create 32-bit data sources, you must, instead, run the 32-bit version of the Windows ODBC Data Source Administrator.  You will find it here: 
 
C:\Windows\SysWoW64\odbcad32.exe
Incident #2493470
Old KB# 32735
Tags: Relativity ODBC

RM/COBOL Runtime v12 Network Installation

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by Steve Jolivet on 10/12/2015 4:34:57 PM

There are two options for installing RM/COBOL in a networked environment:

1. Perform a "Standard" or "Custom" installation of RM/COBOL on all of the PCs that will execute the COBOL application.

2. Perform an "Administrative" installation on a network share, and, perform a "Network" install on all of the desktop PCs.

Below is an excerpt from page 57 of the RM/COBOL User's Guide in regards to the "Network" installation of RM/COBOL on client machines. This excerpt contains a short summary of the network installation process: 

----------------------------------- 

The RM/COBOL installation process for CodeWatch, Runtime, Recover1, and Compiler supports users who wish to install RM/COBOL on a network server machine and then install RM/COBOL on multiple client machines using the RM/COBOL installation on the server. 

First, install all of the RM/COBOL components that you need onto the server machine using the “Administrative Installation” method. This may be performed either directly on the server or from a client machine via a mapped network drive. The administrative installation will prompt for a Network Folder. This must be the shared folder that the client machines will access for the installation. 

Note Using the “Administrative Installation” will not result in a working installation on the network server or the client machine on which it was run. An administrative installation is merely a preparation for installing on client machines. You must perform a standard, custom, or network installation to have a complete installation on the server machine. This is a change in behavior from previous versions of RM/COBOL. 

Then, on each remaining client machine, invoke the LiantInstall program in the network shared directory that was specified as the Network Folder during the administrative installation, and then specify a network installation on the Installation Type page. This causes the installation process to install the RM/COBOL program folder and icons for those components that already exist in the original server installation. Shared system DLLs (such as CTL3D32.DLL and MSVCRT.DLL) also will be installed on the client machine (if a later version does not already exist there) and appropriate Windows registry entries will be created. 

-----------------------------------

For more information, please see the Chapter 3 in the RM/COBOL User's Guide available on our website at: http://supportline.microfocus.com/productdoc.aspx

How do enable ODBC tracing for Relativity products on Windows?

$
0
0
Revision 2 posted to RM/COBOL Knowledge Base by Steve Jolivet on 3/10/2016 9:19:26 PM

Problem:

If you encounter an issue with the Relativity Data Client, Data Server, or, Data Manager, you can obtain additional information about the failure by enabling a Microsoft Windows ODBC trace.

Resolution:

You can enable the Microsoft Windows ODBC tracing facility with the following:

1. Go to the Windows control panel.

2. Double-click on Administrative Tools.

3. Double-click on Data Sources(ODBC). *If this is a 32-bit product running on 64-bit Windows, you will need to use the 32-bit ODBC Administrator (C:\Windows\SysWOW64\odbcad32.exe)

4. Double-click on the Tracing tab.

5. In the Log File Path, choose where you want the log file to be created.

6. When you want to begin logging, click the button labeled: "Start Tracing Now"

You should enable tracing right before causing the error to occur.

**After the error message has occurred, turn off tracing to reduce overhead.

How can I set up WOW Thin Client to run more than one program?

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by Steve Jolivet on 3/11/2016 5:51:26 PM

Problem:

It may be necessary to execute different WOW programs through the Thin Client architecture, without, being able to set up different server configurations for each program.

Resolution:

Starting with the version 9 release, the WOW program can act as a "menu" program (without making the user choose), by using the GETCLIENTARGS function to get the command line of the wowclient.exe (i.e. use "wowclient.exe myprogram" in a program shortcut).

Then, based on this information, the program on the server can determine *which* WOW program to start. You will need to use UNSTRING to get the separate arguments, but this method requires only one port.

From the Help files below (it is not currently included in the User's Guide):

RPC WOW GETCLIENTARGS Function

The GETCLIENTARGS function can be executed on the server in a Thin Client architecture to retrieve any parameters that were part of the command line when the Thin Client executable (wowclient.exe) was started. It can be called only by the server portion of a Thin Client application, not the client. This function may be called by any program in the run unit on the server and may be called more than once.

Calling Sequence

CALL GETCLIENTARGS USING ARGUMENTS.

Parameter Declaration Description

ARGUMENTS PIC X(255) - An alphanumeric data item of at least 255 characters.

Firewall error message during installation of RM/COBOL.

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by Steve Jolivet on 9/12/2016 7:46:54 PM
Created On:  9 August 2010

Problem:

The RM/COBOL installation fails on Windows with the following error message: "Unknown error 0x1002: CallOpenFirewallPort failed."

Resolution:

One of the requirements for the RM/COBOL installation is that the Windows Firewall either is running or is capable of running.

You can check the current status of the Windows Firewall service by going to the Services control panel utility (Control Panel Services). Then right-click on the "Windows Firewall" service listing and select "Properties".

From the "Properties" dialog, you will need to ensure that the Windows Firewall service is not set to disabled and that it can be "Started". If you cannot "Start" the service then you will have to address that issue before installing the Runtime.
Tags: Firewall, RM/COBOL, installation

How do I install both an RM/COBOL Development, and Runtime, System on UNIX?

$
0
0
Revision 1 posted to RM/COBOL Knowledge Base by Steve Jolivet on 10/27/2016 5:00:13 PM

Problem:

If you are installing separately licensed RM/COBOL Development, and Runtime, System products on the same UNIX machine, and, into the same directory, then, you will need to combine those licenses into the same vault file (license.vlt).

Resolution:

In order to install separately licensed RM/COBOL Development, and Runtime, System products, you only have to install the Development system, as that includes a Runtime.  Once the Development System has been installed, then, you can add the higher Use Count Runtime license to the existing license vault using the Liant License Utility(licverifyall).

The licverifyall program ships with the latest versions of our products, and may be found under the SupportTools directory of the product installation.

You can use licverifyall to add the Runtime *.lic to the current license.vlt (that already has the Development System license in it) with the following procedure: 

* Make a backup copy of the existing license.vlt file. 

* Change to the SupportTools directory and place the Runtime System's license certificate(*.lic) file in that location. 

* Execute the licverifyall program with no parameters from a command prompt. It will find the liant.lic file and the existing vault file, and insert the Runtime license into the file. 

Test by running the runcobol command. The banner should display the correct license and Use Count information. If not, put the original license.vlt file back in place (using the backup copy made earlier) and contact us.

Decimal values truncated when using an ADO.NET application with Relativity

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by Steve Jolivet on 10/27/2016 5:21:44 PM

Problem:

When using an ADO.NET application to query a Relativity data source, all, returned decimal data is truncated.

Resolution:

Microsoft's ADO (ActiveX Data Objects), which is used to access ODBC from VB, C#, SQL Server, etc..., does not work with the standard Relativity driver. To avoid this issue, a Relativity ODBC driver has been introduced that is optimized for ADO. This new driver is automatically installed with the Relativity Data Manager, Relativity Data Client (32-bit), and Relativity Data Client (64-bit). The driver names are:

  • Relativity for ADO (*.rcg)
  • Relativity Client for ADO
  • Relativity Client for ADO (64-bit)

This new ADO-compliant driver is available in Relativity v12.13, and above.

Knowledge Base

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by BrianMcCaughey on 2/7/2017 8:31:14 AM

Welcome to the RM/COBOL Knowledge Base. The Knowledge Base contains a large amount of information that may answer any technical questions you have. To take full advantage of the Knowledge Bases across the Community please use the site search found at the top of the page. This search offers a wide range of customisation to narrow down your search to find your article.  If you fail to find a solution here SupportLine will be able to assist you further.

How do I handle invalid numeric data in my Relativity tables?

$
0
0
Revision 1 posted to RM/COBOL Knowledge Base by Steve Jolivet on 4/10/2017 1:25:21 PM

This article describes the method for configuring a Relativity catalog to suppress invalid numeric data in a returned column.

Problem:

COBOL allows invalid numeric data to be stored in a numeric field.  However, since ODBC does not, invalid numeric data will cause an error to be returned when that data is encountered in a column.

Resolution:

In order to resolve the issue of invalid numeric data, you can configure Relativity to return NULLs for any encountered invalid numeric data.  To do so, you can use the Nullable Column Utility.

The Nullable Column utility allows you to choose and apply the nullable settings for all numeric and date columns in your Relativity catalog.  To start this utility in the Relativity Designer window, click Nullable Column Utility on the Tools menu.

 

The following table describes the options available on the pages of the Nullable Column utility:

 

Option

Description

Welcome

The utility opens with the Welcome page, which explains the purpose of the utility.

Click Next button to proceed to the next page of options or click Cancel to close the utility.

Settings

The Settings page allows you to change global catalog settings that determine when NULLs are returned for certain valid data.

·    Note  The following two global data source attributes may also be configured on the Data Source page of the Options dialog box.

-  The Invalid Numerics Return NULL option indicates that the Relativity DBMS will return a NULL value for any column based on a data item containing invalid numeric data.

-  The Invalid Dates Return NULL option indicates that the Relativity DBMS will return a NULL value for any date or date/time column based on a data item containing invalid date ranges either because the underlying numeric data is invalid, or the month or day is out of range.

Click the down arrow in either list box to change the three possible states for these options:

-  Select Never to cause the DBMS to return an error when this condition is encountered.  (This is the default.)

-  Select Yes, Except for Record Key Data Items to cause the DBMS to correct the condition for all data items except for record keys, which will still return an error.

-  Select Always to cause the DBMS to correct the condition in all instances.

Note  Selecting the Always state will result in some numeric data items not being available to participate in SQL indexes.

·    To specify whether settings are to be previewed or applied, choose from the following:

Report Only, to view a report containing only the results of changing these settings.

Apply Settings, to apply the settings without viewing a report.

Report First, then optionally apply, to view a report and then (optionally) apply the settings.

·    Select all the tables or a group of tables in the data source to process with either the Process All Tables or Select Tables to Process options.

Note  If you choose the Select Tables to Process option, the Table Selection page is displayed, prompting you to select the appropriate tables.  Make your selection(s) and click Next.

·    Click Cancel to close the utility, click Back to return to the previous page, or click Next to open the Options page.

Options

The Options page allows you to select which columns are to be included in an index:

·    Only columns that do not participate in an index.  Indicates a sorted index.  Relativity supports only Clustered indexes.

·    All columns.  Indicates an index that can be used to directly index to a row in the table, but is not otherwise sorted.

CAUTION  You may lose indexes depending on your settings for the Invalid Numerics Return NULL and the Invalid Dates Return NULL options on the Settings page.

·    Click Cancel to close the utility, click Back to return to the previous page, or click Next to open the Summary page.

For more information on indexes, refer to "Relativity Indexes" under the For Advanced Users | Relativity-Specific topic in the DBMS Help file.

Summary

A list of all the options you selected is displayed on the Summary page.

Click Finish to start the process.  A Status Report window opens and displays actions taken, and also explains why some actions were not taken.

Note  If on the Settings page you chose to apply the settings rather than simply review a report, you will be prompted with a message to confirm whether you want to update the data source with these changes.

Where can I obtain support for BIS-Express?

$
0
0
Revision 2 posted to RM/COBOL Knowledge Base by Steve Jolivet on 6/6/2017 10:44:09 AM

Problem

Who provides support for the BIS-Express web application generator for Xcentrisity Business Information Server(XBIS)?

Resolution

 

BIS-Express is an application and web service generator designed to work with Micro Focus' Xcentrisity Business Information Server software.  This application generation solution is supported, and distributed, by England Technical Services (ETS). Below is a link to their home page:

 

            http://showcase.netins.net/web/etsinc/index.html

 

Note:

 

The standard Xcentrisity BIS product is supported by Micro Focus; however the specific syntax of BIS Express or issues relating to the use of BIS Express are supported by ETS. 

Tags: RM/COBOL, BIS Express

Why do I need an Activation Code?

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by Steve Jolivet on 7/14/2017 2:28:12 PM

Problem:

Why do I need an Activation Code?

Resolution:

Many of our products require an activation code when installed more than 6 months after purchase. Normally, this code is retrieved automatically if the system can connect with activate.liant.com. However, all Evaluation versions require an activation code that must be obtained manually.

If the system cannot retrieve a valid code automatically, the LSRV: number, serial/registration number, a list of 4 four letter words known as a "machine digest", and a message directing you to obtain the activation code manually  will display.  

To obtain the activation code, bring up your browser and enter "activate.liant.com" (without the quotes). Enter the required information. The activation code will be sent via email.

If there is a problem with retrieving the code, which is another list of 4 four letter words, please contact support@liant.com for assistance.  

Activation codes are good for only 24 hours.  If you get the error message: "Activation code has expired" before 24 hours have gone by, fix the time, date, or timezone on the system. (Remember that Noon is PM and Midnight is AM.)

On Linux systems, you must also set the TZ variable correctly.

    

Old KB# 4665

What are the benefits to upgrading my index files to file version 4?

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by Steve Jolivet on 7/25/2017 11:21:20 AM
 

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 Support

There 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=64
RUN-INDEX-FILES USE-LARGE-FILE-LOCK-LIMIT=YES

**Some systems may require a lower LARGE-FILE-LOCK-LIMIT than the default 64 GB.
 
3. Run rmdefinx on existing index files that are at the 2 GB limit. The above settings will affect only the lock limit placed into the Key Information Block (KIB) for new file version 3 or 4 indexed files created by the runtime system. Existing indexed files always use the lock limit stored when the file was created. In addition, the file version should be changed to the highest setting your runtime version supports. Only file versions 3 and 4 support large files.

Even if the file is at the highest file version that setting your runtime version supports, you must re-enter the file version setting in order to get the prompt to change the File Lock Limit.

Atomic I/O

Below are the steps for enabling Atomic I/O:

1. Use rmdefinx to change the file version format of existing Index files to version 4, turn on Atomic I/O, and run recovery:
 
runcobol rmdefinx A=', CONVERT4 , ATOMICIO, RECOVER1'

where is the name of the file to use.

You may run rmdefinx in batch mode in order to convert a large number of indexed files at the same time. To do so, you must construct a batch stream or command script that runs rmdefinx on each index file. Be certain that you have a current backup of all files being converted.

Note that the path to the runcobol and recover1 commands must be specified in your PATH environment variable and the path to rmdefinx must be in your RUNPATH.

The following general example could be used in a .bat file to convert to file version 4 and Atomic I/O, then automatically run the recover1 utility. Also, it will terminate with return code 1 and the file name, if any error occurs:

start /w runcobol rmdefinx a="d:\dat\file1,CONVERT4 , ATOMICIO, RECOVER1"
if errorlevel 1 echo "error on file1" >>errlog
start /w runcobol rmdefinx a="d:\dat\file2,CONVERT4 , ATOMICIO, RECOVER1"

start /w runcobol rmdefinx a="d:\dat\file3,CONVERT4 , ATOMICIO, RECOVER1"
if errorlevel 1 echo "error on file3" >>errlog
.
start /w runcobol rmdefinx a="d:\dat\file,CONVERT4 , ATOMICIO, RECOVER1"

2. Turn on Atomic I/O for new files, by entering this configuration record into your configuration file:

RUN-INDEX-FILES ENABLE-ATOMIC-IO=YES

For more information regarding the RM/COBOL Define Indexed File (rmdefinx) Utility, file version 4, large file support, or, Atomic I/O, please see the RM/COBOL User’s Guide.  The RM/COBOL User’s Guide is available on our web site at: https://supportline.microfocus.com/productdoc.aspx
 

Creating an index file greater than 2GB

$
0
0
Revision 3 posted to RM/COBOL Knowledge Base by Steve Jolivet on 8/25/2017 2:19:23 PM

Starting with the availability of file version 3 for release version 6.6, RM/COBOL has supported the creation of index files greater than 2 GB. With the release of version 7.5 and file version 4, the default file index file version supports these large files.

There 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 do it differently.

2. Next, edit/create the default configuration file (runcobol.cfg) located in the RM/COBOL installation directory. Add the following two records to that file:

----------------------

RUN-FILES-ATTR LARGE-FILE-LOCK-LIMIT=512
RUN-INDEX-FILES USE-LARGE-FILE-LOCK-LIMIT=YES

----------------------

Some systems may require a lower LARGE-FILE-LOCK-LIMIT than the default 64 GB; 9 is usually safe for most systems.

3. Run rmdefinx on existing index files that are at the 2 GB limit. The above settings will affect only the lock limit placed into the Key Information Block (KIB) for new file version 3 or 4 indexed files created by the runtime system. Existing indexed files always use the lock limit stored when the file was created. In addition, the file version should be changed to the highest setting your runtime version supports. Only file version 3 and 4 support large files.

Even if the file is at the highest file version that setting your runtime version supports, you must re-enter the file version setting in order to get the prompt to change the File Lock Limit.

See the description of the rmdefinx utility in the RM/COBOL User's Guide for more information.

Writing to an index file fails with an RM/COBOL I/O Error 24, 02

$
0
0
Revision 2 posted to RM/COBOL Knowledge Base by Steve Jolivet on 8/25/2017 2:22:47 PM
Created On:  23 April 2012

Problem:

When attempting to add a new record, or, update an existing record, the, WRITE fails with a COBOL I/O error 24, 02.

Resolution:

A COBOL 24, 02 error indicates that there is insufficient room left in the file for the operation.  This behavior can occur when an index file has reached it's maximum size as defined by it's configured File Lock Limit.
 
In order to have the affected file grow larger, you will need to modify the configured File Lock Limit and, possibly, the Index File Version using the Define Indexed File (rmdefinx) Utility.
 
If you would like all newly created files to be configured with a larger file limit, then, you will need to add the following keywords to your RM/COBOL Runtime Configuration file(*.cfg):
 
RUN-FILES-ATTR LARGE-FILE-LOCK-LIMIT=n
RUN-INDEX-FILES USE-LARGE-FILE-LOCK-LIMIT=YES

**Where, n, is the File Lock Limit as expressed in gigabytes(GB).  The default is 512.
 
For more information on "File Lock Limit" and the Define Indexed File (rmdefinx) Utility, please see the RM/COBOL User's Guide.  The RM/COBOL User's Guide is available on our website at: 
 
http://supportline.microfocus.com/productdoc.aspx

 

Is there a 64-bit Relativity ODBC driver for Windows and how is it installed and used?

$
0
0
Revision 2 posted to RM/COBOL Knowledge Base by Steve Jolivet on 11/6/2017 1:39:21 PM

Problem

 

Some applications require a 64-bit Windows ODBC driver; is there a 64-bit Relativity driver and if so, how can it be installed and used?

 

Resolution

 

There is a 64-bit ODBC Relativity driver for windows and it supplied as part of the Windows Data Server and the Windows Data Client products. By default, the 64-bit ODBC driver is not installed so this needs to be manually installed before it can be used.

Installing the 64-bit ODBC Relativity driver

 

The Relativity Data Client for Windows installation media can be downloaded from support line product updates site.

The Windows Data Server product is ordered from Micro Focus and supplied as an Electronic Delivery Product (EPD) that is downloaded from a secure web site.

Once the relevant executable has been run, a DClient\046 directory will be created under the directory that the executable was run from. In that directory is the file DClient64.msi.

DClient64.msi can be run from a command line or from a windows explorer and this will install the 64-bit ODBC Relativity driver using the standard windows installer.

Once the driver has been installed, use the 64-bit ODBC Configuration Manager. There is only one 64-bit ODBC Relativity driver and that is the Relativity Data Client driver. Below is an example of a configured 64-bit System DSN.

Points to note:

  1. The various Relativity ODBC data client products are available to download from Support Line products update site. To be able to view the Relativity Data Client downloads, a valid Relativity Data Server serial number must be associated with the Web-id used to login to the support line website. As the 64-bit ODBC driver is a Relativity Data Client, the update cannot be seen if the Web id only has a Relativity Data Manager serial number associated with it.

  2. As the 64-bit Driver is a Relativity Data Client, it requires a Relativity Data Server to running to service the requests for Data. It will not work with the Relativity Data Manager product. There is not a 64-bit version of the Relativity Data Manager product.

  3. As this is a 64-bit ODBC driver, the 64-bit ODBC Configuration Manager must be used. Care must be taken if system DSN’s are be setup and there are 32-bit Relativity drivers already installed on the machine. Because of a design flaw with ODBC on windows, system DSN’s are shared between 32-bit and 64-bit ODBC drivers. It is recommended that either the name or the description of 64-bit system DSN’s indicates that they using the 64-bit ODBC driver. It is possible to accidently try to use a 64-bit ODBC DSN with a 32-bit application. If that happens, an ‘architecture mismatch’ error will occur when connecting to the data source.

  4. The 64-bit ODBC Relativity does work with a 32-bit Relativity Data Server. At present there is only a 32-bit Relativity Data Server available.

 

Incident: # 2794872

 

 

 

Tags: RM Cobol, 64bit Driver, Relativity, odbc

RM/COBOL Runtime v12 Network Installation

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by Steve Jolivet on 8/9/2018 5:26:08 PM

There are two options for installing RM/COBOL in a networked environment:

1. Perform a "Standard" or "Custom" installation of RM/COBOL on all of the PCs that will execute the COBOL application.

2. Perform an "Administrative" installation on a network share, then, perform a "Network" install on all of the desktop PCs.

Below is an excerpt from page 57 of the RM/COBOL User's Guide in regards to the "Network" installation of RM/COBOL on client machines. This excerpt contains a short summary of the network installation process: 

----------------------------------- 

The RM/COBOL installation process for CodeWatch, Runtime, Recover1, and Compiler supports users who wish to install RM/COBOL on a network server machine and then install RM/COBOL on multiple client machines using the RM/COBOL installation on the server. 

First, install all of the RM/COBOL components that you need onto the server machine using the “Administrative Installation” method. This may be performed either directly on the server or from a client machine via a mapped network drive. The administrative installation will prompt for a Network Folder. This must be the shared folder that the client machines will access for the installation. 

Note Using the “Administrative Installation” will not result in a working installation on the network server or the client machine on which it was run. An administrative installation is merely a preparation for installing on client machines. You must perform a standard, custom, or network installation to have a complete installation on the server machine. This is a change in behavior from previous versions of RM/COBOL. 

Then, on each remaining client machine, invoke the LiantInstall program in the network shared directory that was specified as the Network Folder during the administrative installation, and then specify a network installation on the Installation Type page. This causes the installation process to install the RM/COBOL program folder and icons for those components that already exist in the original server installation. Shared system DLLs (such as CTL3D32.DLL and MSVCRT.DLL) also will be installed on the client machine (if a later version does not already exist there) and appropriate Windows registry entries will be created. 

-----------------------------------

For more information, please see the Chapter 3 in the RM/COBOL User's Guide available on our website at: http://supportline.microfocus.com/productdoc.aspx

How do I install RM/COBOL in a Windows network environment?

$
0
0
Current Revision posted to RM/COBOL Knowledge Base by Steve Jolivet on 8/9/2018 5:26:44 PM

There are two options for installing RM/COBOL in a networked environment:

1. Perform a "Standard" or "Custom" installation of RM/COBOL on all of the PCs that will execute the COBOL application.

2. Perform an "Administrative" installation on a network share, then, perform a "Network" install on all of the desktop PCs.

Below is an excerpt from page 57 of the RM/COBOL User's Guide in regards to the "Network" installation of RM/COBOL on client machines. This excerpt contains a short summary of the network installation process:

-----------------------------------

The RM/COBOL installation process for CodeWatch, Runtime, Recover1, and Compiler supports users who wish to install RM/COBOL on a network server machine and then install RM/COBOL on multiple client machines using the RM/COBOL installation on the server.

First, install all of the RM/COBOL components that you need onto the server machine using the “Administrative Installation” method. This may be performed either directly on the server or from a client machine via a mapped network drive. The administrative installation will prompt for a Network Folder. This must be the shared folder that the client machines will access for the installation.

Note Using the “Administrative Installation” will not result in a working installation on the network server or the client machine on which it was run. An administrative installation is merely a preparation for installing on client machines. You must perform a standard, custom, or network installation to have a complete installation on the server machine. This is a change in behavior from previous versions of RM/COBOL.

Then, on each remaining client machine, invoke the LiantInstall program in the network shared directory that was specified as the Network Folder during the administrative installation, and then specify a network installation on the Installation Type page. This causes the installation process to install the RM/COBOL program folder and icons for those components that already exist in the original server installation. Shared system DLLs (such as CTL3D32.DLL and MSVCRT.DLL) also will be installed on the client machine (if a later version does not already exist there) and appropriate Windows registry entries will be created.

-----------------------------------

For more information, please see the Chapter 3 in the RM/COBOL User's Guide available on our website at: http://supportline.microfocus.com/productdoc.aspx

Viewing all 82 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>