topic Re: DB2 z/OS can LOAD LOG(YES) be replicated in Qlik Replicate

DB2 z/OS can LOAD LOG(YES) be replicated

MilanSuklev — Mon, 16 Feb 2026 07:31:03 GMT

Hello

I have a DB2 z/OS source table, that is maintained by a LOAD job. There are multiple Steps in the Job. First it does a LOAD REPLACE and after that there are several LOAD RESUME steps. None of this is by default captured by the Log Stream task that is reading the source.

However these changes should be visible to Qlik Replicate. My expectation would be to have a reload of the table triggered after the LOAD REPLACE finished and the LOAD RESUME could be handled as mass inserts.

Is there any possibility to achieve this?

Re: DB2 z/OS can LOAD LOG(YES) be replicated

DesmondWOO — Mon, 16 Feb 2026 08:35:45 GMT

Hi @MilanSuklev ,

Yes, Qlik Replicate can detect these actions. By default, the affected table will be suspended. More details are available in the documentation under “Handling actions resulting in subtype 83.”

If you have suggestions or ideas for improving this behavior, please submit them through the Qlik Ideation.

Regards,
Desmond

Re: DB2 z/OS can LOAD LOG(YES) be replicated

MilanSuklev — Mon, 16 Feb 2026 13:53:11 GMT

Hi @DesmondWOO

Thank you for your answer. Just for the record I am still using qlik replicate 2024.11 but the documentation seems to be the same.

Actually I do not see the Warning in my log even though I saw that a LOAD did run on DB2 side. While I checked I saw that I have the set the internal parameter for the DB2 Endpoint to ifi306LogParsing=ERRORS and ifi306MessageLevel=1. I assume this skips these warning messages in my log. Do I have to chnage these parameters to get the Logs?

Best

Milan

Re: DB2 z/OS can LOAD LOG(YES) be replicated

DesmondWOO — Tue, 17 Feb 2026 09:26:29 GMT

Hi @MilanSuklev ,

Please enable verbose level on SOURCE_CAPTURE and set ifi306LogParsing=ALWAYS. Be sure to revert the setting immediately after completing the test.

Regards,
Desmond

Re: DB2 z/OS can LOAD LOG(YES) be replicated

shyamkatika — Wed, 18 Feb 2026 07:32:14 GMT

Hi Team,

In our Production system, we are currently facing this scenario where LOAD RESUME YES and LOAD RESUME REPLACE activities are scheduled and executed from the source side for almost all tables on a daily basis. Since these utilities are happening every day at the source level, as per the current default behavior (IGNORE), this could potentially lead to data gaps unless a table reload is performed after each occurrence.

Given this, we would like to clarify:
1.Since these utilities are executed daily from source, does it mean we are potentially losing data every day unless manual reload is performed?
2.From an operational standpoint, performing daily reloads for multiple production tables is not feasible.
3.Is there any alternative recommended approach to handle frequent LOAD RESUME / REPLACE activities other than monitoring + reload?
4.If we enable the internal parameter db2LoadOption = SUSPEND, we understand it will only help in alerting (via table suspension), but it will not automatically capture missed data, and reload will still be required. Please confirm.

5. If we suspend this table, we need to perform resume or advance resume from the suspend timestamp. Can we get those LOAD RESUME and LOAD REPLACE records. If not what we need to do for avoide this data missing

Re: DB2 z/OS can LOAD LOG(YES) be replicated

DesmondWOO — Fri, 20 Feb 2026 09:42:15 GMT

Hi @shyamkatika ,

From my understanding, both LOAD REPLACE and LOAD RESUME insert data without generating standard DML log records for each row. These bulk load operations bypass normal transactional logging, which means Qlik Replicate cannot capture them as incremental changes. That is why Qlik Replicate issues a warning and, by default, suspends the affected table. After such a load, a full refresh of the target is typically required before CDC can resume capturing ongoing changes.

Regards,
Desmond

Re: DB2 z/OS can LOAD LOG(YES) be replicated

shyamkatika — Tue, 10 Mar 2026 07:12:55 GMT

Hi @DesmondWOO

We have validated LOAD RESUME and LOAD REPLACE in our lower environment. During our testing, we observed that we are not able to capture the data in the target Snowflake.

1. As per our validation for the LOD RESUME based on the below Qlik documentation and observed the following behavior.
Handling actions resulting in subtype 83 | Qlik Replicate Help

When using SHARELEVEL CHANGE with LOG YES+LOAD RESUME, the changes are being captured successfully by Replicate.
LOAD RESUME + SHARELEVEL CHANGE + LOG YES → Changes captured in Target

