Connect CDC SQData

Connect CDC SQData already operates transparently on z/OS under IBM's Application Transparent Transport Layer Security (AT-TLS). Under AT-TLS no changes were required to the base code and only port numbers in the configuration need to be changed, as described below. For more information regarding AT-TLS see your z/OS Systems Programmer.

Once IBM's AT-TLS  has been implemented on z/OS the following steps are all that is required by Daemon, Capture and Publisher components and on z/OS only, the SQDATA Apply Engine and SQDUTIL, to be in compliance with TLS:

1.Request the new secure port to be used by the Daemon

2.Request Certificates for MASTER, Daemon and APPLY Engine Tasks

3.Stop all SQDATA tasks

4.Update APPLY Engine source scripts with the new Daemon port. Note, port's are typically implemented using a Parser parameter so script changes may not be required.

5.Update SQDUTIL JCL and/or SQDPARM lib member's, if any with the new Daemon port.

6.Run  Parse Jobs to update the Parsed Apply Engines in the applicable library referenced by Apply Engine Jobs.

7.Update the Daemon tasks with new port

8.If using the z/OS Master Controller, update the SQDPARM Lib members for the MASTER tasks with new Daemon port

9.Start all the SQDATA tasks

Note, there are no changes to connection URL's for clients on z/OS.