Some of the common errors and their resolution - Connect_CDC - connect_cdc_mimix_share - aws_mainframe_modernization_service - 6.x

Connect CDC Getting Started Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
6.x
ft:locale
en-US
Product name
Connect CDC
ft:title
Connect CDC Getting Started Guide
Copyright
2025
First publish date
2003
ft:lastEdition
2026-02-25
ft:lastPublication
2026-02-25T19:01:02.274000
L1_Product_Gateway
Integrate
L2_Product_Segment
Data Integration
L3_Product_Brand
Precisely Connect
L4_Investment_Segment
Application Data Integration
L5_Product_Group
ADI - Connect
L6_Product_Name
Connect CDC

The following is the list of some of the errors you may encounter when setting up the SSL connections.

Error

Resolution

DDM TCP/IP Secure Sockets error occurred on SSL_Handshake() -- Reason Code -16

Ensure the certificate exists on the server and that it’s assigned to the i5/OS DDM/DRDA Server - TCP/IP application.

DDM TCP/IP Secure Sockets error occurred on SSL_Handshake() -- Reason Code -23

Ensure the certificate exists on the client and that it’s assigned to the i5/OS DDM/DRDA Server - TCP/IP application.

DDM TCP/IP Secure Sockets error occurred on SSL_Handshake() -- Error code 3447

Ensure the RDB directory entry for the server system has port number 448 (the default DDM/DRDA SSL port) specified.

FTP - when using FTP to transfer certificates, use ASCII mode and not binary (bin) mode.

java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath:

Ensure the javax.net.ssl.trustStore property is specified and pointing to the correct cacerts file.