-
Controller Daemon (SQDAEMON):
- When SQDmon is used to request the daemon inventory, the daemon then queries each agent and returns the current agent status. Previously, the inventory command showed the last agent status known to the daemon which resulted in a small increase in CPU overhead each time the inventory command was issued.
-
z/OS Capture and Publisher tasks:
- Support clean shutdown of hot standby capture and publisher tasks on z/OS. A hot standby task can be terminated only by issuing an MVS operator command. Corresponding SQDCONF commands are not supported.
The hot standby task will end with return code 4, reason code CAB_LOCK_CANCELED. No other commands are supported in hot standby mode. For more information, see SQD0004I message.Capture Command DB2 capture and the ZLOG publisher issue MODIFY or F <taskname>,UNMOUNT IMS log capture issue MODIFY or F <taskname>,STOP. You can also issue STOP or P <taskname>. -
Db2/z Capture:
- Issue message WTO to explain DB2 Capture DRSQL_ROW_NOT_FOUND error return code. SQDF048E is an existing Job Log message now also issued as a WTO to explain the obscure DRSQL_ROW_NOT_FOUND error and identify the table that could not be found. For more information, see SQDF048E message.
-
VSAM Log Capture:
- Correct issue with possible CDC data loss where logstream aging window conflicts with long running EXCI programs that issue multiple sync points, where the transaction ID does not change between sync points.
-
Replicator Engine (SQDRPL):
- Fix Avro encoding of TIME column values.
-
Apply (SQDATA and SQDENG) Engines:
- Tolerate COBOL level 66 copybook RENAMES clause on parse.
- Tolerate DB2z DDL keywords associated with temporal tables on parse.
Use length of current record when writing TEXT data to Kafka. When there are multiple record DESCRIPTIONS for a TEXT type Source DATASTORE replicated to Kafka, excess null bytes will no longer be written for shorter records.
-
SQDUTIL Utility:
- Add start and stop stck/bid for sqdutil copy of a z/OS LogStream (zlog) eliminating the need to always copy an entire zlog. Primary use case is to copy a range of zlog records to an extract data set for diagnostic purposes. While Block IDs and STCK (storeclock) values can be used, they cannot be mixed in the same copy statement. The example below uses STCK values. Block IDs must be used with --start-bid and --stop-bid.
//COPY1 EXEC PGM=SQDUTIL,REGION=64M //STEPLIB DD DISP=SHR,DSN=SQDATA.V400.LOADLIB //SQDPARMS DD * copy zlog:///SQDATA.CDC.LOG1 DD:EXTRACT --start-stck=dcb055b0b59a4421 --stop-stck=dcb05646680f7402 /* //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //SQDLOG DD SYSOUT=* //EXTRACT DD DISP=(,CATLG),DSN=SQDATA.CDC.LOG1.EXTRACT, // UNIT=SYSALLDA,SPACE=(TRK,(30,30),RLSE), // DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=0