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

[MilanSuklev]

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?

[shyamkatika]

Hi @john_wang 

Thanks for Response,

please find the updated JCL and diagnostic packages.

Thanks,

Shyam Sundar. 

[john_wang]

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.

[shyamkatika]

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.

[john_wang]

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.