<?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: SAS Management Console - type dependency in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Management-Console-type-dependency/m-p/621340#M18110</link>
    <description>&lt;P&gt;I am assuming you have LSF as the scheduler and looking at Flowmanager for the color coding. This is the most common scenario. LSF does not know of a warning condition; it only distinguishes between success (rc=0) and failure (rc&amp;gt;0). This is why many admins decide to reduce a warning completion code (rc=2) to rc=0. Otherwise a warning would potentially stall the progress of a flow. The color yellow in Flowmanager does not indicate a warning but merely the "initializing" or "waiting" state. In that common scenario a warning will&amp;nbsp; implies success. Otherwise it will be interpreted as an error and the job will show up red.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The code to accomplish this is already present in the sasbatch.sh script as comments at the bottom of the file:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;# Add this code to capture exit=1 (SAS warning) and make it exit=0
# Comment out exec line above and uncomment the code below to allow the return code to be captured
#"$SAS_COMMAND" -noxcmd -lrecl 32767 "$@" "${USERMODS_OPTIONS[@]}"
#rc=$?
#if [ $rc -eq 1 ]; then
#  rc=0
#fi
#exit $rc
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;Follow the instruction to turn rc=2 into rc=0.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The difference between "completes successfully" and "ends with any exit code" is what it says: a dependent job will either run only when its predecessor end with rc=0 or will always run when the predecessor ends regardless of its return code.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The condition "Ends with exit code" allows for user defined return codes (using the SAS abort statement) to control specific paths through the flow.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The value for "Runs more than" will trigger a dependent job only when the predecessor runs longer than a specific amount of time. This could help for example when you want to be alerted for unusually long running jobs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SAS and scheduling docs are &lt;A href="https://documentation.sas.com/api/docsets/scheduleug/9.4/content/scheduleug.pdf?locale=en" target="_self"&gt;here&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;LSF is extensively documented in this IBM Knowledge Center &lt;A href="https://www.ibm.com/support/knowledgecenter/en/SSZSHQ_10.2.0/ppm_welcome.html" target="_self"&gt;doc .&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Keep in mind that the LSF software that comes with SAS is somewhat limited compared to the full functionality you would buy from IBM.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;- Jan.&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jan 2020 23:21:57 GMT</pubDate>
    <dc:creator>jklaverstijn</dc:creator>
    <dc:date>2020-01-30T23:21:57Z</dc:date>
    <item>
      <title>SAS Management Console - type dependency</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Management-Console-type-dependency/m-p/621104#M18109</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On SAS Management Console, regarding&amp;nbsp; how to setting event type dependency between jobs .&lt;/P&gt;&lt;P&gt;Does anyone please&amp;nbsp; know if&amp;nbsp; the condition “ Completes Successfully “accept Warnings( yellow msg) when is running jobs or it must be run with any warnings ( warning are not&amp;nbsp; red errors are just warnings like to delete a table that do not exist will cause a warning msg not an error msg) while running the code.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also does anyone know what is the difference between the condition “ Completes Successfully” and “ Ends with any exit code” ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example some conditions, such as &lt;STRONG&gt;Ends with exit code&lt;/STRONG&gt; and &lt;STRONG&gt;Runs more than&lt;/STRONG&gt;, require you to specify additional values (such as the exit code or the number of minutes that the job runs. )&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additionally&amp;nbsp; where I can find a detailed description about all the event types &amp;nbsp;conditions?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks in advance.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2020 10:46:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Management-Console-type-dependency/m-p/621104#M18109</guid>
      <dc:creator>jorquec</dc:creator>
      <dc:date>2020-01-30T10:46:11Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Management Console - type dependency</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Management-Console-type-dependency/m-p/621340#M18110</link>
      <description>&lt;P&gt;I am assuming you have LSF as the scheduler and looking at Flowmanager for the color coding. This is the most common scenario. LSF does not know of a warning condition; it only distinguishes between success (rc=0) and failure (rc&amp;gt;0). This is why many admins decide to reduce a warning completion code (rc=2) to rc=0. Otherwise a warning would potentially stall the progress of a flow. The color yellow in Flowmanager does not indicate a warning but merely the "initializing" or "waiting" state. In that common scenario a warning will&amp;nbsp; implies success. Otherwise it will be interpreted as an error and the job will show up red.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The code to accomplish this is already present in the sasbatch.sh script as comments at the bottom of the file:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;# Add this code to capture exit=1 (SAS warning) and make it exit=0
# Comment out exec line above and uncomment the code below to allow the return code to be captured
#"$SAS_COMMAND" -noxcmd -lrecl 32767 "$@" "${USERMODS_OPTIONS[@]}"
#rc=$?
#if [ $rc -eq 1 ]; then
#  rc=0
#fi
#exit $rc
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;Follow the instruction to turn rc=2 into rc=0.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The difference between "completes successfully" and "ends with any exit code" is what it says: a dependent job will either run only when its predecessor end with rc=0 or will always run when the predecessor ends regardless of its return code.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The condition "Ends with exit code" allows for user defined return codes (using the SAS abort statement) to control specific paths through the flow.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The value for "Runs more than" will trigger a dependent job only when the predecessor runs longer than a specific amount of time. This could help for example when you want to be alerted for unusually long running jobs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SAS and scheduling docs are &lt;A href="https://documentation.sas.com/api/docsets/scheduleug/9.4/content/scheduleug.pdf?locale=en" target="_self"&gt;here&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;LSF is extensively documented in this IBM Knowledge Center &lt;A href="https://www.ibm.com/support/knowledgecenter/en/SSZSHQ_10.2.0/ppm_welcome.html" target="_self"&gt;doc .&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Keep in mind that the LSF software that comes with SAS is somewhat limited compared to the full functionality you would buy from IBM.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;- Jan.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2020 23:21:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Management-Console-type-dependency/m-p/621340#M18110</guid>
      <dc:creator>jklaverstijn</dc:creator>
      <dc:date>2020-01-30T23:21:57Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Management Console - type dependency</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Management-Console-type-dependency/m-p/621478#M18113</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thanks for your email , but I am not a sas expert so I didn't understant anything.&lt;/P&gt;&lt;P&gt;I copy an image from DIStudio where my jobs are previous saved to be deployed on SAS Managment Console.&lt;/P&gt;&lt;P&gt;On DI Studio when I manually run a job I can see these messages of Completed Successfully despite a warning , so my doubt is this in Management Console will be consider as Completed Successfully or not&amp;nbsp;?&lt;/P&gt;&lt;P&gt;Many thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sas warning.JPG" style="width: 600px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/35785iB0E7A3830979AA36/image-size/large?v=v2&amp;amp;px=999" role="button" title="sas warning.JPG" alt="sas warning.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jan 2020 16:27:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Management-Console-type-dependency/m-p/621478#M18113</guid>
      <dc:creator>jorquec</dc:creator>
      <dc:date>2020-01-31T16:27:51Z</dc:date>
    </item>
  </channel>
</rss>

