<?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 Setting up SAS/Connect between Windows and UNIX in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Setting-up-SAS-Connect-between-Windows-and-UNIX/m-p/62580#M13630</link>
    <description>I'm working in a very tightly controlled UNIX environment.    SAS/Connect is licensed but not hooked up.    &lt;BR /&gt;
&lt;BR /&gt;
Is it correct to assume that the only way SAS/Connect can access a UNIX system from Windows is to add a service entry to /etc/services on the UNIX server to accept the incoming TCP connection from Windows?

Message was edited by: JMarkW</description>
    <pubDate>Fri, 21 Nov 2008 15:00:31 GMT</pubDate>
    <dc:creator>JMarkW</dc:creator>
    <dc:date>2008-11-21T15:00:31Z</dc:date>
    <item>
      <title>Setting up SAS/Connect between Windows and UNIX</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Setting-up-SAS-Connect-between-Windows-and-UNIX/m-p/62580#M13630</link>
      <description>I'm working in a very tightly controlled UNIX environment.    SAS/Connect is licensed but not hooked up.    &lt;BR /&gt;
&lt;BR /&gt;
Is it correct to assume that the only way SAS/Connect can access a UNIX system from Windows is to add a service entry to /etc/services on the UNIX server to accept the incoming TCP connection from Windows?

Message was edited by: JMarkW</description>
      <pubDate>Fri, 21 Nov 2008 15:00:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Setting-up-SAS-Connect-between-Windows-and-UNIX/m-p/62580#M13630</guid>
      <dc:creator>JMarkW</dc:creator>
      <dc:date>2008-11-21T15:00:31Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up SAS/Connect between Windows and UNIX</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Setting-up-SAS-Connect-between-Windows-and-UNIX/m-p/62581#M13631</link>
      <description>If you are using telnet access method, no entry is needed. If you plan to use a spawner, adding an entry in /etc/services is optional. But it is a nice way to tell other UNIX applications that this port no has been occupied. If you at spawner startup want to refer to a service name, then you have to have an services entry. I think you can use port numbers generally, but I think it's more user friendly and a better practice to use service names.&lt;BR /&gt;
&lt;BR /&gt;
/Linus&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://support.sas.com/documentation/cdl/en/camref/59596/HTML/default/a002251146.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/camref/59596/HTML/default/a002251146.htm&lt;/A&gt;</description>
      <pubDate>Fri, 21 Nov 2008 15:34:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Setting-up-SAS-Connect-between-Windows-and-UNIX/m-p/62581#M13631</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2008-11-21T15:34:38Z</dc:date>
    </item>
  </channel>
</rss>

