<?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: DI Studio - How do I force a job to exit? in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/DI-Studio-How-do-I-force-a-job-to-exit/m-p/721215#M19807</link>
    <description>&lt;P&gt;In Status Handling for jobs and transformations there are some default conditions and actions where you could do such things.&lt;/P&gt;
&lt;P&gt;Unfortenately there is no default condtion of a certain table has zero rows,&lt;/P&gt;
&lt;P&gt;So depending on what leads up to you having zero rows, you might be able to use a condition of&amp;nbsp;&lt;SPAN&gt;Data Modified?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Otherwise you could code this fairly easy, perhaps write a macro that check no of obs given your table of interest, and then force the SAS job to quit using ABORT ABEND. Insert the macro either as a post processing for the transformation or the job. Or you could bundle it into a User Writter Transformation to make it visible in the job canvas.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Feb 2021 09:18:52 GMT</pubDate>
    <dc:creator>LinusH</dc:creator>
    <dc:date>2021-02-23T09:18:52Z</dc:date>
    <item>
      <title>DI Studio - How do I force a job to exit?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/DI-Studio-How-do-I-force-a-job-to-exit/m-p/721155#M19806</link>
      <description>&lt;P&gt;Hello - we want to develop code that would force the job to exit based on a certain value in a table.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Basically this is for a validation check - if the count in a table is zero, the job should finish successfully. If the count is &amp;gt; zero - then the job should error out and stop processing.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If there a way to force a job to stop based on this logic? Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2021 01:11:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/DI-Studio-How-do-I-force-a-job-to-exit/m-p/721155#M19806</guid>
      <dc:creator>kjarvis</dc:creator>
      <dc:date>2021-02-23T01:11:11Z</dc:date>
    </item>
    <item>
      <title>Re: DI Studio - How do I force a job to exit?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/DI-Studio-How-do-I-force-a-job-to-exit/m-p/721215#M19807</link>
      <description>&lt;P&gt;In Status Handling for jobs and transformations there are some default conditions and actions where you could do such things.&lt;/P&gt;
&lt;P&gt;Unfortenately there is no default condtion of a certain table has zero rows,&lt;/P&gt;
&lt;P&gt;So depending on what leads up to you having zero rows, you might be able to use a condition of&amp;nbsp;&lt;SPAN&gt;Data Modified?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Otherwise you could code this fairly easy, perhaps write a macro that check no of obs given your table of interest, and then force the SAS job to quit using ABORT ABEND. Insert the macro either as a post processing for the transformation or the job. Or you could bundle it into a User Writter Transformation to make it visible in the job canvas.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2021 09:18:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/DI-Studio-How-do-I-force-a-job-to-exit/m-p/721215#M19807</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2021-02-23T09:18:52Z</dc:date>
    </item>
  </channel>
</rss>

