<?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>article Qlik Replicate: DB2 z/OS R4Z  [SOURCE_CAPTURE ]W: R4DB2: ALL CB ENTRIES ARE IN USE in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-DB2-z-OS-R4Z-SOURCE-CAPTURE-W-R4DB2-ALL-CB/ta-p/2052148</link>
    <description>&lt;P&gt;A Qlik Replicate DB2 z/OS task may stop/fail with the following message:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;[SOURCE_CAPTURE ]W: R4DB2: ALL CB ENTRIES ARE IN USE&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;This means that a task is trying to start, but the maximum number of R4Z Control Blocks (in the&amp;nbsp; R4Z CDC service environment on the mainframe) is in use. The task will not be able to start unless the MAXSESSIONS setting is increased to allow more than 32 R4Z sessions to start. One temporary solution is to stop some other tasks that are unnecessary to have running at the moment.&amp;nbsp; Another possible long-term solution is to implement&amp;nbsp; LOGSTREAM tasks to reduce the number of sessions being created on the mainframe.&amp;nbsp; Below are the steps to resolve this issue by increasing the total number of sessions.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;All versions of Qlik Replicate using R4Z&lt;BR /&gt;UDTF:&amp;nbsp; &amp;nbsp; &amp;nbsp;'XXX.your_R4Z_UDTF__CDC1'&amp;nbsp; &amp;nbsp; &amp;lt;&amp;lt;&amp;lt;&amp;nbsp; &amp;nbsp;Your&amp;nbsp; UDTF's CDC server environemnt CDC1, CDC2, DB2T, DB2P as examples.&lt;BR /&gt;APPLENV:&amp;nbsp; &amp;nbsp; &amp;nbsp;'XXX.your_R4Z_APPLENVF__CDC1'&amp;nbsp; &amp;nbsp; &amp;lt;&amp;lt;&amp;lt;&amp;nbsp; &amp;nbsp;Your&amp;nbsp; APPLENV 's CDC server environment CDC1, CDC2, DB2T, DB2P as examples.&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI&gt;Stop ALL GUI Qlik Replicate DB2 z/OS&amp;nbsp; ONLY tasks&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Wait for the tasks to finish Stopping.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Run/Submit the XMDUMP Job from the&amp;nbsp; .INSTALL library. This is a simple reporting job that shows how many sessions are in use and how many are available. &lt;BR /&gt;&lt;BR /&gt;Don't forget to edit the CDCSERV parm = CDC1 or DB2P or whatever your 4 characters are for the CDC service.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;/V WLM,applenv=xxxxxx,Quiesce&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;This quiesces the application environment associated with the corresponding UDTF and CDC Service, for example, R4Z_MYAPPLENV__CDC1 or R4Z_MYAPPLENV__DB2P)&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Run the XMTERMIN Job from the&amp;nbsp;.INSTALL library and expect a return Code: RC=0 The job terminates the CDC service environment ( for example CDC1 or DB2P for Prod) and releases the ECSA memory allocation. &lt;BR /&gt;&lt;BR /&gt;Don't forget to edit the CDCSERV parm = CDC1 or DB2P or whatever your 4 characters are for the CDC service.&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Run the XMDUMP Job again, from the .INSTALL library and&amp;nbsp; expect a return Code: RC=1 = NON-EXISTENT&lt;BR /&gt;&lt;BR /&gt;This verifies that the CDC service environment is truly gone and memory is freed up.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Edit the .CONFIG file members:&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;Change all members that contain the MAXSESSIONS setting and increase it by 5 or 10, for example.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Save the .CONFIG file members&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&amp;nbsp;/V WLM,applenv=xxxx,RESUME&lt;BR /&gt;&lt;BR /&gt;This resumes the application environment associated with the corresponding UDTF and CDC Service, for example, R4Z_MYAPPLENV__CDC1 or R4Z_MYAPPLENV__DB2P.&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Resume the Qlik Replicate DB2 z/OS&amp;nbsp;tasks from the Qlik Replicate console.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Related Content&lt;/STRONG&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://help.qlik.com/en-US/replicate/Content/Global_Common/Content/SharedReplicateHDD/R4Z_Install_Config/controlling-r4z-on-zos.htm" target="_blank" rel="noopener"&gt;Controlling the CDC process | Qlik Help&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Mar 2023 08:56:25 GMT</pubDate>
    <dc:creator>Barb_Fill21</dc:creator>
    <dc:date>2023-03-23T08:56:25Z</dc:date>
    <item>
      <title>Qlik Replicate: DB2 z/OS R4Z  [SOURCE_CAPTURE ]W: R4DB2: ALL CB ENTRIES ARE IN USE</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-DB2-z-OS-R4Z-SOURCE-CAPTURE-W-R4DB2-ALL-CB/ta-p/2052148</link>
      <description>&lt;P&gt;A Qlik Replicate DB2 z/OS task may stop/fail with the following message:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;[SOURCE_CAPTURE ]W: R4DB2: ALL CB ENTRIES ARE IN USE&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;This means that a task is trying to start, but the maximum number of R4Z Control Blocks (in the&amp;nbsp; R4Z CDC service environment on the mainframe) is in use. The task will not be able to start unless the MAXSESSIONS setting is increased to allow more than 32 R4Z sessions to start. One temporary solution is to stop some other tasks that are unnecessary to have running at the moment.&amp;nbsp; Another possible long-term solution is to implement&amp;nbsp; LOGSTREAM tasks to reduce the number of sessions being created on the mainframe.&amp;nbsp; Below are the steps to resolve this issue by increasing the total number of sessions.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;All versions of Qlik Replicate using R4Z&lt;BR /&gt;UDTF:&amp;nbsp; &amp;nbsp; &amp;nbsp;'XXX.your_R4Z_UDTF__CDC1'&amp;nbsp; &amp;nbsp; &amp;lt;&amp;lt;&amp;lt;&amp;nbsp; &amp;nbsp;Your&amp;nbsp; UDTF's CDC server environemnt CDC1, CDC2, DB2T, DB2P as examples.&lt;BR /&gt;APPLENV:&amp;nbsp; &amp;nbsp; &amp;nbsp;'XXX.your_R4Z_APPLENVF__CDC1'&amp;nbsp; &amp;nbsp; &amp;lt;&amp;lt;&amp;lt;&amp;nbsp; &amp;nbsp;Your&amp;nbsp; APPLENV 's CDC server environment CDC1, CDC2, DB2T, DB2P as examples.&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI&gt;Stop ALL GUI Qlik Replicate DB2 z/OS&amp;nbsp; ONLY tasks&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Wait for the tasks to finish Stopping.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Run/Submit the XMDUMP Job from the&amp;nbsp; .INSTALL library. This is a simple reporting job that shows how many sessions are in use and how many are available. &lt;BR /&gt;&lt;BR /&gt;Don't forget to edit the CDCSERV parm = CDC1 or DB2P or whatever your 4 characters are for the CDC service.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;/V WLM,applenv=xxxxxx,Quiesce&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;This quiesces the application environment associated with the corresponding UDTF and CDC Service, for example, R4Z_MYAPPLENV__CDC1 or R4Z_MYAPPLENV__DB2P)&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Run the XMTERMIN Job from the&amp;nbsp;.INSTALL library and expect a return Code: RC=0 The job terminates the CDC service environment ( for example CDC1 or DB2P for Prod) and releases the ECSA memory allocation. &lt;BR /&gt;&lt;BR /&gt;Don't forget to edit the CDCSERV parm = CDC1 or DB2P or whatever your 4 characters are for the CDC service.&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Run the XMDUMP Job again, from the .INSTALL library and&amp;nbsp; expect a return Code: RC=1 = NON-EXISTENT&lt;BR /&gt;&lt;BR /&gt;This verifies that the CDC service environment is truly gone and memory is freed up.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Edit the .CONFIG file members:&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;Change all members that contain the MAXSESSIONS setting and increase it by 5 or 10, for example.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Save the .CONFIG file members&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&amp;nbsp;/V WLM,applenv=xxxx,RESUME&lt;BR /&gt;&lt;BR /&gt;This resumes the application environment associated with the corresponding UDTF and CDC Service, for example, R4Z_MYAPPLENV__CDC1 or R4Z_MYAPPLENV__DB2P.&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;Resume the Qlik Replicate DB2 z/OS&amp;nbsp;tasks from the Qlik Replicate console.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Related Content&lt;/STRONG&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://help.qlik.com/en-US/replicate/Content/Global_Common/Content/SharedReplicateHDD/R4Z_Install_Config/controlling-r4z-on-zos.htm" target="_blank" rel="noopener"&gt;Controlling the CDC process | Qlik Help&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 08:56:25 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-DB2-z-OS-R4Z-SOURCE-CAPTURE-W-R4DB2-ALL-CB/ta-p/2052148</guid>
      <dc:creator>Barb_Fill21</dc:creator>
      <dc:date>2023-03-23T08:56:25Z</dc:date>
    </item>
  </channel>
</rss>

