The following summary highlights what is new in Connect ETL 9.13.
9.13.22
- Improved system security and stability by updating internal core components.
Fixed Issues
- Fixed an issue where data extracted from a Teradata 11-character column was truncated during encoding conversion.
For more information, see Fixed issues for 9.13.22.
9.13.19
- Additional support was added for EBCDIC code pages in DMXMFSRT/DMXMMSRT. For more information, see 9.13.19 table entry in New functionality.
Fixed Issues
- Corrected the errors which caused processes to fail when using Report Writer options such as /SECTION or /SECTIONFOOTER.
- String concatenation for constants caused max lengths and NULL characters added to the output file.
- Corrected the error that occurred when a job is running to insert data into a target table.
For more information, see Fixed issues for 9.13.19.
9.13.18
- Support higher precision constants-only arithmetic operations. For more information, see 9.13.18 entry in New functionality.
Fixed Issues
- Installing and running Connect ETL using RHEL9.
- Native snappy lib usage in DMX job after CDP 7.1.9 upgrade.
For more information, see Fixed issues for 9.13.18.
9.13.17
- Verify sequence for join task pre-sorted sources.
- Improved performance for high precision arithmetic operations.
For more information, see 9.13.17 entries in New functionality.
Fixed Issues
- Task Editor was taking a long time to verify a database connection.
- An error occurred when running a Connect ETL task writing to a Snowflake target table using a JDBC connection.
- Mainframe target files with floating point numeric fields have some incorrect zero (0) values.
- Repeatedly searching directories that contain many tasks and jobs when "
Look in subfolders
" is checked. - Output file record format inconsistent with expected format.
For more information about these issues, see Fixed issues for 9.13.17.
9.13.16
- Improved performance for high precision arithmetic operations. For more information, see 9.13.16 entries in New functionality.
Fixed Issue
- JCL does not specify target dataset length. For more information about this issue, see Fixed issues for 9.13.16.
9.13.15
- Support for a new file type
Variable record length with 2-byte record prefix (little endian)
and record formatVariable length with 2-byte prefix (little endian)
in the corresponding source and target dialogs. For more information, see 9.13.15 entry in New functionality. - The maximum record length has been increased from 32756 to 32760 bytes. For more information, see 9.13.15 entry in New functionality.
Fixed Issues
- Submitting JCL to a MicroFocus Enterprise Server when Connect DMXMFSRT is configured as the sort replacement. For more information, see Fixed issues for 9.13.15.
- The Task Editor dialog hangs and becomes non-responsive when attempting to map layouts for sample source and target data files. For more information, see Fixed issues for 9.13.15.
9.13.14
Fixed Issue
- Eliminate excessive task validation time when the record layout includes a 5000 plus element variable length array. For more information, see Fixed issues for 9.13.14.
9.13.13
- Support for Connect Serve GUI password repository. For more information, see 9.13.13 entry in New functionality.
- Improved performance for high precision arithmetic operations. For more information, see 9.13.13 entry in New functionality.
- Use DMXMFSRT with JCL to convert hex constants from EBCDIC to ASCII. For more information, see Fixes that change product behavior.
Fixed Issues
- Incorrect output when running multiple tasks and jobs at the same time using mainframe VSAM sources. For more information, see Fixed issues for 9.13.13.
- Running a Connect ETL task or job with an empty target file created on Azure Storage. For more information, see Fixed issues for 9.13.13.
- (COLDSNAV) information about the columns could not be retrieved for "columndata". For more information, see Fixed issues for 9.13.13.
9.13.12
- Support for Windows 11 has been added for 9.13.12 and later.
- Improvements to mainframe IAM file detection.
Fixed Issue
- Task Editor crashes when editing a task that contains an Excel database connection. For more information, see Fixed issues for 9.13.12.
9.13.11
- DMXPublishLineage.jar file and related Lineage REST API components were removed because they are no longer supported.
- Publishing lineage to Cloudera Navigator is no longer supported since Cloudera Navigator has been removed from the Cloudera Data Platform (CDP). For more details, refer to Upgrading CDH 5 to CDP Private Cloud Base.
9.13.10
- Improved performance for large number of source files in a copy task. The elapsed time improves significantly for a Connect-ETL task that processes a large number of source files with the “Original order of source records need not be maintained” performance tuning option set.
- Salesforce QueryAll support. Data extracted from Salesforce.com objects can now include deleted records. For more information, see 9.13.10 entry in New functionality.
Fixed Issue
- An error was generated when running DataFunnel with a Databricks target when mapping metadata from Netezza, Oracle, or Redshift sources. For more information, see Fixed issues for 9.13.10.
- Designing/running new or existing tasks that contain a regular expression with a character class that includes an ambiguous hyphen character. For more information, see Fixes that change product behavior.
9.13.9
Fixed Issues
- Running a job (
dmxjob
) on multiple nodes of a Databricks cluster returns successful even when there are warnings. For more information, see Fixed issues for 9.13.9. - When using wildcards, running a task with more than 32768 source generated a crash report. For more information, see Fixed issues for 9.13.9.
9.13.8
- Remote VSAM file enhancements. IAM file sizes can now be properly detected. For more information, see 9.13.8 entry in New functionality.
Fixed Issue
- An error occurred while creating a directory when running a Connect ETL job on Databricks and the job contains a task with multiple targets writing to Azure storage. For more information, see
- Fixed issues for 9.13.9.
9.13.7
- Initial support for higher precision arithmetic expressions. For more information, see 9.13.7 entry in New functionality.
Fixed Issue
- DMXReport encountered an error when running on a task that contains a connection with a repository password. For more information, see Fixed issues for 9.13.7.
Known Issue
- (MFESFNNS) JCL sort step includes functions that are not currently supported. Micro Focus MFSORT will be used.
Workaround
- Set the environment variable
DMX_MFSERVER_VERSION
to the following.- For Micro Focus Enterprise Server / Enterprise Developer prior to release 4.0 Product Update 18 (including all of 3.0 and earlier releases) and prior to release 5.0 Product Update 7.0 and for Micro Focus Server Express versions release 6.0 Service Pack 2 and later, set
DMX_MFSERVER_VERSION=3
. - For Micro Focus Server Express versions prior to release 6.0 Service Pack 2 but after release 5.1 Wrap Pack 2, set
DMX_MFSERVER_VERSION=2
.
- For Micro Focus Enterprise Server / Enterprise Developer prior to release 4.0 Product Update 18 (including all of 3.0 and earlier releases) and prior to release 5.0 Product Update 7.0 and for Micro Focus Server Express versions release 6.0 Service Pack 2 and later, set
- Restart the Micro Focus server after the environment variable is set.
For more information, see Known issues for 9.13.7.
9.13.6
- Target header enhancement. Target headers can now be generated even when the source is empty. For more information, see 9.13.6 entry in New functionality.
- Optional warning for possible precision loss. For more information, see 9.13.6 entry in New functionality.
9.13.5
- Support for Postgres bulk load with postgres 13.4 has been added..
- Launch of Connect ETL on Databricks for AWS cloud. Precisely Connect ETL now supports customers who want to leverage the analytics capabilities of Databricks for AWS without recalibrating their ETL pipelines. With this release, Connect ETL customers can move their existing ETL jobs to Databricks easily by running data processing on Databricks under the Intelligent Execution (IX) layer and then moving their current non-Databricks ETL workloads to Databricks clusters.
Fixed Issues
- Multiple issues were fixed. For more information, see the list for Fixed issues for 9.13.5.
9.13.4
- Salesforce API was updated to support version 55 and higher. For non-supported Salesforce platforms, see Platform Lifecycle Information.
- The minimum and recommended supported version is Teradata client bundle (ttu) 16.20. For more information about non-supported Teradata platforms, see Platform Lifecycle Information.
- Support for Aurora for postgres and mysql have been updated. For more information, see Connect ETL online help.
Known Issue
- Known issues were reported. For more information, see the list for Known issues from previous releases.
Fixed Issue
- Multiple issues were fixed. For more information, see the list for Known issues from previous releases.
9.13.2
- Support has been added for Amazon RDS databases. For more information, see Connecting to Amazon RDS in the help.
- Support has been added for Databricks. For more information, see Execution profile file in the help.
- Launch of Connect ETL on Databricks for Azure Cloud. Precisely Connect ETL now supports customers who want to leverage the analytics capabilities of Databricks for Azure Cloud without recalibrating their ETL pipelines. With this release, Connect ETL customers can move their existing ETL jobs to Databricks easily by running data processing on Databricks under the Intelligent Execution (IX) layer and then moving their current non-Databricks ETL workloads to Databricks clusters.
- Precisely Branding. Connect ETL is now rebranded as Precisely.
- Improved integration with Azure Cloud services. Precisely Connect continues to improve integration with the Azure cloud platform. This release provides integration with Azure Key Vault; customers can manage their secrets in Azure multi-tenant environments, and Connect ETL can securely access secrets from the Vault on-the-fly to establish data connections. This release adds support for Azure Active Directory (AD) authentication, enabling Connect ETL jobs to use Azure AD for authentication. Connect ETL now provides direct support for Azure storage which enables customers to read/write to Azure storage from on-prem, hybrid, and on-cloud environments.
- Additional SFTP key exchange support. Connect ETL now supports the following key exchanges for SFTP: diffie-hellman-group14-sha256, diffie-hellman-group16-sha512, and diffie-hellman-group18-sha512. For more information, see 9.13.2 entry in New functionality.
Known Issue
- Known issues were reported. For more information, see the list for Known issues from previous releases.
Fixed Issue
- Multiple issues were fixed. For more information, see the list for Fixed issues for 9.13.x.
9.13.1
- Access Databricks clusters using Azure Active Directory (AD). Precisely Connect ETL now supports Databricks cluster access using Azure AD tokens when deploying jobs from an Azure VM. For more information, see 9.13.1 entry in New functionality.
Known Issue
- Known issues were reported. For more information, see the list for Known issues from previous releases.
Fixed Issue
- Multiple issues were fixed. For more information, see the list for Fixed issues for 9.13.x.
9.13
- Connect ETL Localization. Precisely Connect ETL 9.13 software and documentation are now localized for Japanese customers.
- The documentation support for Connect ETL will no longer be located in the top level directory of the installation. For your documentation needs, refer to the Support Site.
- Lineage REST API will no longer be supported.
Known Issue
- Known issues were reported. For more information, see the list for Known issues from previous releases.
Fixed Issue
- Multiple issues were fixed. For more information, see the list for Fixed issues for 9.13.x.