Databridge 6.6 Release Notes

June 2019

Micro Focus Databridge 6.6 includes new features, enhancements, and bug fixes.

Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs.

The documentation for this product is available on the Documentation Website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the Databridge documentation posted at the Documentation Website.

1.0 What’s New?

The following outline the key features and functions provided by this version, as well as issues resolved in this release:

1.1 Improvements for Databridge 6.6

This release resolves several issues, including those which were fixed by 6.5 through the 6.5 Service Pack 1 releases.

What’s New in the Databridge 6.6 Release:

  • Added support for MCP and DMSII SSR level 60.0 (version 19)

  • Added support for Windows Server 2019

  • Added support for SQL Server 2017

  • Added support for Oracle 18c on Windows, AIX, Linux and Solaris platforms

  • Developed the Databridge Client for Kafka for Linux platforms.

    The Databridge Client for Kafka enables the Databridge to utilize the Kafka messaging system. The Kafka messaging system is a scalable fault-tolerant data management system that provides efficient real-time data processing. The new component is available in the Kafka folder of the release medium.

Client Improvements

  • Added the ability to use Oracle in the cloud. The Client has been modified to eliminate the need for the GRANT of SELECT on SYS.OBJ$.

  • The SQL Server Client was modified to use the BCP API during data extraction instead of using the bcp utility. This release also supports using the bcp utility as a fallback in case there are problems with the BCP API.

  • Increased performance by extending multi-threaded updates to the data extraction code, which can now run multi-threaded. Both of these are controlled by the parameter "n_update_threads".

  • Added the ability for the clients to control the order in which data sets get extracted. This is done by using the extract_priority column in the DATASETS table.

  • The -n option was added to the reorg command to facilitate the handling of DMSII reorganizations in a multi-sourced database environment.

  • Added support for multi-threaded extracts and updates for the Flat File Client.

  • Added support for data masking with SQL Server 2016 or 2017.

  • The SQL Server and Oracle Clients were enhanced to recognize database errors that indicate that the connection to the database was lost. Previously these errors were treated as SQL errors, which caused the service to disable the data source. The Client now uses exit code 2089 in this situation. The service will then periodically try to restart the client until the database comes back on-line.

  • The lower limit for the second value of the " sql_exec_timeout" parameter was reduced to 30 seconds to allow for faster recovery from hung SQL updates.

DBEngine Improvements

  • Audit files are now read without using DBPlus or DMAuditLib.

  • Added DBTwin support for reformatted (redacted) data items.

  • Host software Hot Fixes and Service Packs are now installed using the same technique as installing the base release.

1.2 Known Issues

  • The Databridge Console does not work with Java 9. Install the Java 8 JRE or an earlier version.

  • Starting with SQL Server 2016, enhanced security no longer allows you to add "NT AUTHORITY\SYSTEM" to the sysadmin role. We suggest one of the following two options to mitigate this problem:

    • Run the service under the user account that is setup to run the command line client (dbutility) and use Integrated Windows authentication.

    • Setup the client to use SQL Server authentication to connect to the database, and continue to run the service under the SYSTEM account.

1.3 License Key Update

For Databridge 6.5 and subsequent releases, a new license key algorithm is required to run Databridge. This new key is based on the components you currently have licensed.

For more information on license keys, contact Customer Care before installing this upgrade.

WARNING:Before installing CSS 3.0 on a ClearPath Software Series machine please contact Micro Focus Customer Care for assistance. A CSS 3.0 migration changes the system type name which invalidates the license key required to use Databridge.

1.4 Security Guidelines

Databridge 6.6 includes the following security guidelines:

Table 1


To decrease security risk

Databridge Host

Install Databridge Host to the Unisys mainframe under its own privileged usercode. This is preferable to installing under the usercode of the DMSII database. If you install and run Databridge under multiple usercodes, you must install a copy of DBEngine under each of those usercodes.Alternatively, you can establish DBEngine as a system library (SL).

Databridge Client

File security helps to protect Client operations by restricting access to the working directory and its files and subdirectories. Access is limited to the administrators and the system account, and to designated users (or on Windows, user groups). In Windows, you can enable file security via the option Enable File Security at installation, or by running the program setfilesecurity.exe as Administrator after installation.From the UserID box and the DBAdministrator box, specify users who can run Databridge Client and modify the working directory and its files. User IDs specified in the DBOperator box can monitor operations by reading the log files, but cannot run Databridge ClientIn UNIX, you restrict file access via the umask entry in the file globalprofile.ini. See Install Databridge Client on UNIX.

