<?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 Arguments of  ABORT statement in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Arguments-of-ABORT-statement/m-p/249830#M47048</link>
    <description>&lt;P&gt;I was trying to understand the different arguments the ABORT statment. &amp;nbsp;One of many arguments is interger(n). &amp;nbsp;What is the purpose of that number. An example would be helpful to understand.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/lestmtsref/63323/HTML/default/viewer.htm#p0hp2evpgqvfsfn1u223hh9ubv3g.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/lestmtsref/63323/HTML/default/viewer.htm#p0hp2evpgqvfsfn1u223hh9ubv3g.htm&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 12 Feb 2016 21:59:41 GMT</pubDate>
    <dc:creator>SAS_inquisitive</dc:creator>
    <dc:date>2016-02-12T21:59:41Z</dc:date>
    <item>
      <title>Arguments of  ABORT statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Arguments-of-ABORT-statement/m-p/249830#M47048</link>
      <description>&lt;P&gt;I was trying to understand the different arguments the ABORT statment. &amp;nbsp;One of many arguments is interger(n). &amp;nbsp;What is the purpose of that number. An example would be helpful to understand.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/lestmtsref/63323/HTML/default/viewer.htm#p0hp2evpgqvfsfn1u223hh9ubv3g.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/lestmtsref/63323/HTML/default/viewer.htm#p0hp2evpgqvfsfn1u223hh9ubv3g.htm&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Feb 2016 21:59:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Arguments-of-ABORT-statement/m-p/249830#M47048</guid>
      <dc:creator>SAS_inquisitive</dc:creator>
      <dc:date>2016-02-12T21:59:41Z</dc:date>
    </item>
    <item>
      <title>Re: Arguments of  ABORT statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Arguments-of-ABORT-statement/m-p/249841#M47056</link>
      <description>&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/hostunx/61879/HTML/default/viewer.htm#retcod.htm" target="_self"&gt;Determining the Completion Status of a SAS Job in UNIX Environments&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Feb 2016 00:49:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Arguments-of-ABORT-statement/m-p/249841#M47056</guid>
      <dc:creator>mohamed_zaki</dc:creator>
      <dc:date>2016-02-13T00:49:38Z</dc:date>
    </item>
    <item>
      <title>Re: Arguments of  ABORT statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Arguments-of-ABORT-statement/m-p/249842#M47057</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/64404"&gt;@SAS_inquisitive﻿&lt;/a&gt;&amp;nbsp;What does the documentation say about n? And what part is unclear to you. It's worth knowing as the documentation should be accessible and easy to navigate. If it's not, that an issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Feb 2016 01:31:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Arguments-of-ABORT-statement/m-p/249842#M47057</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2016-02-13T01:31:50Z</dc:date>
    </item>
    <item>
      <title>Re: Arguments of  ABORT statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Arguments-of-ABORT-statement/m-p/250083#M47125</link>
      <description>&lt;P&gt;Quite simple. The &amp;lt;n&amp;gt; argument determines the exit condition that is handed back to the operating system once the SAS process has terminated.&lt;/P&gt;
&lt;P&gt;This allows specific failure conditions that you detected during processing being treated correctly by the invoking shell script/batch file/scheduler/whatever.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;eg&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In some cases, we want to specifically detect if a certain table has a given minimum of records, and if not, signal that by passing 4 as the exit code:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data somelib.someset;
infile our_in end=done;
* input statements;
if done and _n_ &amp;lt; &amp;amp;minimum_rec then abort abend 4;
run;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;Now the envoking script (after detecting that SAS exited with code 4) can set a special condition that lets the scheduling software trigger another job that sends an alarm email with the detailed information that not enough data was provided&lt;/P&gt;</description>
      <pubDate>Mon, 15 Feb 2016 12:56:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Arguments-of-ABORT-statement/m-p/250083#M47125</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2016-02-15T12:56:22Z</dc:date>
    </item>
  </channel>
</rss>

