<?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 tDie - Graceful Exit in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/tDie-Graceful-Exit/m-p/2365200#M128831</link>
    <description>&lt;P&gt;In a slightly more ideal world, the tDie component would allow a job to exit early as a result pf the flow logic and by using the Error/Exit Code of 0 would NOT be handled as a job "failure". ie You would set the code to whatever you want and that would be used as the exit status of the job, &amp;nbsp;&amp;gt;0 would be a failure, exist status 0 would be normal/successful completion. However, the way the exception processing is currently implemented prevents this - and more disappointingly also prevents anyone from developing a custom tDie component.&lt;BR /&gt;Could I propose that the generated tDie_x_Error exception handler includes a test for the errorCode and if 0 it does not set the status to "failure"?&lt;BR /&gt;Mark&lt;/P&gt;</description>
    <pubDate>Thu, 06 Apr 2017 09:19:59 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-04-06T09:19:59Z</dc:date>
    <item>
      <title>tDie - Graceful Exit</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tDie-Graceful-Exit/m-p/2365200#M128831</link>
      <description>&lt;P&gt;In a slightly more ideal world, the tDie component would allow a job to exit early as a result pf the flow logic and by using the Error/Exit Code of 0 would NOT be handled as a job "failure". ie You would set the code to whatever you want and that would be used as the exit status of the job, &amp;nbsp;&amp;gt;0 would be a failure, exist status 0 would be normal/successful completion. However, the way the exception processing is currently implemented prevents this - and more disappointingly also prevents anyone from developing a custom tDie component.&lt;BR /&gt;Could I propose that the generated tDie_x_Error exception handler includes a test for the errorCode and if 0 it does not set the status to "failure"?&lt;BR /&gt;Mark&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2017 09:19:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tDie-Graceful-Exit/m-p/2365200#M128831</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-04-06T09:19:59Z</dc:date>
    </item>
    <item>
      <title>Re: tDie - Graceful Exit</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tDie-Graceful-Exit/m-p/2365201#M128832</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;As a workaround, you may have a subjob (or a joblet) dedicated to catch Java exceptions, tDie or tWarn (using tLogCatcher).&lt;BR /&gt;Then, in this subjob you can decide to terminate with a return code equal to 0 using a tJava and "System.exit(0);" based on the condition of your choice.&amp;nbsp;&lt;BR /&gt;Maybe not as clean as you expect but works.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;TRF</description>
      <pubDate>Thu, 06 Apr 2017 09:47:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tDie-Graceful-Exit/m-p/2365201#M128832</guid>
      <dc:creator>TRF</dc:creator>
      <dc:date>2017-04-06T09:47:12Z</dc:date>
    </item>
  </channel>
</rss>

