Which connector?: DB2z/os

Additional details:

We believe the following information is available on HVR but missing from HVA, however we don't have access to a trial version of HVR to verify. The ColumnProperties we need are hvr_cap_tstamp, hvr_cap_user and hvr_tx_seq fields.

Please expose the source log-record timestamp and primary authorization ID for each replicated change, and pass this metadata through to a Kafka destination as part of each change event.

Each change event delivered to Kafka should include:

- **Log-record timestamp:** Both the raw `LRHTIME` value in hex and its decoded UTC timestamp, with **at least millisecond precision**.
- **Primary authorization ID:** The authorization ID associated with the change’s unit of recovery.
- **Unit of recovery ID (URID):** To correlate changes within the same transaction.
- **Log record type and subtype:** To identify the source record.

The implementation guidance we have for obtaining this metadata through `IFI READS IFCID 0306` is:

- Read `LRHTIME` from the log record header.
- Obtain the primary authorization ID from the transaction’s `Begin_UR` record and associate it with changes using `URID`. Undo/Redo change records do not contain this ID themselves.
- Use `WQALLCRI=X'00'` to include both change records and unit-of-recovery control records, and maintain a `URID → authorization ID` mapping.
- Detect whether the log uses the 6-byte or 10-byte format before decoding. Interpret `LRHTIME` according to the environment: STCK in non-data-sharing environments, or LRSN plus member ID in data-sharing environments. Identify the interpretation used in the event metadata.