What's New
- Filter IFI calls
-
During normal capture operation, the Db2z capture program SQDDB2C now reads Db2 log records only for tables that are defined as a source. This reduces processing overhead and eliminates locks on non-source tables.
Source table log filtering is not active during the initial capture pre-scan startup phase, so some brief locking on non-source tables may still be observed during this period.
To disable source table filtering and restore the former processing of log records for all Db2 tables, add command line argument --no-ifi-filter to the SQDPARMS DD input.
-
Improvements
- DB2z Dynamic Refresh has been improved to specify the index column sort order, ASCENDING or DESCENDING, in the SELECT statement ORDER BY clause generated for an SQDCONF refresh command.
- Improved the clarity and reliability of the
--indexoption in the SQDCONF refresh command, ensuring predictable index selection and reducing unexpected refresh failures. - Improved handling of primary key changes for Kafka targets: sqdata now sends a DELETE for the old key and an INSERT for the new key instead of an UPDATE, ensuring correct behavior and reliable processing in multi‑partition environments.Note: This behavior applies only to Kafka JSON targets.
Fixed Issues
- z/OS Health Checker:
- Fixed an issue where the Health Checker returned RC=8 even though the capture was running normally.
- SQDCONF Utility:
- Fixed an issue where SQDCONF returned RC=00 even when the user lacked authorization to execute the program.
- Fixed an issue where canceling a refresh did not always clean up associated log entries and temporary files.
- z/OS Capture and Publisher tasks:
- Fixed an issue where the DB2 Capture Publisher Detail screen in the SQData ISPF Utility displayed the Safe Restart point instead of the Safe Remine point.
- Fixed an issue to prevent incorrect type handling that could cause the wrong length to be selected for variable-length data, leading to malformed values and an abend in the Db2z Capture/Publisher(SQDDB2C).
- Fixed an issue in the Db2z target drivers where replication could terminate after a reconnect if unexpected metadata was received. This occurred when TLS renegotiation caused the engine to receive initial metadata instead of a metadata refresh, leading to an assertion failure.
- Controller Daemon (SQDAEMON):
- The SQDAEMON informational connection messages SQDC060I and SQDC061I are suppressed by default on z/OS. They are issued as WTO messages on z/OS, and as syslog messages on other platforms where they were already being suppressed by default.
SQDC061I Accepted incoming connection for v_ab@VDI-US01-3-009 with acl:0x4e SQDC060I Accepted incoming connection for guest as v_ab@VDI-US01-3-009 with acl:0x4eTo enable these WTO messages on the SQDAEMON joblog, you can set
message_level=6in the daemon's acl.cfg file, or specify --syslog-level=6 in the SQDPARMS input data set.
- Apply Engine (SQDENG/SQDATA) and Parser:
- Fixed an issue where Kafka
tableandtable_keyoptions used with the APPLY command did not produce the expected keying behavior. - Fixed an issue where the monitoring display showed record totals that did not match the detailed breakdown of processed records.
- Fixed an issue where Kafka
- Apply Engine (SQDENG/SQDATA), Parser, and Replicator (SQDRPL):
- Fixed an issue where the COBOL parser rejected valid PICTURE clauses that used lowercase symbols.
- Fixed an issue where the Apply Engine and Replicator Engine could fail when using a CDC file as the source that contains extended rrecon (reconciliation) data, and the engine scripts specify the optional
RRECON_UUIDandRRECONfile parameters. - Resolved an issue that improved
TLSrenegotiation handling to prevent data corruption during encrypted transmissions.TLSrehandshakes are now coordinated to occur only after active records or transactions complete, ensuring reliable and correctly formatted data delivery.
- Replicator (SQDRPL):
- Improved handling of incompatible schema changes using
RPLMAP_IGNORE_INCOMPATIBLE_SCHEMA. This enhancement eliminates the need to restart the Replicator Engine and reports incompatible DDL changes through theSQDRP07Wwarning message. - Replicator stopped trimming trailing blanks from source character data even when STRIP TRAILING SPACES was provided in OPTIONS statement in replicator script. This fix restores that behavior for the Replicator by correctly propagate the training flag.
- Improved handling of incompatible schema changes using
- z/OS CDCzLog Publisher (SQDZLOGC):
- SQDLOG option parsing was improved so the final OPTIONS= value is recognized without a trailing comma.
- Support for writing RRECON data has been added to the Db2 z Publisher. For more information, see Source and Target Reconciliation Overview.