<?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: running sas in a terminal window of winscp in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/running-sas-in-a-terminal-window-of-winscp/m-p/767888#M39538</link>
    <description>&lt;P&gt;In my experience a shell terminal to a Linux OS can close after a time, either due to firewall timeout or (with us working from home) a temporary network disconnect.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The best approach is to run any long-running process asynchronously so it is not interrupted when the shell window disconnects. Use the &amp;amp; terminator on the command, which returns control immediately back to the shell.&amp;nbsp; Example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="shell"&gt;/usr/local/bin/sas mysasbatch.sas -log ./logs/mysasbatch.log &amp;amp;&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When you return to find the shell disconnected, simple "shell in" again and check the contents of the SAS log.&lt;/P&gt;</description>
    <pubDate>Wed, 15 Sep 2021 13:00:55 GMT</pubDate>
    <dc:creator>ChrisHemedinger</dc:creator>
    <dc:date>2021-09-15T13:00:55Z</dc:date>
    <item>
      <title>running sas in a terminal window of winscp</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/running-sas-in-a-terminal-window-of-winscp/m-p/767886#M39537</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A colleague is executing a sas program via a terminal window of winscp, on a unix server and it start well.&lt;/P&gt;
&lt;P&gt;However, as the execution last at least 10 hours, the terminal window will closed after let's say few hours then causing the sas program to stop.&lt;/P&gt;
&lt;P&gt;Is there a way to avoid that and if so how.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Sep 2021 12:50:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/running-sas-in-a-terminal-window-of-winscp/m-p/767886#M39537</guid>
      <dc:creator>alepage</dc:creator>
      <dc:date>2021-09-15T12:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: running sas in a terminal window of winscp</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/running-sas-in-a-terminal-window-of-winscp/m-p/767888#M39538</link>
      <description>&lt;P&gt;In my experience a shell terminal to a Linux OS can close after a time, either due to firewall timeout or (with us working from home) a temporary network disconnect.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The best approach is to run any long-running process asynchronously so it is not interrupted when the shell window disconnects. Use the &amp;amp; terminator on the command, which returns control immediately back to the shell.&amp;nbsp; Example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="shell"&gt;/usr/local/bin/sas mysasbatch.sas -log ./logs/mysasbatch.log &amp;amp;&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When you return to find the shell disconnected, simple "shell in" again and check the contents of the SAS log.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Sep 2021 13:00:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/running-sas-in-a-terminal-window-of-winscp/m-p/767888#M39538</guid>
      <dc:creator>ChrisHemedinger</dc:creator>
      <dc:date>2021-09-15T13:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: running sas in a terminal window of winscp</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/running-sas-in-a-terminal-window-of-winscp/m-p/767892#M39539</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am glad to see that your are using almost the same command as we are usually do.&lt;/P&gt;
&lt;P&gt;Most of the time, we usually use a command like this one:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;nohup path/sasprogram.sas &amp;amp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;and normally we don't have any issue.&amp;nbsp; As we have received the question on our internal sas forum,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I did not have a chance to talk to that person due to time zone.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks a lot for your advise.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Sep 2021 13:10:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/running-sas-in-a-terminal-window-of-winscp/m-p/767892#M39539</guid>
      <dc:creator>alepage</dc:creator>
      <dc:date>2021-09-15T13:10:32Z</dc:date>
    </item>
  </channel>
</rss>

