Databridge 7.0 SP1 Release Notes
Last Updated: February 2023
Version 7.0 SP1 Update 4
February 2023
Fixes and changes in version 7.0 SP1 Update 4
- The parameter
use_dmsii_keyswas added to the Kafka client to make it use the DMSII SET selected by the Engine as the keys rather than always using the AA Values/RSN as the key. - The parameter
json_output_optionwas added to the Kafka client to control the content of UPDATE and DELETE records in the JSON output. - Implemented keep alive to broker for Kafka client.
- Updated the Kafka library
librdkafka.so.3. -
The daemon script was enhanced to use the TERM signal to stop the daemon and the USR1 or USR2 signals to write the RPC trace and the program status to the file
trace.login the working directory. -
The atm_crypto libraries were updated to version 3.4.24 to mitigate these vulnerabilities:
- CVE-2023-0286
- CVE-2023-0215
- CVE-2022-4304
-
Resolved several issues. This release includes cumulative fixes in previous versions. Refer to the patch notes for individual software component for details.
Version Information
The Databridge components and utilities are listed with their version numbers in the base release of version 7.0 and in the current release. All host programs have been compiled with MCP Level 57.1 software.
| Databridge Client | Base release | Current release |
|---|---|---|
| bconsole version: | 7.0.0.000 | 7.0.7.001 |
| dbutility version: | 7.0.0.000 | 7.0.7.082 |
| DBClient version: | 7.0.0.000 | 7.0.7.082 |
| DBClntCfgServer version: | 7.0.0.000 | 7.0.7.082 |
| dbscriptfixup version: | 7.0.0.000 | 7.0.7.082 |
| DBClntControl version: | 7.0.0.006 | 7.0.7.020 |
| dbctrlconfigure: | 7.0.0.006 | 7.0.7.020 |
| dbrebuild version: | 7.0.0.000 | 7.0.4.082 |
| Databridge Administrative Console | Base release | Current release |
|---|---|---|
| Administrative Console | 7.0.0 | 7.0.7 |
Version 7.0 SP1 Update 3
November 2022
Fixes and changes in version 7.0 SP1 Update 3
- Removed the JXPath library to mitigate CVE-2022-41852.
Version 7.0 SP1 Update 2
October 2022
Fixes and changes in version 7.0 SP1 Update 2
- Apache Commons Text library was updated to version 1.10.0 to mitigate CVE-2022-42889.
- Apache Shiro library was updated to version 1.10.0 to mitigate CVE-2022-40664.
- The Administrative Console was updated to use Java 11.
Note
On Linux systems, you must install the provided Java 11 (replace Java 8) because the Administrative Console now requires Java 11.
Version 7.0 SP1 Update 1
October 2022
Fixes and changes in version 7.0 SP1 Update 1
-
Corrected the problems with updating the “Blackout period” parameter from the Administrative Console.
-
Changed the data sources page to show "Blacked out" data sources as Blacked out rather than Not defined.
-
Modified the Kafka client to use update types of 1 – 3, which represent "insert", "delete", and "update".
-
Corrected the Kafka client’s handling of key changes to implement a key change as a DELETE followed by an INSERT.
-
Enhanced the Oracle client’s index creation to use the "parallel 8" and the "nologging" options to speed the index creation.
-
Reworked the redefine command to eliminate the concept of back-to-back redefine commands, by making the command restore the old copy of the control tables from the unload file before calling Compare_Layouts(), like the Administrative Console’s Customize command does.
This change makes the
-uoption meaningless for the "Redefine" command. -
Modified the UNIX/Linux version of the dbfixup program to launch a shell script to refresh the control tables.
Launching dbutility directly returned an exit code of
-1, which caused dbfixup to assume that the refresh failed. -
Implemented the
-noption for dbfixup to defer the running of redefine command and ensuing generate command. When the user tries to run a process command, it will exit with an exit code indicating that a redefine command is required before updates can be processed. -
When a blackout period ends, the service now restarts process commands that were interrupted by the blackout period.
-
Resolved several issues. This release includes cumulative fixes in previous versions. Refer to the patch notes for individual software component for details.
Version 7.0 SP1
June 2022
Fixes, features, and changes introduced in version 7.0 SP1
-
The install package contains only 64-bit software. The Windows folder replaces the Windows64 and Window32 folders.
-
Added support for the "max_string_size" parameter in the Oracle Client to allow it to use wider varchar2 and raw columns, which is more efficient than using clob.
-
Added support for the Oracle TIMESTAMP data type in user columns that allows fractions of seconds in time stamps.
-
The configuration file parameter "keep_undigits" was changed to three values instead of being a boolean. Values of
0and1work in the same way as before. A value of2extends1to treat undigits in numeric fields like 9s, similar to most MCP COBOL applications. -
Support for HP-UX Itanium was removed; it is available on demand.
Databridge Client
-
(018) Implemented the configuration file parameter "suppress_delete_msgs." When set to True, this parameter stops the Client from reporting data errors for DELETE operations that result in discards. The Client ignores such discards because the target records have keys with data errors and cannot be in the relational database. They are not included in the discard count and they are not written to the table's discard file.
-
(019) The Oracle Client is susceptible to buffer overruns when cloning the dataset with the widest table because the size estimation fails to take into account the fact that character data is enclosed in quotes.
-
(020) The user column “create_time”, which was originally implemented for the SQL Server client, does not work correctly for the Oracle client.
-
(021) Implemented the parameter "enable_extended_types" for the Oracle clients to allow the client to honor the Oracle database’s “max_string_size” parameter, which when set to “extended” increases the maximum size of the varchar2 and raw data types to 32K. If the client finds the parameter set to extended, it starts using the value for the maximum size for such column. The upgrade requires a redefine command to take effect.
-
(022) Implemented protocol negotiation between the administrative console and the service to allow 7.0 consoles to connect to 6.6 services and 6.6 consoles to connect to 7.0 services. Implemented the changes needed to reconcile the two protocols. All console operator commands that have protocol dependencies pass the protocol level along with the command allowing the client to generate the response using the right protocol.
Client Manager Service
-
(007) Fixed buffer sizing bug in service code for the one-time password used to allow scripts launched by the service to connect back to the service. This bug caused the service to occasionally crash.
-
(008) Implemented protocol negotiation between the administrative console and the service to allow 7.0 consoles to connect to 6.6 services, and 6.6 consoles to connect to 7.0 services. Implemented the changes needed to reconcile the two protocols. All console operator commands that have protocol dependencies pass the protocol level along with the command allowing the client to generate the response using the right protocol.
Administrative Console
- (007) Fixed formatting errors in the "Lag time" and "db op counts" columns of the monitor.
- When updating the Databridge Administrative Console over an existing Linux/UNIX installation, we recommend removing the contents of the lib directory beforehand.
Version Information
The Databridge components and utilities are listed with their version numbers in the base release of version 7.0 and in the current release. All host programs have been compiled with MCP Level 57.1 software.
| Databridge Host | Base release | Current release |
|---|---|---|
| DBEngine | 7.0.0.002 | 7.0.1.006 |
| DBServer | 7.0.0.002 | |
| DBSupport | 7.0.0.000 | |
| DBGenFormat | 7.0.0.001 | |
| DBSpan | 7.0.0.000 | |
| DBSnapshot | 7.0.0.000 | |
| DBTwin | 7.0.0.000 | |
| DMSIIClient | 7.0.0.000 | |
| DMSIISupport | 7.0.0.001 | |
| DBInfo | 7.0.0.000 | 7.0.1.001 |
| DBLister | 7.0.0.000 | |
| DBChangeUser | 7.0.0.000 | |
| DBAuditTimer | 7.0.0.000 | |
| DBAuditMirror | 7.0.0.000 | |
| DBCobolSupport | 7.0.0.000 | |
| DBLicenseManager | 7.0.0.000 | |
| DBLicenseSupport | 7.0.0.000 |
| Databridge FileXtract | Base release | Current release |
|---|---|---|
| Initialize | 7.0.0.000 | |
| PatchDASDL | 7.0.0.000 | |
| COBOLtoDASDL | 7.0.0.000 | |
| UserdatatoDASDL | 7.0.0.000 | |
| UserData Reader | 7.0.0.000 | |
| SUMLOG Reader | 7.0.0.000 | |
| COMS Reader | 7.0.0.000 | |
| Text Reader | 7.0.0.000 | |
| BICSS Reader | 7.0.0.000 | |
| TTrail Reader | 7.0.0.000 | |
| LINCLog Reader | 7.0.0.000 | |
| BankFile Reader | 7.0.0.000 | |
| DiskFile Reader | 7.0.0.000 | |
| PrintFile Reader | 7.0.0.000 |
| Databridge Enterprise Server | Base release | Current release |
|---|---|---|
| DBEnterprise | 7.0.0.000 | |
| DBDirector | 7.0.0.000 | |
| EnumerateDisks | 7.0.0.000 | |
| LINCLog | 7.0.0.000 |
| Databridge Client | Base release | Current release |
|---|---|---|
| bconsole | 7.0.0.000 | |
| dbutility | 7.0.0.000 | 7.0.3.023 |
| DBClient | 7.0.0.000 | 7.0.3.023 |
| DBClntCfgServer | 7.0.0.000 | 7.0.3.023 |
| dbscriptfixup | 7.0.0.000 | 7.0.3.023 |
| DBClntControl | 7.0.0.006 | 7.0.3.008 |
| dbctrlconfigure | 7.0.0.006 | 7.0.3.008 |
| dbfixup | 7.0.0.000 | |
| migrate | 7.0.0.000 | |
| dbpwenc | 7.0.0.000 | |
| dbrebuild | 7.0.0.000 | 7.0.3.023 |
File Structure
The directory structure is similar to previous releases; however, the console is now a separate install located in the Console\Windows directory in the install package. The console install includes a private JRE.
Hot Fixes, Updates, and Service Packs will use the same directory structure as the install package.
Note
Hot Fixes, Updates and Service Packs still contain a patch in the Windows directory, which updates the Client and Enterprise Server. The console is patched by running setup.exe from the Console\Windows directory, which reinstalls the console software and its private JRE.
System Requirements
Databridge 7.0 SP1 includes support for the following hardware and software requirements.
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 59.1 through 62.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) or - Windows PC that meets the minimum requirements for one of these operating systems:
TCP/IP transport - To view the product Help, a supported Internet browser (such as Microsoft Edge, Firefox, or Google Chrome) is required. In addition, JavaScript must be enabled in the browser settings to navigate and search Help. |
| Databridge Administrative Console | - We recommend that you install the Administrative Console and the Client on different machines. Installing the Administrative Console on the same machine as the client can lead to performance issues as well as monitoring failures because connection issues on the Client machine will also affect the Administrative Console's ability to monitor activity. - The Administrative Console install includes a private JRE that is used to run the Administrative Console server. |
| 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 Administrative Console on 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 or - 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:
+ For Windows systems only ++ Oracle 18c requires Solaris 11.4 or newer |
| Client - UNIX and Linux | One of the following systems:
- 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 18c requires Solaris 11.4 or newer |
Downloading Databridge 7.0 SP1
The Micro Focus Software, License and Downloads (SLD) site offers two download options. Choose the appropriate one for your environment.
-
If Databridge 7.0 is already installed, then download and install
Databridge 7.0 SP1. -
If you are installing Databridge 7.0 for the first time (such as upgrading from 6.6), then download and install
Databridge Host, Databridge Enterprise Server, and All Clients. ZIP format. (7.0 + SP1).
Installation Instructions
See the Installation Guide for information on system and installation requirements, upgrade instructions, and other helpful tips.
Note
The new Administrative Console must be installed following the installation of the Databridge software. See the Databridge Installation Guide section on Installing the Databridge Administrative Console for instructions on installing the Administrative Console on Windows and UNIX machines.
We recommend that you install the Administrative Console in a separate server from the client machine(s) for the following reasons:
- The Administrative Console can use significant resources that may impact the client's performance.
- If the Administrative Console is installed with a Client machine, the Administrative Console would not be able to monitor activity when the client machine is down. By having the Administrative Console on a different machine, you can monitor Client Manager(s) and receive alerts for to address warnings and connectivity errors.
Contacting Micro Focus Customer Support
For specific product issues, contact Micro Focus Technical Support.
For additional technical information, see:
Legal Notice
© 2023 Open Text
The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.