Databridge Enterprise Server

File security is automatically enabled when you install Databridge Enterprise. File security protects the configuration and log files by restricting privileges on the PC to users who need to modify the configuration.By default, any user in the Administrators group can modify the configuration files and delete the read-only log files. If you create a user group in Windows called DBEAdmins, only the users in that group will be able to alter the configuration files and delete log files. Likewise, if you create a group called DBEUsers, only the users in that group will be able to view the configuration. For more information, see " Implementing File Security" in the Databridge Enterprise Server Help.

1.5 Version Information

The Databridge components and utilities are listed below with their version number in the base release of version 6.6.


Table 2


DBEngine version:

DBServer version:

DBSupport version:

DBGenFormat version:

DBSpan version:

DBSnapshot version:

DBTwin version:

DMSIIClient version:

DMSIISupport version:

DBInfo version:

DBLister version:

DBAuditTimer version:

DBChangeUser version:

DBAuditMirror version:

DBCobolSupport version:

DBLicenseManager version:

DBLicenseSupport version:

Table 3


Initialize version:

PatchDASDL version:

COBOLtoDASDL version:

UserdatatoDASDL version:

UserData Reader version:

SUMLOG Reader version:

COMS Reader version:

Text Reader version:

BICSS Reader version:

TTrail Reader version:

LINCLog Reader version:

BankFile Reader version:

DiskFile Reader version:

PrintFile Reader version:

Table 4

Enterprise Server

DBEnterprise version:

DBDirector version:

EnumerateDisks Version:

LINCLog version:

Table 5


bconsole version:

dbutility version:

DBClient version:

DBClntCfgServer version:

dbscriptfixup version:

DBClntControl version:


dbfixup version:

migrate version:

dbpwenc version:

dbrebuild version:

2.0 System Requirements

Databridge 6.6 includes support for the following hardware and software requirement:

System Support Updates

  • Databridge will remove support for operating systems and target databases when their respective software company ends mainstream and extended support.

Databridge Host

Unisys mainframe system with an MCP level SSR 54.1 through 60.0

DMSII or DMSII XL software (including the DMALGOL compiler)

DMSII database DESCRIPTION, CONTROL, DMSUPPORT library, and audit files

Databridge Enterprise Server

ClearPath PC with Logical disks or MCP disks (VSS disks in MCP format)


Windows PC that meets the minimum requirements of its operating system, which is one of the following:

  • Windows 7

  • Windows Server 2019 (CORE mode must be disabled for installation and configuration)

  • Windows Server 2016 (CORE mode must be disabled for installation and configuration)

  • Windows Server 2012 R2 (CORE mode must be disabled for installation and configuration)

  • Windows Server 2012

  • Windows Server 2008 R2

Direct Disk replication (recommended) requires read-only access to MCP disks on a storage area network (SAN)

TCP/IP transport

To view the product Help, a supported Internet browser (such as, Internet Explorer, Firefox, or Google Chrome) is required. In addition, JavaScript must be enabled in the browser settings to navigate and search Help.

Databridge Client Console

You can install Client Console to the same machine as the Client; however, this can drain resources and impact the performance of your relational database. Instead, we recommend that you install the Client Console to a machine that connects to the Client machine via TCP/IP transport.

Requires Java Runtime Environment (JRE). Download and install the latest version from Oracle. Install JRE version 8 as the Client will not run on JRE 9. For more information, see Java JRE Installation.

Databridge Client

NOTE:Disk space requirements for replicated DMSII data are not included here. For best results, use a RAID disk array and store the client files on a separate disk from the database storage.

NOTE:Memory requirements do not include the database requirements when running the Client in the server that houses the relational database (consult your database documentation for these). The numbers are for a stand-alone client machine that connects to a remote database server.

If you run the console in the same machine as the Client, it will need an additional 1-2 GB of memory depending on how many data sources you have and how long you let it run. All log information is saved in memory.

Client - Windows

Unisys ES7000


Pentium PC processor 3 GHz or higher (multiple CPU configuration recommended)

2 GB of RAM (4 GB recommended)

100 GB of disk space in addition to disk space for the relational database built from DMSII data)

TCP/IP transport

