Micro Focus Databridge 6.6 Update 1 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.
The following outline the key features and functions provided by this version, as well as issues resolved in this release:
This update includes several fixes and improvements to Databridge components and utilities.
Client Improvements
Fixed the SQL Server Client handling of DMSII REAL(Sm,n) items that are negative.
Fixed the SQL Server Client to convert the values of DMSII ALPHA items, which get stored as a number, to native form.
Improved functionality of the Windows Client during data extraction when using bcp or SQL*Loader.
Fixed the Flat File Client redaction code when redacted_database parameter is set to 1.
Improved how the Client stores links.
Fixed the client to correctly set the host variable length for binary columns.
Resolved the handling of DMSII link updates.
Fixed multi-threaded data extractions involving links to allow the CREATE buffer to be processed prior to being released.
The aa value at the beginning of the record gets converted to a decimal value without error when cloning data sets with links if the parameter use_decimal_aa or use_binary_aa is true.
Resolved client errors when setting a LINK to NULL.
Improved how the client handles DMSII links that have OCCURS clauses.
Improved the client’s use of buffers when a data set, which maps to multiple tables, has links.
DBEngine Improvements
Fixed the following issue:
DBSupport faults with an INVALID INDEX or DBEnterprise fails with a formatting error if the data set has a symbolic link. For example:
ADDRESS-LINK IS KEY OF ADDRESS-BY-RSN;
Previously, symbolic links and self-correcting links were converted to normal data items. They will now remain as links.
NOTE:DBSupport must be recompiled after installing this patch.
Fixed client database handling of links and other data items in records that are longer than 4095 half-bytes.
DBServer Improvements
Fixed DBServer to use only the primary audit file if the AUDIT ON option specifies PRIMARY.
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.
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.
Databridge 6.6 Update 1 includes the following security guidelines:
Table 1
|
For |
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. |
The Databridge components and utilities are listed below with their version number in the release of version 6.6 Update 1.
Host
Table 2
|
Host |
|
|
DBEngine version: |
6.6.0.021 |
|
DBServer version: |
6.6.1.008 |
|
DBSupport version: |
6.6.0.000 |
|
DBGenFormat version: |
6.6.0.000 |
|
DBSpan version: |
6.6.0.003 |
|
DBSnapshot version: |
6.6.0.000 |
|
DBTwin version: |
6.6.0.001 |
|
DMSIIClient version: |
6.6.0.005 |
|
DMSIISupport version: |
6.6.1.001 |
|
DBInfo version: |
6.6.0.000 |
|
DBLister version: |
6.6.0.000 |
|
DBAuditTimer version: |
6.6.0.000 |
|
DBChangeUser version: |
6.6.0.000 |
|
DBAuditMirror version: |
6.6.0.001 |
|
DBCobolSupport version: |
6.6.0.000 |
|
DBLicenseManager version: |
6.6.0.001 |
|
DBLicenseSupport version: |
6.6.0.000 |
Table 3
|
FileXtract |
|
|
Initialize version: |
6.6.0.000 |
|
PatchDASDL version: |
6.6.0.000 |
|
COBOLtoDASDL version: |
6.6.0.000 |
|
UserdatatoDASDL version: |
6.6.0.000 |
|
UserData Reader version: |
6.6.0.000 |
|
SUMLOG Reader version: |
6.6.0.000 |
|
COMS Reader version: |
6.6.0.000 |
|
Text Reader version: |
6.6.0.000 |
|
BICSS Reader version: |
6.6.0.000 |
|
TTrail Reader version: |
6.6.0.000 |
|
LINCLog Reader version: |
6.6.0.000 |
|
BankFile Reader version: |
6.6.0.000 |
|
DiskFile Reader version: |
6.6.0.000 |
|
PrintFile Reader version: |
6.6.0.000 |
Table 4
|
Enterprise Server |
|
|
DBEnterprise version: |
6.6.1.013 |
|
DBDirector version: |
6.6.0.001 |
|
EnumerateDisks Version: |
6.6.0.001 |
|
LINCLog version: |
6.6.1.001 |
Table 5
|
Client |
|
|
bconsole version: |
6.6.0.000 |
|
dbutility version: |
6.6.1.030 |
|
DBClient version: |
6.6.1.030 |
|
DBClntCfgServer version: |
6.6.1.030 |
|
dbscriptfixup version: |
6.6.1.030 |
|
DBClntControl version: |
6.6.0.002 |
|
dbctrlconfigure: |
6.6.0.002 |
|
dbfixup version: |
6.6.0.000 |
|
migrate version: |
6.6.0.000 |
|
dbpwenc version: |
6.6.0.000 |
|
dbrebuild version: |
6.6.1.030 |
Databridge 6.6 Update 1 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) -or- Windows PC that meets the minimum requirements of its operating system, which is one of the following:
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 -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:
One of the following databases:
|
|
Client - UNIX and Linux |
One of the following systems:
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:
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. |
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
On the MCP Server, upload DB66xxxxx using binary or image file transfer (where xxxx is a string of characters that identifies the type of release).
ftp my_aseries_host <login> bin put DB66xxxxx.con DB66xxxxx
Log on to the Databridge usercode on the host and go to CANDE.
Extract the install WFL from the above mentioned file, using the following command:
WFL UNWRAP *WFL/DATABRIDGE/INSTALL AS WFL/DATABRIDGE/INSTALL OUTOF DB66xxxxx
Run the Databridge install file to apply the patch.
START WFL/DATABRIDGE/INSTALL
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.
START WFL/DATABRIDGE/INSTALL ("DATABRIDGE", "otherpack")
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.
WFL UNWRAP *= AS = OUTOF DB66xxxxx TO DISK (RESTRICTED=FALSE)
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.
© 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.