<?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: how to run sas job on a Unix server in cascade in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-run-sas-job-on-a-Unix-server-in-cascade/m-p/933342#M44893</link>
    <description>&lt;P&gt;If you want to make sure the jobs run in succession, do not run them in the background (that's what the &amp;amp; does).&lt;/P&gt;
&lt;P&gt;To run the jobs in succession in the background, put them into a shell script (without the nohup and &amp;amp;), and run the script with nohup and &amp;amp;.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Jun 2024 15:39:03 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2024-06-21T15:39:03Z</dc:date>
    <item>
      <title>how to run sas job on a Unix server in cascade</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-run-sas-job-on-a-Unix-server-in-cascade/m-p/933326#M44891</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have many sas programs that I need to execute on a unix server by sending the following command directly to the terminal windows (winscp)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;nohup sas -sysparm '20230315#' /dwh_actuariat/.../HYFI_INTExpSF.sas &amp;amp;&lt;/DIV&gt;
&lt;DIV&gt;nohup sas -sysparm '20230415#' /dwh_actuariat/.../HYFI_INTExpSF.sas &amp;amp;&lt;/DIV&gt;
&lt;DIV&gt;nohup sas -sysparm '20230515#' /dwh_actuariat/.../HYFI_INTExpSF.sas &amp;amp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I could also put those instructions into a ksh file and just execute the ksh file.&lt;/DIV&gt;
&lt;DIV&gt;But I wonder how to make sure that the first job is completed before starting the second one. Same thing for the last job, how to make sure that the second job is completed before starting the last one.&lt;/DIV&gt;</description>
      <pubDate>Fri, 21 Jun 2024 14:22:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-run-sas-job-on-a-Unix-server-in-cascade/m-p/933326#M44891</guid>
      <dc:creator>alepage</dc:creator>
      <dc:date>2024-06-21T14:22:54Z</dc:date>
    </item>
    <item>
      <title>Re: how to run sas job on a Unix server in cascade</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-run-sas-job-on-a-Unix-server-in-cascade/m-p/933334#M44892</link>
      <description>&lt;P&gt;Remove the &amp;amp;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the list is large it might be easier with two files.&amp;nbsp; One with the list of programs to run:&lt;/P&gt;
&lt;PRE&gt;sas -sysparm '20230315#' -log 20230315.log /dwh_actuariat/.../HYFI_INTExpSF.sas
sas -sysparm '20230415#' -log 20230415.log /dwh_actuariat/.../HYFI_INTExpSF.sas 
sas -sysparm '20230515#' -log 20230515.log /dwh_actuariat/.../HYFI_INTExpSF.sas &lt;/PRE&gt;
&lt;P&gt;Then a second one that calls that file which could then use nohup to allow it to complete even if the shell that launched it is closed.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 14:54:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-run-sas-job-on-a-Unix-server-in-cascade/m-p/933334#M44892</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2024-06-21T14:54:27Z</dc:date>
    </item>
    <item>
      <title>Re: how to run sas job on a Unix server in cascade</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-run-sas-job-on-a-Unix-server-in-cascade/m-p/933342#M44893</link>
      <description>&lt;P&gt;If you want to make sure the jobs run in succession, do not run them in the background (that's what the &amp;amp; does).&lt;/P&gt;
&lt;P&gt;To run the jobs in succession in the background, put them into a shell script (without the nohup and &amp;amp;), and run the script with nohup and &amp;amp;.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 15:39:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/how-to-run-sas-job-on-a-Unix-server-in-cascade/m-p/933342#M44893</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2024-06-21T15:39:03Z</dc:date>
    </item>
  </channel>
</rss>