One of the following operating systems:

  • Windows Server 2019 (CORE mode must be disabled for installation and console cannot be run locally)

  • Windows Server 2016 (CORE mode must be disabled for installation and console cannot be run locally)

  • Windows Server 2012 R2 (CORE mode must be disabled for installation and console cannot be run locally)

  • Windows Server 2012

  • Windows Server 2008 R2

  • Windows 10

  • Windows 8.1

  • Windows 8

  • Windows 7

One of the following databases:

  • Microsoft SQL Server 2017

  • Microsoft SQL Server 2016

  • Microsoft SQL Server 2014

  • Microsoft SQL Server 2012

  • Microsoft SQL Server 2008 R2 (up to SP1)

  • Oracle 11g, 12c, and 18c

Client - UNIX and Linux

One of the following systems:

  • Sun Microsystems SPARCstation running Solaris 11 or later.

  • Hewlett Packard Itanium with HP-UX 11i v3 (B11.31) or later.

  • IBM pSeries running AIX 7.1 or later.

  • Intel X-86 with Red Hat Enterprise Linux Release 6 or later.

  • Intel X-86 with Red Hat SUSE Linux Enterprise Server 11 SP1 or later.

  • Intel X-86 with UBUNTU Linux 14.4 or later.

2 GB of RAM (4 GB recommended)

100 GB of free disk space for installation (in addition to disk space for the relational database built from DMSII data)

TCP/IP transport

One of the following databases:

  • Oracle 11g Release 2, 12c or 18c (AIX, Linux and Solaris only)

NOTE:Oracle 12c and 18c clients only exist as 64-bit programs.

NOTE:If you are using Oracle 11g, we strongly recommend that you upgrade Oracle 11g release 2, as the client is designed for this version of Oracle.

3.0 Installation Instructions for Hot Fixes and Updates

Before you install a hot fix (or update), quit all Databridge applications including the Console, and then terminate the service (daemon on UNIX). After the installation is complete, restart the service/daemon manually. In the case of Windows Installations there is a checkbox in the last dialog of the post-install program "updatepath" that allows you do this without having to go through the Windows control panel).

IMPORTANT:To avoid potential problems, we strongly recommend that you upgrade the Host, Enterprise Server, software simultaneously.

If you're updating the Client software, you must also update the Client Console as the older console is incompatible with the 6.6 service.

Databridge Host

  1. On the MCP Server, upload DB66xxxxx.con using binary or image file transfer (where xxxx can be "HOTFIX" or "UPDATE" depending on the type of release).

    ftp my_aseries_host
    put DB66xxxxx.con DB66xxxxx
  2. Log on to the Databridge usercode on the host and go to CANDE.

  3. Extract the install WFL from the above mentioned file, using the following command:

  4. Run the Databridge install file to apply the patch.


    If installing the Databridge software to a different pack family than the primary pack of the FAMILY substitution statement (FAMILY DISK = primarypack OTHERWISE secondarypack) use the following command instead.


    NOTE:This procedure is identical to that you would do to install the base release.

    The container file DISKINSTALL is provided for backward compatibility, and you can also get it from the DB66xxxxx container file. Alternatively, you can upload DISKINSTALL and get the INSTALL WFL by unwrapping this file.


    The advantage of using the install WFL is that you will not get into trouble if (UNRESTRICTED = FALSE) is not added. New patches replace all the modules regardless of whether they have changed or not.

Databridge Client, Client Console and Enterprise Server

  • On Windows, open the Windows64 folder of the Hot Fix or Update and double-click the file databridge.D66xxxx.W64.exe. All installed components such as the Client, the Console, or Enterprise Server will be updated.

  • On UNIX, upload the appropriate tar files for the Client and Console from the update to the directories where these components are installed. (the Client and Console should be installed in separate directories to facilitate maintenance.) If you use Windows to process the extract of the tar file from the zip file, you must transfer the tar file to UNIX using binary FTP.

    Continue by using the following command:

    tar  -xvf <filename>

    where <filename> is the full name of the tar file. This command replaces the files in the Databridge install directory with updated files from the tar file.

    NOTE:To avoid accidentally deleting the Databridge applications, we recommend that you always keep the install directory and the working directory separate.

4.0 Legal Notice

© Copyright 2019 Micro Focus or one of its affiliates.

The only warranties for products and services of Micro Focus and its affiliates and licensors (Micro Focus) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.