<?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 SAS Process running on UNIX in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/SAS-Process-running-on-UNIX/m-p/322080#M71219</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am using tcpunix.scr file to connect to the UNIX server. After the session gets established, a unix job starts running which looks something like:-&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;userid 27949 28760 &amp;nbsp;0 02:32:40 ? &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 0:00 /opt/sas/sas9.3ts1m2/SASFoundation/9.3/sasexe/sas -dmr -comamid tcp -noterminal -nosyntaxcheck -news&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;In some scenarios these jobs keeps running even after signing off and closing the SAS session.Please suggest the&amp;nbsp;scenarios of these orphan jobs.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Jan 2017 08:00:10 GMT</pubDate>
    <dc:creator>Aditi24</dc:creator>
    <dc:date>2017-01-03T08:00:10Z</dc:date>
    <item>
      <title>SAS Process running on UNIX</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Process-running-on-UNIX/m-p/322080#M71219</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am using tcpunix.scr file to connect to the UNIX server. After the session gets established, a unix job starts running which looks something like:-&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;userid 27949 28760 &amp;nbsp;0 02:32:40 ? &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 0:00 /opt/sas/sas9.3ts1m2/SASFoundation/9.3/sasexe/sas -dmr -comamid tcp -noterminal -nosyntaxcheck -news&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;In some scenarios these jobs keeps running even after signing off and closing the SAS session.Please suggest the&amp;nbsp;scenarios of these orphan jobs.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2017 08:00:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Process-running-on-UNIX/m-p/322080#M71219</guid>
      <dc:creator>Aditi24</dc:creator>
      <dc:date>2017-01-03T08:00:10Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Process running on UNIX</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Process-running-on-UNIX/m-p/322096#M71226</link>
      <description>&lt;P&gt;You might have a broken TCP/IP connection before the signoff, or the client SAS session terminated in a non-graceful way, preventing a proper signoff.&lt;/P&gt;
&lt;P&gt;I routinely scan for CONNECT server sessions that have a parent process ID of 1 (meaning that the telnetd terminal server part has closed, signifying a lost telnet connection) and kill them (superuser privilege needed).&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2017 10:27:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Process-running-on-UNIX/m-p/322096#M71226</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-01-03T10:27:42Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Process running on UNIX</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Process-running-on-UNIX/m-p/322100#M71230</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/11562"&gt;@Kurt_Bremser&lt;/a&gt;: Thanks for your reply. Could you please provide more information on the below part :-&lt;BR /&gt;&lt;BR /&gt;CONNECT server sessions that have a parent process ID of 1 (meaning that the telnet terminal server part has closed, signifying a lost telnet connection)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, is there a scenario to replicate this?&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2017 10:58:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Process-running-on-UNIX/m-p/322100#M71230</guid>
      <dc:creator>Aditi24</dc:creator>
      <dc:date>2017-01-03T10:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Process running on UNIX</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Process-running-on-UNIX/m-p/322122#M71242</link>
      <description>&lt;P&gt;In your output of the ps command, the third column (the second number) is the PPID. Typically, this would be the shell from which SAS was started. If the terminal connection is lost, this number changes to 1.&lt;/P&gt;
&lt;P&gt;But this is true only for connections that use telnet. With a Connect Spawner, you will probably need another mechanism to detect orphaned connect sessions.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2017 13:51:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Process-running-on-UNIX/m-p/322122#M71242</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-01-03T13:51:00Z</dc:date>
    </item>
  </channel>
</rss>

