<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Consumer task with full load and CDC sourcing from logstream in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Consumer-task-with-full-load-and-CDC-sourcing-from-logstream/m-p/2548697#M16273</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;SPAN&gt;Pranathi,&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/151916"&gt;@unay&lt;/a&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;In this scenario, the Full Load data is read directly from IBM DB2 for z/OS and replicated to the target, rather than flowing through LogStream. That is why you still see connections to Db2 z/OS during the Full Load phase.&lt;/P&gt;
&lt;P&gt;By the way, even during the Change Processing phase, Replicate still maintains connections to Db2 z/OS, as these connections are used for metadata retrieval, DDL change monitoring, and other control operations.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hope this helps.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;John.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 07 May 2026 22:44:36 GMT</pubDate>
    <dc:creator>john_wang</dc:creator>
    <dc:date>2026-05-07T22:44:36Z</dc:date>
    <item>
      <title>Consumer task with full load and CDC sourcing from logstream</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Consumer-task-with-full-load-and-CDC-sourcing-from-logstream/m-p/2548691#M16270</link>
      <description>&lt;P&gt;Hello Qlik community,&lt;/P&gt;&lt;P&gt;We have a user who does full load sourcing from Logstream task. Logstream task is sourcing from DB2 zo/s and they have 1 week of data retention.&lt;/P&gt;&lt;P&gt;We see consumer task is sourcing from Logstream explicity while it also has feature to enter Db2 zo/s credentials and the users entered those and the test connectton was successful.&lt;/P&gt;&lt;P&gt;Question : How is full load done here. Is it sourced from DB2 zo/s or sourced from the Logstream task (staging area).&lt;/P&gt;&lt;P&gt;Please advise !&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Pranathi&lt;/P&gt;</description>
      <pubDate>Thu, 07 May 2026 19:39:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Consumer-task-with-full-load-and-CDC-sourcing-from-logstream/m-p/2548691#M16270</guid>
      <dc:creator>unay</dc:creator>
      <dc:date>2026-05-07T19:39:39Z</dc:date>
    </item>
    <item>
      <title>Re: Consumer task with full load and CDC sourcing from logstream</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Consumer-task-with-full-load-and-CDC-sourcing-from-logstream/m-p/2548697#M16273</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;SPAN&gt;Pranathi,&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/151916"&gt;@unay&lt;/a&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;In this scenario, the Full Load data is read directly from IBM DB2 for z/OS and replicated to the target, rather than flowing through LogStream. That is why you still see connections to Db2 z/OS during the Full Load phase.&lt;/P&gt;
&lt;P&gt;By the way, even during the Change Processing phase, Replicate still maintains connections to Db2 z/OS, as these connections are used for metadata retrieval, DDL change monitoring, and other control operations.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hope this helps.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;John.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 07 May 2026 22:44:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Consumer-task-with-full-load-and-CDC-sourcing-from-logstream/m-p/2548697#M16273</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2026-05-07T22:44:36Z</dc:date>
    </item>
  </channel>
</rss>

