<?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/coonect in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/SAS-CONNECT-required-for-remote-connection/m-p/458034#M29502</link>
    <description>&lt;P&gt;If your using sas/coonect, then you need a pigeon.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As for SAS/Connect, well, that depends on your setup of remote system and local environment, licensees, what the connection is to be - for instance, can you get away with ftp'ing files across etc.&amp;nbsp; Not enough information to make a judgement.&lt;/P&gt;</description>
    <pubDate>Fri, 27 Apr 2018 08:03:39 GMT</pubDate>
    <dc:creator>RW9</dc:creator>
    <dc:date>2018-04-27T08:03:39Z</dc:date>
    <item>
      <title>SAS/CONNECT required for remote connection?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/SAS-CONNECT-required-for-remote-connection/m-p/458026#M29500</link>
      <description>&lt;P&gt;TO connect with a remote system from our local environment do we need sas/connect component in both the system?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Apr 2018 10:44:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/SAS-CONNECT-required-for-remote-connection/m-p/458026#M29500</guid>
      <dc:creator>ajay143</dc:creator>
      <dc:date>2018-04-27T10:44:04Z</dc:date>
    </item>
    <item>
      <title>Re: sas/coonect</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/SAS-CONNECT-required-for-remote-connection/m-p/458028#M29501</link>
      <description>&lt;P&gt;If your "local environment" is Base SAS with the SAS Windowing Environment the answer is yes, you need SAS/CONNECT installed on both your local workstation and on the remote SAS server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On the other hand, if your local environment includes Enterprise Guide then that includes the ability to connect to both local SAS and remote server SAS so you don't need SAS/CONNECT.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Apr 2018 07:10:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/SAS-CONNECT-required-for-remote-connection/m-p/458028#M29501</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-04-27T07:10:46Z</dc:date>
    </item>
    <item>
      <title>Re: sas/coonect</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/SAS-CONNECT-required-for-remote-connection/m-p/458034#M29502</link>
      <description>&lt;P&gt;If your using sas/coonect, then you need a pigeon.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As for SAS/Connect, well, that depends on your setup of remote system and local environment, licensees, what the connection is to be - for instance, can you get away with ftp'ing files across etc.&amp;nbsp; Not enough information to make a judgement.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Apr 2018 08:03:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/SAS-CONNECT-required-for-remote-connection/m-p/458034#M29502</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2018-04-27T08:03:39Z</dc:date>
    </item>
  </channel>
</rss>