For the LOAD REPLACE based on the below Qlik article
Does the DB2 Native Endpoint capture changes when ... - Qlik Community - 1730439
Alternative for LOAD REPLACE → TRUNCATE + LOAD RESUME + SHARELEVEL CHANGE + LOG YES → Changes captured in Target

Could you please validate this behavior and confirm whether this approach is fully supported to use in Production? We would like to ensure there are no downstream risks or inconsistencies if we adopt this as the standard process.

Re: DB2 z/OS can LOAD LOG(YES) be replicated

john_wang — Wed, 11 Mar 2026 09:00:51 GMT

Hello @shyamkatika , copy @DesmondWOO

When using SHARELEVEL CHANGE with LOG YES+LOAD RESUME, the changes are being captured successfully by Replicate.
LOAD RESUME + SHARELEVEL CHANGE + LOG YES → Changes captured in Target

You are correct — this is expected behavior and is documented in the User Guide (see: All variations except SHRLEVEL CHANGE).
When SHRLEVEL CHANGE is used together with LOG YES and LOAD RESUME, the LOAD utility records the loaded rows in the log as INSERT operations. As a result, Qlik Replicate captures these changes and applies them to the target.

Please note:
We assume that the data loaded using the LOAD utility does not conflict with the existing data. If there are conflicts between the loaded data and the existing data, such as primary key violations, that would be a separate topic.

Hope this helps.

John.

Re: DB2 z/OS can LOAD LOG(YES) be replicated

shyamkatika — Wed, 11 Mar 2026 12:31:35 GMT

Hi @john_wang , @DesmondWOO

Thanks @john_wang

Same way for LOAD REPLACE

As per below Support article

https://community.qlik.com/t5/Official-Support-Articles/Does-the-DB2-Native-Endpoint-capture-changes-when-loading-data/ta-p/1730439

For LOAD REPLACE:

TRUNCATE + LOAD RESUME + SHARELEVEL CHANGE + LOG YES → Changes captured in Target

Could you please validate this behavior and confirm whether this approach is fully supported to use in Production? We would like to ensure there are no downstream risks or inconsistencies if we adopt this as the standard process.

Thanks,

Shyam Sundar.

Re: DB2 z/OS can LOAD LOG(YES) be replicated

john_wang — Fri, 13 Mar 2026 02:45:57 GMT

Hello Shyam Sundar, @shyamkatika

Could you please share the JCL sample so we can confirm the behavior on our side?

thanks,

John.

Re: DB2 z/OS can LOAD LOG(YES) be replicated

shyamkatika — Fri, 13 Mar 2026 14:12:40 GMT

Hi @john_wang

Thanks for Response,

please find the updated JCL and diagnostic packages.

Thanks,

Shyam Sundar.

Re: DB2 z/OS can LOAD LOG(YES) be replicated

john_wang — Mon, 16 Mar 2026 08:10:38 GMT

Hello Shyam Sundar, @shyamkatika

To avoid any potential information leakage, please do not upload Diagnostics Packages to the community in the future, as the content is publicly accessible to all visitors. I have removed the attachments as soon as I noticed them at that day.

Thank you for providing the JCL. It appears to be the same as the samples I have here. We have also confirmed that the user guide is correct: for LOAD REPLACE (all variations), a warning message will be generated.

In short, LOAD REPLACE + LOG YES is not equivalent to TRUNCATE + LOAD RESUME + SHARELEVEL CHANGE + LOG YES. This behavior is by design in IBM Db2 for z/OS.

thanks,
John.

Re: DB2 z/OS can LOAD LOG(YES) be replicated

shyamkatika — Mon, 16 Mar 2026 15:30:28 GMT

Hi @john_wang

Thank you for the clarification. Yes, that is correct — from the source side, With using LOAD REPLACE, if we first perform a TRUNCATE and then load the new data using LOAD RESUME + SHARELEVEL CHANGE + LOG YES, the changes should be properly logged.

With this approach, we expect the changes to be captured through CDC. Could you please validate this approach from your side?

Thanks,

Shyam Sundar.

Re: DB2 z/OS can LOAD LOG(YES) be replicated

john_wang — Tue, 17 Mar 2026 01:19:29 GMT

Hello Shyam Sundar, @shyamkatika

If the TRUNCATE and the LOAD RESUME + SHARELEVEL CHANGE + LOG YES are executed as two separate operations (rather than a single LOAD REPLACE), then it can be captured by Qlik Replicate. This behavior occurs because IBM Db2 records the changes in the transaction log in this manner.

If you need further assistance, please feel free to open a support ticket. Our support team will be happy to help you.

thanks,
John.