Databridge 6.5 Service Pack 1 Release Notes

August 2018

Micro Focus Databridge 6.5 Service Pack 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.

1.0 What’s New?

This release includes several changes, fixes, and new features, which are described in detail in the section, "What's New In This Release" in Chapter 1 of the Databridge Installation Guide. The following outline the key features and functions provided by this version, as well as issues resolved in this release:

1.1 What’s New

The following upgrade to your Micro Focus product(s) is now available:

  • Databridge Host 6.5 Service Pack 1

  • Databridge Client 6.5 Service Pack 1

  • Databridge Enterprise Server 6.5 Service Pack 1

  • Databridge DMSII Client 6.5 Service Pack 1

  • Databridge Twin 6.5 Service Pack 1

The following outline the key issues resolved in this release:

  • The "auto_reclone" parameter has been deprecated, as this feature did not work correctly with online garbage collection reorgs. The two options that are available are:

    1. Stop the client when a garbage collection is detected.

    2. Let the client deselect the affected data sets and reclone after all the reorgs are completed. The -y option for the process command makes it simple to reclone these data sets.

  • The update rate statistics has been enhanced to work in the granularity of milliseconds to account for the improved clock for the client. This issue caused the load to get unbalanced when using multi-threaded updates.

  • A new algorithm to balance the load, which does not use past update rate history, was implemented. This new algorithm responds to changing loads and gets automatically rebalanced when the characteristics of the load change.

  • A new parameter named inhibit_init_values was implemented to allow sites with large tables to leave new columns as NULL following a DMSII reorganization. This improves performance over setting them to the DMSII initial values.

  • SQL Server and Oracle clients have been tested with databases in the cloud. To use Oracle in the cloud, modifications were made to the client to eliminate the need for the grant of select on SYS.OBJ$.

  • Using SQL Server in the cloud involves a server name containing dots, which gets truncated at the first dot when using the ODBC driver to retrieve the server name. You need to set the configuration parameter "use_odbc_reg" to true in the [signon] section of the configuration file to make the client get the full server name from the registry, which is needed to make bcp work correctly.

IMPORTANT:Databridge version 6.5 will be the final release that supports DBTanker.

For the list of software fixes and enhancements in previous releases, see Previous Releases.

1.2 License Key Update

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

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

1.3 Security Guidelines

Databridge 6.5 Service Pack 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.

1.4 Version Information

The Databridge components and utilities are listed below with their version number in the base release of version 6.5 and the current release of Databridge 6.5 Service Pack 1.

Host

Table 2

Host

Base Release

Current Release

DBEngine version:

6.5.0.048

6.5.2.073

DBServer version:

6.5.0.030

6.5.2.038

DBSupport version:

6.5.0.008

6.5.1.010

DBGenFormat version:

6.5.0.014

6.5.1.016

DBPlus version:

6.5.0.010

6.5.1.014

DBSpan version:

6.5.0.002

 

DBSnapshot version:

6.5.0.004

 

DBTwin version:

6.5.0.006

6.5.2.007

DMSIIClient version:

6.5.0.007

6.5.1.008

DMSIISupport version:

6.5.0.007

6.5.2.012

DBInfo version:

6.5.0.004

 

DBLister version:

6.5.0.002

 

DBTanker version:

6.5.0.001

 

DBAuditTimer version:

6.5.0.001

 

DBChangeUser version:

6.5.0.002

 

DBAuditMirror version:

6.5.0.001

 

DBCobolSupport version:

6.5.0.002

 

DBLicenseManager version:

6.5.0.001

 

DBLicenseSupport version:

6.5.0.021

 

Table 3

FileXtract

 

Initialize version:

6.5.0.001

 

PatchDASDL version:

6.5.0.002

 

COBOLtoDASDL version:

6.5.0.002

 

UserdatatoDASDL version:

6.5.0.001

 

UserData Reader version:

6.5.0.000

 

SUMLOG Reader version:

6.5.0.002

 

COMS Reader version:

6.5.0.000

 

Text Reader version:

6.5.0.000

 

BICSS Reader version:

6.5.0.000

 

TTrail Reader version:

6.5.0.000

 

LINCLog Reader version:

6.5.0.002

 

BankFile Reader version:

6.5.0.000

 

DiskFile Reader version:

6.5.0.000

 

PrintFile Reader version:

6.5.0.000

 

Table 4

Enterprise Server

 

DBEnterprise version:

6.5.0.073

6.5.1.086

DBDirector version:

6.5.0.003

 

EnumerateDisks Version:

6.5.0.001

6.5.1.002

LINCLog version:

6.5.0.1026.73

6.5.1.002

Table 5

Client

 

bconsole version:

6.5.0.000

6.5.2.001

dbutility version:

6.5.0.015

6.5.2.082

DBClient version:

6.5.0.015

6.5.2.082

DBClntCfgServer version:

6.5.0.015

6.5.2.082

dbscriptfixup version:

6.5.0.015

6.5.2.082

DBClntControl version:

6.5.0.003

6.5.1.005

dbctrlconfigure:

6.5.0.003

6.5.1.005

dbfixup version:

6.5.0.002

6.5.2.007

migrate version:

6.5.0.000

 

dbpwenc version:

6.5.0.000

 

dbrebuild version:

6.5.0.015

6.5.2.082

2.0 System Requirements

Databridge 6.5 Service Pack 1 includes support for the following hardware and software requirement:

System Support Updates

  • Support for 32-bit clients will be removed in the next major release of Databridge.

  • 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 53.1 through 59.1

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:

  • Windows 7

  • 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. 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:

  • 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 2016

  • Microsoft SQL Server 2014

  • Microsoft SQL Server 2012

  • Microsoft SQL Server 2008 R2 (up to SP1)

  • Microsoft SQL Server 2005 (up to SP4)

  • Oracle 11g, and 12c

Client - UNIX and Linux

One of the following systems:

  • Sun Microsystems SPARCstation running Solaris 10 or later.

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

  • IBM pSeries running AIX 5.3L 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, or 12c

NOTE:Oracle 12c 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).

NOTE:Before installing a Databridge 6.5 Hot Fix, Update, or Service Pack you must have installed the base release of Databridge 6.5. If the base release of Databridge 6.5 is not currently installed follow the installation guide documentation to install Databridge 6.5.

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.5 service.

Databridge Host

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

    ftp my_aseries_host
<login>
bin
put DB65xxxxx.con DB65xxxxx

  2. Log on to the Databridge usercode on the host and go to CANDE.

  3. To unwrap encapsulated files in the DB65xxxxx file, use the following command:

    WFL UNWRAP *= AS = OUTOF DB65xxxxx TO DISK (RESTRICTED=FALSE)

Databridge Client, Client Console and Enterprise Server

  • On Windows, open the Windows32 or Windows64 folder of the Hot Fix, Update, or Service Pack and double-click the file databridge.D65bbbb-xxxx-Wnn.exe (where xxxx can be "HOTFIX", "UPDATE", or “SERVICEPACK” depending on the type of release). All installed components such as the Client, the Console, or Enterprise Server will be updated.

    NOTE:After the installation is complete, restart the Client Manager service/daemon manually. In the case of Windows, the service will not automatically start after a patch is applied.

  • 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

For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/.

Copyright © 2018 Attachmate Corporation, a Micro Focus company. All Rights Reserved.